Align the roadmap and runtime documentation
This commit is contained in:
@@ -41,7 +41,8 @@ The application configuration scope uses ConfigKit's native effective values,
|
|||||||
source evidence, explanation, comparison, and redaction. PromptKit supplies its
|
source evidence, explanation, comparison, and redaction. PromptKit supplies its
|
||||||
own configuration and resource scopes and request preparation, validation, and
|
own configuration and resource scopes and request preparation, validation, and
|
||||||
explicit smoke diagnostics. Inspection does not require a processing-ready
|
explicit smoke diagnostics. Inspection does not require a processing-ready
|
||||||
pipeline or contact a provider. Processing preflight separately checks the selected\nprofiles and glossary entries. Smoke tests can contact providers and are run
|
pipeline or contact a provider. Processing preflight separately checks the selected
|
||||||
|
profiles and glossary entries. Smoke tests can contact providers and are run
|
||||||
only on explicit request.
|
only on explicit request.
|
||||||
|
|
||||||
Process stdout contains transcript JSON when no output file is selected. Ordinary
|
Process stdout contains transcript JSON when no output file is selected. Ordinary
|
||||||
|
|||||||
@@ -45,10 +45,11 @@ in the returned output only when debug capture is requested. A work unit can
|
|||||||
complete with model errors and applied corrections. Recoverable model failures
|
complete with model errors and applied corrections. Recoverable model failures
|
||||||
never trigger shared cancellation. Fatal failures and parent cancellation stop
|
never trigger shared cancellation. Fatal failures and parent cancellation stop
|
||||||
further dispatch and join active workers. The initiating error carries its
|
further dispatch and join active workers. The initiating error carries its
|
||||||
processing phase and available origin. Work-unit evidence preserves each peer's
|
processing phase and available origin. With ordinary reports enabled, work-unit
|
||||||
interruption or error. The runner drains active outcomes and assigns indices
|
evidence includes available peer interruption details. The runner drains active
|
||||||
to usable proposals from later sections even when it could not validate them. The
|
outcomes and assigns indices to usable proposals from later sections even when
|
||||||
working transcript advances only at the module's successful commit boundary.
|
it could not validate them. The working transcript advances at the module's
|
||||||
|
successful commit boundary.
|
||||||
Earlier committed text remains available to an interrupted run, and transcript
|
Earlier committed text remains available to an interrupted run, and transcript
|
||||||
delivery requires successful processing.
|
delivery requires successful processing.
|
||||||
|
|
||||||
|
|||||||
@@ -1,7 +1,8 @@
|
|||||||
# Audita Reliability and Maintainability Roadmap
|
# Audita Reliability and Maintainability Roadmap
|
||||||
|
|
||||||
**Date:** 2026-11-15. **Status:** target state defined; implementation pending.
|
**Date:** 2026-11-15. **Status:** [Implementation landed](implementation.md).
|
||||||
**Baseline:** `730c1e4`; application code is unchanged from the audited `c4ccd78`.
|
[Post-implementation findings and their status](remediation.md) track follow-up work.
|
||||||
|
**Planning baseline:** `730c1e4`; its application code matched the audited `c4ccd78`.
|
||||||
|
|
||||||
## Purpose and scope
|
## Purpose and scope
|
||||||
|
|
||||||
@@ -20,12 +21,12 @@ Earlier source-audit remedies remain proposals where the assessment supersedes
|
|||||||
them. This document specifies the target state and accepted scope. The
|
them. This document specifies the target state and accepted scope. The
|
||||||
[implementation plan](implementation.md) owns the sequence and verification.
|
[implementation plan](implementation.md) owns the sequence and verification.
|
||||||
|
|
||||||
The current application already has native library integration, preflight,
|
The baseline already had native library integration, preflight,
|
||||||
ordered module execution, partial-success validation, bounded correction repair,
|
ordered module execution, partial-success validation, bounded correction repair,
|
||||||
ordinary reports, and opt-in debug artifacts. This work improves those paths and
|
ordinary reports, and opt-in debug artifacts. The sprint improved those paths
|
||||||
adds processing progress. It does not redesign editorial policy or the public
|
and added processing progress. It preserved editorial policy and the public
|
||||||
configuration schema. The D1 architecture-policy update is complete; its code
|
configuration schema. The D1 architecture-policy update preceded the related
|
||||||
cleanup and the other accepted remediation remain to be implemented.
|
code cleanup.
|
||||||
|
|
||||||
### Design boundaries
|
### Design boundaries
|
||||||
|
|
||||||
@@ -419,11 +420,10 @@ of test counts for evidence of the selected outcomes.
|
|||||||
|
|
||||||
## Completion and audit coverage
|
## Completion and audit coverage
|
||||||
|
|
||||||
The roadmap is complete when the target behaviors above are implemented and
|
The [implementation plan](implementation.md) records the landed changes and
|
||||||
verified, the obsolete mechanisms are removed, and canonical documentation
|
verification. The coverage map accounts for every catalog entry, including
|
||||||
describes the resulting application. The coverage map accounts for every catalog
|
closed and superseded remedies. The [assessment](audit/assessment.md) records
|
||||||
entry, including closed and superseded remedies; it does not authorize those old
|
which remedies were selected.
|
||||||
remedies. Record implementation evidence against the target sections as work lands.
|
|
||||||
|
|
||||||
| Target area or disposition | Catalog entries |
|
| Target area or disposition | Catalog entries |
|
||||||
| --- | --- |
|
| --- | --- |
|
||||||
|
|||||||
@@ -173,6 +173,10 @@ Keep the existing exact-ID and unknown-field tests for both input envelopes.
|
|||||||
|
|
||||||
### R5 — Align Roadmap Status and Runtime Guidance (P3)
|
### R5 — Align Roadmap Status and Runtime Guidance (P3)
|
||||||
|
|
||||||
|
**Complete.** The roadmap points to the landed implementation and follow-up
|
||||||
|
review. The pipeline guide describes available peer evidence in reporting mode.
|
||||||
|
The CLI guide renders the preflight sentence normally.
|
||||||
|
|
||||||
**Affected plan:** Stages 15, 19, and 20.
|
**Affected plan:** Stages 15, 19, and 20.
|
||||||
|
|
||||||
**Evidence:** The [feature roadmap](reliability-and-maintainability.md) still
|
**Evidence:** The [feature roadmap](reliability-and-maintainability.md) still
|
||||||
|
|||||||
Reference in New Issue
Block a user