Outcome
Declare the first supported replacement protocol baseline only after the M3 vertical slice exercises every essential state machine end to end.
Scope and normative requirements
- Inventory all descriptors/messages/fields/enums/services/spec state machines used by M3 and ensure normative limits/errors/authorization/reconnect semantics are complete.
- Establish Buf breaking baseline, supported server/client version range, capability negotiation, additive-change rules, deprecation/reservation period, and major-version process.
- Publish descriptor/generated Go/Rust packages, fixtures, docs, checksums, SBOM/provenance, and consumer compatibility manifest as one immutable release set.
- Define security-fix handling and whether unknown additive fields/features are ignored, rejected, or capability-gated by context.
- Record content/artifact/resource format versions separately; protocol release must not hide their compatibility.
Acceptance criteria
- Pinned M3 Go server/Rust client pass all conformance/negative/state-machine tests using released artifacts.
- No hand-written duplicate message model is treated as canonical in consumers.
- All field numbers/names removed during development are reserved before freeze.
- A compatibility test proves an allowed additive update and an intentionally breaking change is rejected by policy.
- Post-freeze schema changes require owning issues, consumer coordination, fixtures, and release notes.
Dependencies and parallelization
Depends on #1-#12 and the integrated M3 slice. It gates production client/server compatibility promises, not M1/M2 parallel development.
Licensing and scope boundary
Protocol schemas, specifications, fixtures, and generators are MIT. Verified original past work by an approved MIT provenance grantor may be migrated under the recorded provenance grant. Compiled content artifacts are specified by content-toolkit; this repository owns network contracts only.
Program equivalence output
The frozen GP1 release must publish immutable schema/descriptor/generated-package/conformance coordinates and a compatibility manifest consumable by atrinik#279. This issue is a native blocker of atrinik#280. Functional equivalence is compared through stable observations, not classic packet bytes or a dual-protocol implementation.
Outcome
Declare the first supported replacement protocol baseline only after the M3 vertical slice exercises every essential state machine end to end.
Scope and normative requirements
Acceptance criteria
Dependencies and parallelization
Depends on #1-#12 and the integrated M3 slice. It gates production client/server compatibility promises, not M1/M2 parallel development.
Licensing and scope boundary
Protocol schemas, specifications, fixtures, and generators are MIT. Verified original past work by an approved MIT provenance grantor may be migrated under the recorded provenance grant. Compiled content artifacts are specified by content-toolkit; this repository owns network contracts only.
Program equivalence output
The frozen GP1 release must publish immutable schema/descriptor/generated-package/conformance coordinates and a compatibility manifest consumable by atrinik#279. This issue is a native blocker of atrinik#280. Functional equivalence is compared through stable observations, not classic packet bytes or a dual-protocol implementation.