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

Refactor validators into built-in registry chains

Browse Source
This commit is contained in:
Eric Rakestraw
2026-05-13 18:36:46 +00:00
parent 1bc5936681
commit d6126bf52b
21 changed files with 559 additions and 83 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/roadmap.md
View File

@@ -511,6 +511,20 @@ Add explicit report schema metadata, for example:
Make validators as easy to reason about as modules.
## Implementation status (2026-05-13)
This workstream is now implemented for built-in validator composition:
- first-class built-in validator registry exists in `internal/validators`;
- stable validator keys are defined and used for built-in chains and runtime validator names;
- explicit built-in module validator-chain definitions are implemented and resolved through registry-backed chain wiring;
- production module constructors use built-in chain resolution instead of ad hoc manual validator construction;
- runner execution preserves deterministic ordering (deterministic validators before LLM-backed validators);
- report validator decision/rejection records now carry stable validator keys.
Current boundary:
- validator chains are built-in and not user-configurable.
- prompt-asset registries, prompt metadata, scheduler utilization diagnostics, correction ledgers, and generated summaries remain planned.
Validators are now central runtime components. They are reused across modules, have deterministic and LLM-backed implementations, produce diagnostics, and affect final correction acceptance. They should therefore have stable identities, registry metadata, and composable chain definitions.
## Package structure