Skip to main content
A verifier is one testable check. Policies are bundles of verifiers: every string in a policy’s checks[] is surfaced in the Verifier Registry as a runtime verifier (id: policy:<policyId>:<index>), so each policy links out to the exact checks it will run.

Verifier kinds

Craft a new verifier

This scaffolds a Harbor-style bundle:
task.toml
tests/test.sh
Draft verifiers live client-side (localStorage: akhara.custom-verifiers.v1) until you sync them. A draft looks like { id: "custom_<slug>_<base36>", name, kind, desc, checks, custom: true }.

Sync to the decision point

Push drafts to the PDP so policies can bind them at runtime:

How verifiers relate to everything else

At runtime each verifier emits a result under the amazon.mobile.verifier_result.v1 schema and appears on both the run trace and the enforcement feed.

Next: publish tasks

Package reproducible agent work graded by these verifiers.