The Agent Governance Protocol — specification, JSON Schemas, and reference fixtures.
concept-and-spec.md— full v0.1 working draft (concepts + protocol spec + reference implementation plan + adoption strategy)schemas/— JSON Schemas for canonical event, policy descriptor, decision request/response, discovery document (coming)fixtures/events/— 50 example events covering allaction.typevalues (coming)fixtures/policies/— 10 example policies covering all rule patterns (coming)decisions/— RFCs and decision records for substantive spec changes (coming)
v0.1 — working draft. The spec is functional enough to start a reference implementation against, but is not yet a final RFC. Items marked [OPEN] in the spec are decisions for the standards working group once formed.
See §4 of the spec for the build order. The reference implementations live in sibling repos:
openagp/sdk-pythonopenagp/sdk-typescriptopenagp/cts— Conformance Test Suiteopenagp/registry— Public actor registryopenagp/examples
See CONTRIBUTING.md and GOVERNANCE.md at the org level. For routing — questions vs. bugs vs. spec changes — see SUPPORT.md.
For spec changes:
- Open a Spec change issue describing the change and rationale.
- PR adds a decision record in
decisions/. - Substantive changes have a 2-week comment period; breaking changes have 4 weeks.
# Validate every event fixture against schemas/event.json (same script CI runs)
pip install "jsonschema>=4.21.0" "referencing>=0.34.0"
# see .github/workflows/validate.yml for the exact validator
# Run the cross-language test vectors against an SDK
cd ../sdk-python && pytest tests/test_interop.py
cd ../sdk-typescript && npm test -- interop
cd ../cts && make vectorsIf you're changing a schema or a test vector, the SDKs and agp-cts must all stay green — they share these inputs.
Use GitHub Discussions on this repo for design conversations and "how do I model X?" questions.
CC BY 4.0 — you may share and adapt the spec for any purpose, including commercially, with attribution.