Skip to content

Protocol Change System

AUMP is a multi-repo protocol suite. A change is not complete when a schema or SDK test passes in one repository. Protocol work must preserve parity across:

  • spec
  • conformance
  • aump-py
  • aump-js
  • examples
  • site

Automated Gates

Repository Gate Purpose
conformance scripts/check_spec_parity.py Ensures copied schemas and canonical examples match spec.
aump-py scripts/check_conformance_snapshot.py Ensures bundled SDK fixtures match canonical conformance fixtures.
aump-js npm run check:parity Ensures bundled TypeScript fixtures match canonical conformance fixtures.
site scripts/check_docs_parity.py Ensures public docs track spec fields, conformance count, compliance docs, and example pages.

Publishing

The site CI builds and smokes the static documentation on every pull request and push. On main, the deploy job publishes the built public/ assets through Wrangler to Cloudflare.

Required site repository secrets:

  • CLOUDFLARE_API_TOKEN
  • CLOUDFLARE_ACCOUNT_ID

If those secrets are missing, the docs can still build locally and in CI, but the live site will not update.

Agent Skill

The workspace includes a project-local skill:

.agents/skills/aump-protocol-development/SKILL.md

Future Codex work should use that skill whenever protocol behavior, schemas, fixtures, SDK evaluators, examples, docs, CI, or deployment are touched. The skill makes the parity workflow explicit so changes do not depend on memory or manual checklist discipline.