eric/audita
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 6 Wiki Activity

Verify the integrated resilient processing contract

Browse Source
This commit is contained in:
Eric Rakestraw
2026-09-24 18:03:25 +00:00
parent a770c77a23
commit 6523d7ac74
5 changed files with 242 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
docs/roadmap/resilience.md
View File

@@ -2,9 +2,9 @@
**Last updated:** 2026-09-24
**Status:** Target behavior agreed; not implemented. This document defines the
desired end state and user intent. Concrete design decisions and implementation
steps are recorded in [implementation.md](implementation.md).
**Status:** Implemented. This document records the selected behavior and user
intent. Concrete design decisions and completion evidence are in
[implementation.md](implementation.md).
## Purpose and User Intent
@@ -33,20 +33,21 @@ Internal structures and measurements must serve Audita's processing workflow.
The reporting package adapts those outcomes to structured and human-facing
presentations, rather than reshaping processing around a reporting convenience.
## Current Baseline and Intended Change
## Historical Baseline and Implemented Change
The [pipeline](../internal/pipeline.md), [LLM integration](../integrations/openai-compatible-llm.md),
[report assembly](../internal/diagnostics-reporting.md), and
[artifact lifecycle](../operations.md) describe current behavior.
Currently, exhausted structural repairs can become warnings and skipped proposals
or rejected validation batches. Other model runtime failures cancel peer work,
stop subsequent modules, and prevent final transcript output. Successful repairs
appear in execution observations rather than a dedicated recovery classification.
Detailed artifacts are written during ordinary runs and may subsequently be
removed by retention. The working transcript is re-chunked between modules.
Before this work, exhausted structural repairs could become warnings and skipped
proposals or rejected validation batches. Other model runtime failures canceled
peer work, stopped subsequent modules, and prevented final transcript output.
Successful repairs appeared in execution observations rather than a dedicated
recovery classification. Detailed artifacts were written during ordinary runs
and could later be removed by retention. The working transcript was re-chunked
between modules.
This feature deliberately changes those behaviors. It builds on the completed
This feature changed those behaviors. It builds on the completed
[library adoption](library-adoption.md) and [review remediation](remediation.md).
Fatal cancellation remains necessary; unsuccessful model work must be separated
from failures that actually require cancellation of the run.
@@ -278,8 +279,7 @@ volume, and a short reason breakdown. Detailed inspection belongs in YAML or deb
failures, and reporting/debug selections. Preserve domain safeguards, capacity
limits, and redaction.
- Canonical CLI, configuration, operations, integration, internal, and architecture
documentation describes the implemented final behavior. Until implementation,
this roadmap does not change their current implemented contracts.
documentation describes the implemented final behavior.
## Implementation Reference