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

Document completed Phase 6 diagnostics

Browse Source
This commit is contained in:
Eric Rakestraw
2026-05-11 14:03:14 +00:00
parent 5217093be2
commit db880ed868
2 changed files with 49 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
docs/architecture.md
View File

@@ -14,8 +14,8 @@ Implemented today:
- Transcript and glossary parsing/validation.
- Deterministic transcript normalization.
- Deterministic token estimation and transcript chunking.
- Per-run diagnostics directory creation plus basic artifacts.
- Minimal process report JSON output.
- Per-run diagnostics directory creation plus Phase 6 process-level artifacts.
- Process report JSON output with diagnostics artifact references.
- Framework foundation packages for contracts and proposal application.
Not implemented in CLI runtime path today:
@@ -196,16 +196,35 @@ Current per-run artifacts include:
- `normalized-transcript.json`
- `normalization-summary.json`
- `chunking-summary.json`
- `invocation.json`
- `effective-config.json` (redacted credentials)
- `report.json`
- `error.log` on failure
`--report-json` writes a separate report file when requested.
Current process reports include diagnostics metadata references for:
- diagnostics directory path;
- source transcript artifact path;
- parsed source transcript artifact path;
- normalized transcript artifact path;
- normalization summary artifact path;
- chunking summary artifact path;
- invocation metadata artifact path;
- redacted effective-config artifact path;
- error-log artifact path on failure.
Retention modes implemented in `ApplyRetention`:
- `always`: keep successful runs
- `never`: remove successful runs
- `auto`: currently same as `never` for successful runs
- failed runs are always retained
- `always`: keep all run directories.
- `never`: keep successful run directories.
- `auto`: keep failed runs and successful runs with skipped corrections.
- failed runs are always retained.
Current runtime note:
- module execution is not implemented yet, so successful runs generally have no skipped corrections and `auto` typically removes clean successful run directories.
Intentionally deferred to module/LLM phases:
- module prompt/response diagnostics artifacts are not produced yet because module execution and LLM calls are not in the runtime path.
## Current tests and quality posture
Implemented tests currently cover: