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

Plan the interface remediation sprint

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-26 14:24:07 +00:00
parent f6d54a094a
commit 0dd16aa8a9
2 changed files with 698 additions and 292 deletions
Download Patch File Download Diff File Expand all files Collapse all files

41
docs/roadmap/interface-remediation.md
View File

@@ -6,9 +6,9 @@ Planning baseline: `1f64673` (v0.10.2 implementation plus documentation changes)
This roadmap covers the four findings in the [interface audit](interfaces.md).
The audit owns reproductions, evidence, and finding numbers. This document owns
the combined target, required changes, and general dependency order. A subsequent
implementation plan should own concrete stages, private implementation choices,
validation commands, and progress.
the combined target, required changes, and design intent. The
[implementation plan](implementation.md) owns concrete stages, private
implementation choices, validation commands, and progress.
## Purpose And Scope
@@ -264,41 +264,6 @@ would therefore be insufficient. No public ordering option is needed for this
correction. Keep primary selection, conflict detection, acquisition order, and
dependency-ready scheduling unchanged.
## General Implementation Order
1. Prepare the concrete shared-evidence design and focused regression cases.
Map existing producers and consumers to the new owner, distinguish common
attribution from presentation rules, and identify the old paths to remove.
Select representations and indexes that preserve existing query and lifetime
needs without adding public contracts.
2. Repair entry-state presence queries and `Default` (finding 1). This is a local
correction that can proceed independently of the larger history work.
3. Repair final explicitness preservation (finding 2), retaining the shape evidence
needed by metadata updates. Coordinate this work with history construction so
the two fixes do not introduce competing definitions of path identity.
4. Build the shared model and migrate metadata history, explanation, sensitivity
dependencies, and diagnostic-location readers. Preserve phase evidence and
derive both public projections through common semantic attribution. Remove
the superseded reconstruction paths and reconcile retained-history accounting.
Verify finding 3 and its interaction with final presence metadata; repairing
pointer buckets alone does not complete the selected architecture.
5. Complete composition diagnostic ordering (finding 4) as an independent change;
it may proceed alongside the path work. Check rendering as well as the
structured error before considering it complete.
6. Review the integrated result, run applicable development checks, and update
affected implementation documentation and finding status.
This work will be completed in one implementation sprint. Intermediate stages
and commits need not be coherent or compile, and will not be made available to
consumers. The order above describes dependencies within that sprint. It does
not require temporary adapters or parallel implementations merely to keep each
stage buildable.
Keep changes focused and the four findings individually traceable. Run focused
checks when the affected surface is buildable, and complete any pending checks
against the integrated result. The final sprint result must compile, pass the
applicable development checks, and satisfy the full completion criteria below.
## Validation And Completion
Follow the [testing policy](../policy/testing.md) and use the