Clarify completed implementation records and later corrections

This commit is contained in:
2026-10-07 18:27:04 +00:00
parent b98845bae9
commit b45cbb3bb6
3 changed files with 40 additions and 13 deletions

View File

@@ -1,6 +1,6 @@
# Initial CommandKit feature roadmap
Status: selected initial implementation target; implemented.
Status: selected initial target implemented; completed design baseline.
Date: 2026-10-07.
@@ -9,8 +9,10 @@ Date: 2026-10-07.
This document defines the selected initial target for the library: packages,
features, integration contracts, dependencies, and completion evidence. It was
prepared using [the agreed checklist](initial-plan.md). Implementation steps and
stage evidence belong in [the implementation plan](implementation.md). The
included target is implemented; the table below records feature status.
stage evidence belong in [the completed implementation plan](implementation.md).
Detailed specifications below preserve the selected design baseline; they are
planning history, not a parallel current API or operator reference. The included
target is implemented; the table below records feature status.
| Included feature IDs | Status | Evidence |
| --- | --- | --- |
@@ -25,8 +27,10 @@ The [architecture policy](../policy/architecture.md) and nine accepted ADRs cont
this roadmap. The delivery scope, typed API model, selector/report behavior, and
full profile inspection described here were selected during roadmap review.
These implementation choices operate within the accepted architecture. Exact
exported contracts will belong in Go declarations and GoDoc; implemented operator
contracts will belong in `docs/cli.md`.
exported contracts belong in Go declarations and GoDoc, navigated through the
[consumer guide](../consumers/guide.md); implemented operator contracts belong in
the [CLI reference](../cli.md). The [internal overview](../internal/overview.md)
owns current package inventory and mechanics.
### Requirements and traceability