Decisions

Durable decisions about how the project is built and released. Each record states the context, the decision and its consequences; plans link to them instead of repeating them. Accepted by the Maintainer on 2026-10-16 with ops/plan-architecture.md.

An accepted decision is not necessarily in effect. The records describe the target; until a decision is implemented, the pages it would change (for example Versioning) describe what the project does today. Each record has an “Implemented” line.

Decision	In effect (2026-10-22)
0001: Release model: a pinned contract bundle, not lockstep	No. No contract bundle yet; Phase C of the plan, parked
0002: SDK capability tiers; Go and .NET as verifier plus thin client	No. No capability matrix; Go and .NET still follow the lockstep train
0003: Verification engine: separate ports driven by generated tables	No. No generated per-kind tables
0004: Forward compatibility for unknown record kinds	No. No unverified_kind outcome
0005: Feature-switch lifecycle and upgrade support window	No. upgrade.yml still covers every release since 0.59.1
0006: Review: automatic Copilot review and review agents, no required human approval	Yes
0007: Dormant core packages are internal	In part. The module map marks the packages; the contract only omits them

• 0001: Release model: a pinned contract bundle, not lockstep
• 0002: SDK capability tiers; Go and .NET as verifier plus thin client
• 0003: Verification engine: separate ports driven by generated tables
• 0004: Forward compatibility for unknown record kinds
• 0005: Feature-switch lifecycle and upgrade support window
• 0006: Review: automatic Copilot review and review agents, no required human approval
• 0007: Dormant core packages are internal