M2 — spec state (drift-guarded source of truth)

Milestone 2 of the AF governance layer. This tag marks the dspack spec repo's M2 state: the v0.3 contract as amended through M1/M2 (governance blocks, example links, the maintainer's table component), serving as the byte-authoritative source of truth for the contract copies in dspack-emit, dspack-gen, and ds-mcp — now drift-guarded by CI checks in every consumer repo (dspack-gen#7).

Companion M2 tags: ds-mcp@m2, dspack-emit@m2 (second emitter target, npm rename), dspack-gen@m2 (eval harness + findings). The governing plan document (revision records 1–6) is maintained by the project owner.

M1 — dspack v0.3: the governance blocks

Milestone 1 of the AF governance layer. This tag marks the dspack v0.3 draft as shipped for M1:

• Governance blocks (intents, rules, examples) — machine-checkable, strictly additive over v0.2 (spec/dspack-v0.3.md, with the migration guide and worked anti-pattern→rule conversion in spec/migration-v0.2-to-v0.3.md).
• dspack surface v0.1 (schema/dspack.surface.v0_1.schema.json) — the protocol-neutral component tree governance is evaluated against; an intermediate representation, never rendered or transported.
• Validation harness (npm run validate) — schema compile, example validation with gates S1/S2 over embedded surfaces, cross-reference consistency (incl. normative sub-component id uniqueness), 12 negative fixtures, CI-gated.

Companion M1 tags: dspack-to-a2ui@m1 (A2UI emitter, gates A1–A3), dspack-gen@m1 (pipeline, gates S1–S3, audit report v1, evidence). The governing plan document ("AF Governance Layer — ADR-Driven Implementation Plan", revision records 1–3) is maintained by the project owner and referenced by the M1 write-up.