This page lists the v0.1.0 vocabulary used by the schema, validator, and portal examples.
Public schema identifier for this vocabulary:
https://schemas.openagentcontracts.org/aoc/v0.1.0/contract.schema.json
| Key | Status | Notes |
|---|---|---|
contract_version |
stable | Semver target for the contract grammar. |
app |
stable | App identifier and plain-prose purpose. |
contexts |
stable | Agent-visible context catalog. |
actions |
stable | Agent-visible action catalog. |
human_ask |
stable | Human review or authorization channel. |
receipts |
stable | Declared runtime receipt event names. |
anti_claims |
stable | No-overclaim statements; optional-with-default in raw input. |
provenance |
stable | Authoring source and timestamp. |
user_values |
experimental | Builder-stated preferences or norms. |
hard_boundaries |
experimental | Explicit advisory boundary statements. |
export_targets |
experimental | Builder intent for future projection targets. |
stability |
experimental | Optional sidecar for field stability overrides. |
human_ask.channel may be:
in_appemail_linkpushcliout_of_bandout_of_band is required when a contract declares
gate: authorization_required for an external or irreversible action.
The local validator reports two channels:
errors[] for invalid or unsafe-to-accept contract defects;findings[] for coverage gaps and advisory issues.Each entry carries:
pathcodemessageseveritydocE_SCHEMA_INVALIDE_MISSING_REQUIRED_KEYE_MISSING_REQUIRED_SUBFIELDE_RESERVED_KEY_COLLISIONE_HUMAN_ASK_REQUIREDE_RECEIPTS_R1E_RECEIPTS_R2E_RECEIPTS_R3E_OUT_OF_BAND_REQUIREDE_FORBIDDEN_FIELDE_VERSION_MISMATCHF_EMPTY_CONTEXTSF_EMPTY_ACTIONSF_EMPTY_ANTI_CLAIMSF_NON_READONLY_GATE_NONEF_EXPERIMENTAL_FIELDF_GENERATOR_MISSINGF_BOUNDARY_GREP_HITF_UNUSED_EXPORT_TARGETFindings are not certification failures. They are coverage signals for maintainers and implementers.