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

Record selected initial roadmap decisions

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-07 03:27:13 +00:00
parent 9d7f3b25a1
commit 0f6ced42ef
2 changed files with 90 additions and 156 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/roadmap/initial-plan.md
View File

@@ -1,12 +1,14 @@
# Preparing the initial CommandKit feature roadmap
Status: initial roadmap drafted; delivery/API decisions and roadmap review pending.
Status: roadmap review complete; ready to prepare the staged implementation plan.
Date: 2026-10-07.
Progress is recorded in [the initial roadmap](initial.md). Checked entries mean
the assessment or recommendation is recorded, not that a proposed contract has
been approved. Its Open Decisions section identifies the remaining choices.
Progress is recorded in [the initial roadmap](initial.md). Roadmap review selected
the delivery scope, typed API/outcome model, selectors/report behavior, and full
profile coverage including `ExtraParams`. Exact Go declarations will be specified
in the staged implementation plan using those selections. Checked entries record
completed planning work; the staged plan remains the next deliverable.
## Purpose and use
@@ -111,7 +113,7 @@ Organize the inventory around these feature groups:
- [x] Identify which capabilities are available now and which need upstream work.
- [x] For each missing capability, recommend including the upstream work or
explicitly deferring that feature, with the reason and affected targets.
- [ ] Settle initial delivery scope before preparing the ordered implementation
- [x] Settle initial delivery scope before preparing the ordered implementation
plan. Missing capabilities leave independently supported operations available.
**Result:** feature specifications and an explicit initial delivery scope with its
@@ -164,7 +166,7 @@ provenance and adaptation requirements for proposed ports.
applicable policies and current dependency requirements.
- [x] For viable alternatives, record a recommendation and a short analysis of
each alternative.
- [ ] Resolve choices that would otherwise require Luna to invent public behavior
- [x] Resolve choices that would otherwise require Luna to invent public behavior
or package boundaries while following the implementation plan.
API shapes in planning remain design targets until implemented. Go declarations
@@ -185,7 +187,7 @@ resolved to the depth needed by the later implementation plan.
implementation lands.
- [x] Review the complete draft against its requirements checklist and package map.
- [x] Make upstream work, deferrals, and unresolved decisions visible in the draft.
- [ ] Review the targeted end state before translating it into implementation tasks.
- [x] Review the targeted end state before translating it into implementation tasks.
- [ ] Prepare the subsequent staged plan with ordered tasks, prerequisites, precise
deliverables, and completion checks mapped to the roadmap's feature identifiers.