base-layer/commandkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Plan the multi-module implementation sprint

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-11 00:06:31 +00:00
parent bb849ff3e1
commit 0d23676144
4 changed files with 839 additions and 137 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/roadmap/registration-api.md
View File

@@ -1274,15 +1274,15 @@ The documentation alignment is complete:
| --- | --- |
| [ADR 0011](../adr/0011-captured-declarations-and-installation.md) | Captured declarations, atomic installation batches, installed-family ownership, root-only placement, separate input/shared-state lifetimes, and scope-aware configuration input validation |
| [ADR 0001 status](../adr/0001-command-dispatch-and-inputs.md#status) | Remains accepted, with refinements recorded in ADR 0011 and its decision text preserved |
| [ADR 0010](../adr/0010-optional-integration-modules.md) | Core/integration dependency boundaries remain in effect; ADR 0011 refines registration and supersedes the migration-guide requirement for this unreleased prototype |
| [ADR 0010](../adr/0010-optional-integration-modules.md) | Core/integration dependency boundaries remain in effect; ADR 0011 refines registration and supersedes the earlier prototype migration-guide requirement |
| [Architecture policy](../policy/architecture.md) | Uniform installed-family ownership, optional integration facades, and declaration/input boundaries |
| [Module roadmap](modules.md) | Final API and backend design selected; extraction and release adoption still pending |
| [Backend design](registration-backend.md) | Shared internal pipeline, runnable children, scope-error attachment, unused-binding validation, and both composition-question resolutions |
A staged module implementation plan remains to be written from this finalized
The [staged implementation plan](implementation.md) translates this finalized
API, the finalized [backend design](registration-backend.md), and the module
roadmap. Both composition questions are resolved. The plan should specify eager
capture, error retention, neutral bindings, scope isolation, maintained examples,
and release adoption.
roadmap into ordered implementation assignments. Both composition questions are
resolved; the plan covers eager capture, error retention, neutral bindings, scope
isolation, maintained examples, and release adoption.
The documentation alignment neither implements these changes nor authorizes
implementation by itself.