Architecture Contract Decision Index¶
This index connects future-state proposals and compatibility registry decisions
to the active implementation surfaces they govern. It does not replace
docs/reference/public-contracts.md; it is the planning-side index for decisions
that are not fully implemented yet.
Decision |
Status |
Owner |
Blocking gate |
Current implementation surface |
|---|---|---|---|---|
Formalize MCP internal API references as public exports |
Future-state proposal, Tier 2 |
mcp |
Export tests for the three symbols and no |
|
Define benchmark family plugin seam before core package extraction |
Pilot complete on SSB; further migration stopped pending new evidence |
benchmark-api |
Keep public wrapper tests and the SSB plugin contract green; do not migrate another family until a runtime consumer of |
|
Remove maintainer/release tooling from the wheel |
Blocked on evidence for further extraction |
packaging/release |
Measure demand, CI-minute impact, and release cost after confirming the current wheel has no maintainer-package paths. |
|
Isolate experimental core subsystems |
Blocked on evidence for further extraction |
architecture |
Measure demand, install-size benefit, CI burden, and release cost before creating a companion package or extra; current wheel contents remain unchanged. |
|
Gate monitoring behind an optional extra |
Blocked on evidence |
core-runtime |
Demonstrate an install-size win and a second-consumer or demand case; |
|
Preserve top-level wrapper facades while benchmark API cleanup proceeds |
Active compatibility boundary |
benchmark-api |
Wrapper facade tests stay green or a deprecation row/migration lands. |
|
Retain |
Deprecated compatibility surface |
core-runtime |
Dedicated migration/removal item completes and updates the compatibility registry. |
|
Keep composition below CLI and MCP in the core kernel |
Accepted architecture boundary |
architecture |
Remove allowlisted core-to-platforms edges in the ADR’s order; canonicalize the SQL execute primitive before broad injection work. |
|
Review Rule¶
When a future-state proposal becomes implementation work, the PR should update both this index and the public contract map if it changes a public, beta-public, generated, deprecated, or experimental surface.