Align the roadmap and runtime documentation

This commit is contained in:
2026-11-17 03:57:22 +00:00
parent fd65d9ca1e
commit 1bc54a405c
4 changed files with 23 additions and 17 deletions

View File

@@ -1,7 +1,8 @@
# Audita Reliability and Maintainability Roadmap
**Date:** 2026-11-15. **Status:** target state defined; implementation pending.
**Baseline:** `730c1e4`; application code is unchanged from the audited `c4ccd78`.
**Date:** 2026-11-15. **Status:** [Implementation landed](implementation.md).
[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
@@ -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
[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,
ordinary reports, and opt-in debug artifacts. This work improves those paths and
adds processing progress. It does not redesign editorial policy or the public
configuration schema. The D1 architecture-policy update is complete; its code
cleanup and the other accepted remediation remain to be implemented.
ordinary reports, and opt-in debug artifacts. The sprint improved those paths
and added processing progress. It preserved editorial policy and the public
configuration schema. The D1 architecture-policy update preceded the related
code cleanup.
### Design boundaries
@@ -419,11 +420,10 @@ of test counts for evidence of the selected outcomes.
## Completion and audit coverage
The roadmap is complete when the target behaviors above are implemented and
verified, the obsolete mechanisms are removed, and canonical documentation
describes the resulting application. The coverage map accounts for every catalog
entry, including closed and superseded remedies; it does not authorize those old
remedies. Record implementation evidence against the target sections as work lands.
The [implementation plan](implementation.md) records the landed changes and
verification. The coverage map accounts for every catalog entry, including
closed and superseded remedies. The [assessment](audit/assessment.md) records
which remedies were selected.
| Target area or disposition | Catalog entries |
| --- | --- |

View File

@@ -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)
**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.
**Evidence:** The [feature roadmap](reliability-and-maintainability.md) still