Add output schema registry and public contract docs
This commit is contained in:
@@ -398,6 +398,27 @@ The second command should use the same redaction behavior as run diagnostics.
|
||||
|
||||
Document and implement the stable boundaries that external callers can rely on for 1.0.
|
||||
|
||||
## Implementation status (2026-05-13)
|
||||
|
||||
This workstream is now partially implemented in the repository:
|
||||
- output schema registry is implemented with supported schemas:
|
||||
- `bare-segments` (default);
|
||||
- `audita-v1`;
|
||||
- `audita process --output-schema <name>` is implemented;
|
||||
- versioned file config supports `output.schema`;
|
||||
- process reports include explicit report metadata with:
|
||||
- report schema name/version;
|
||||
- selected output schema;
|
||||
- config file version when a file config is used;
|
||||
- public contract documentation and output schema documentation are now present in:
|
||||
- `docs/public-contract.md`
|
||||
- `docs/output-schemas.md`
|
||||
|
||||
Current intentional gap:
|
||||
- `seriatim-intermediate` remains deferred because no concrete implemented contract exists yet.
|
||||
|
||||
This status update only applies to output schema/report metadata/public contract documentation. Validator refactors, prompt-asset registries, scheduler utilization diagnostics, correction ledgers, and generated summaries remain planned.
|
||||
|
||||
This phase should happen early because Audita is both a user-facing CLI and a subprocess dependency. The public contract should guide the remaining implementation decisions rather than merely documenting them after the fact.
|
||||
|
||||
## Public contract document
|
||||
|
||||
Reference in New Issue
Block a user