Roadmap: human- and AI-readable MAP schemas

[rajanbor]

Outcome

Deliver a coherent schema layer for MAP in dependency order. Every contract follows ADR-0001: machine-readable JSON Schema plus a human guide, complete examples, invalid fixtures, compatibility notes, and deterministic validation.

Phase 1 — shared foundation

• Schema: canonical MAP document envelope #95 Canonical MAP document envelope
• Schema: project manifest and initialization contract #89 Project manifest and initialization contract

Phase 2 — intent and authority

• Schema: architecture decision records #91 Architecture decision records
• Schema: AI agent profiles, permissions, and escalation #92 AI agent profiles, permissions, and escalation
• Schema: tools and side-effect contracts #90 Tools and side-effect contracts

Phase 3 — execution and quality

• Schema: deterministic agent workflows #93 Deterministic agent workflows
• Schema: reusable prompts and output contracts #97 Reusable prompts and output contracts
• Schema: evaluations, datasets, metrics, and release gates #96 Evaluations, datasets, metrics, and release gates
• Schema: token budgets and context optimization reports #94 Token budgets and context optimization reports

Cross-cutting definition of done

• JSON Schema draft 2020-12; stable IDs and explicit versions.
• Human guide uses exactly the same vocabulary as the schema.
• At least one complete valid example and representative invalid fixtures.
• Validation errors name file, field, reason, and remediation.
• Offline deterministic CI validation.
• Compatibility, migration, and rollback are documented.
• Schema artifacts are published with releases and consumable by the CLI.

Delivery rule

Land one independently reviewable schema per PR. Do not start a dependent schema until its required vocabulary is accepted; prototypes may use x- extension fields.