Verify the native cutover and complete the implementation roadmap

This commit is contained in:
2026-11-22 07:11:50 +00:00
parent 633ebd282f
commit 75444b8ef3
8 changed files with 102 additions and 31 deletions

View File

@@ -13,9 +13,10 @@ accepted-artifact caching, and artifact-first output. It owns the selected targe
decision status, removal inventory, acceptance criteria, and supporting evidence.
The earlier discussion documents are retired; Git history preserves the discussion.
The [implementation plan](implementation.md) owns the ordered, prompt-sized stages.
The native cutover and canonical documentation are implemented, with completion
evidence recorded in that plan. The final whole-roadmap acceptance audit remains
pending; implementation markers do not substitute for that verification.
The native cutover, canonical documentation, and final whole-roadmap acceptance
audit are complete. The implementation plan records the owning evidence and
successful assembled checks; no live-model quality or release-publication claim
is implied.
Current behavior belongs in [Configuration](../config.md), [CLI Reference](../cli.md),
[Operations](../operations.md), and [native migration guidance](../consumers/native-migration.md).
Unrelated future work remains in the [separate backlog](future.md).
@@ -61,7 +62,7 @@ together without local replacements in an isolated consumer module. Maintained
composed-CLI and offline-preparation examples and focused message-hash,
configuration-handoff, and schema tests passed without live provider calls.
Those checks established the upstream baseline; subsequent Notarius implementation
evidence is recorded in the plan, with final acceptance pending. See the
evidence and final acceptance are recorded in the plan. See the
[current integration boundary](../integrations/pkg-commandkit.md) and
[integration version guidance](https://forge.maximumdirect.net/base-layer/commandkit/src/tag/v0.7.0/docs/consumers/guide.md#module-selection)
and tagged [release notes][release], [migration guide][migration],
@@ -159,7 +160,7 @@ guidance ownership below; U5 selects retry controls and the correction budget.
U6 selects strict-by-default handling and module-owned fallbacks below;
configuration precedence and fallback behavior are implemented. See
[Pipeline Internals](../internal/pipeline.md) and the plan's completed operation/
module work; final acceptance remains pending.
module work and completed final acceptance evidence.
Retain the fixed `input -> chunk -> extract -> merge -> normalize -> output`
shape, ordered steps and generated references, typed artifact-family boundaries,
@@ -438,8 +439,8 @@ identity/version/name metadata whose only consumers were adapters, checkpoints,
or reporting. No independent schema metadata system replaces them.
Native preparation is implemented and covered by asset/operator-schema tests
recorded in the plan. Final verification must confirm embedded and operator
prompt definitions, shared-file paths, schema selection from embedded and external
recorded in the plan. Final verification confirmed embedded and operator prompt
definitions, shared-file paths, schema selection from embedded and external
roots, source-relative/inline selection, and complete request-contract replacement
where actually used. Missing or invalid schemas follow native preparation
behavior. No new schema check requiring synthetic requests is added to offline
@@ -527,7 +528,7 @@ apply U6's strict/permissive handling when no acceptable result is obtained.
Ownership, response contracts, and default profile behavior are resolved. Refine
exact template prose, correction IDs, and necessary operation-specific inputs
within implemented module boundaries. The plan records producer/prompt/assessment
coverage; final verification remains pending. U5 selects semantic budgets and U6
coverage and successful final verification. U5 selects semantic budgets and U6
selects strict-by-default terminal handling and fallbacks.
#### Execution And Assessment Flow
@@ -730,8 +731,8 @@ Record why fallback was used and expose that qualification in the ordinary
completion report, even when diagnostic verbosity hides individual warnings.
Use the same application outcome for reporting and optional debug detail. Keep
conversation state in process, outside ordinary artifact/cache payloads;
explicitly requested detailed debug is separate. U6 is resolved; module-specific
construction remains implementation work.
explicitly requested detailed debug is separate. U6 and module-specific
construction are implemented; the plan records terminal-mode and domain coverage.
### Admission And Pipeline Workers (U7 Resolved)
@@ -819,7 +820,7 @@ translate a cross-backend ceiling into per-backend limits or preserve worker
inheritance/caps from that field. Provide a native limited-backend example with
usable queue capacity, without requiring operators to override the upstream
queue default. U7 is implemented with focused worker/admission and assembled
coverage recorded in the plan; final acceptance remains pending.
coverage and final acceptance recorded in the plan.
### Accepted-Artifact Cache (U8 Resolved)
@@ -1232,8 +1233,8 @@ U1–U10 are resolved. There are no remaining open architectural or dependency
choices in this roadmap. Native loading/execution/commands, accepted-result reuse,
artifact-first reporting, capture, examples, and documentation are implemented.
Observer wiring, private debug representations, and routine API placement are
concrete implementation choices, not deferred architecture. The final assembled
acceptance/removal/link audit remains pending in the [implementation plan](implementation.md).
concrete implementation choices, not deferred architecture. The completed assembled
acceptance/removal/link audit is recorded in the [implementation plan](implementation.md).
IDs retain continuity with the earlier roadmap.
**U1 resolved:** The [reviewed dependency set](#baseline-and-dependency-target)
@@ -1242,7 +1243,7 @@ and CommandKit v0.7.0. Native `MessageContentHash` satisfies the cache requireme
typed result handoff and focused inspection enable one application-owned load.
The native resource layout, schema selections, and `OutputContractInput`
API are implemented. Upstream and focused assembled checks passed as recorded
in the plan; the final full acceptance audit remains pending.
in the plan, including successful final full acceptance.
**U2 resolved:** Ordinary embedded assets, prompt-declared output contracts,
native schema-source selection, and removal of duplicate schema/filesystem
@@ -1312,7 +1313,7 @@ manifest, and reporting-only sidecars and migrate consumers to documented paths.
Observer wiring and [debug filenames/layout](#inventory-and-depth) are explicitly
implementation choices, not unresolved architecture or stable debug contracts.
Implemented native observations/capture/publication and reporting tests are
recorded in the plan; final acceptance remains pending.
recorded with successful final acceptance in the plan.
**U10 resolved:** CommandKit versions, capabilities, commands, loaders/preflight,
output, and debug policy are implemented as selected above.