AletheIA — Quality Baseline v1
Objective
This document formalizes AletheIA entering quality Phase 3.
In plain language:
after vision, contracts, kernel, and governance, the framework must prove automatically that:
- its contracts remain intact;
- its core behaviors remain stable;
- its minimum flow still works end to end.
Three minimum alpha proofs
1. Contract tests
These verify whether the framework’s minimum artifacts still have the expected structure.
In the alpha, this mainly covers:
- core contracts;
- governance artifacts;
- required minimum fields.
2. Golden tests
These verify whether reference behaviors remain unchanged.
In the alpha, this covers:
- the
allowpath forhello-world; - the
reviewpath for low confidence; - the
ask_humanpath for critical risk; - the
blockpath for governance failure.
3. Minimum E2E
This verifies whether the integrated flow still closes:
kernel -> governance hook -> policy evaluation
What this phase aims to prove
- contracts did not break silently;
- reference scenarios remain stable;
- the framework remains coherent from start to finish.
Important rule
The alpha does not need to start with a heavy test suite.
It only needs a small but reliable baseline that prevents invisible regression.
Implementation in this iteration
Main scripts
scripts/aletheia/test-contracts.tsscripts/aletheia/test-goldens.tsscripts/aletheia/test-e2e.tsscripts/aletheia/test-learnings.ts
Reference fixtures
docs/examples/aletheia/goldens/*.jsondocs/examples/aletheia/learning-from-failed-validation/*
Additional coverage in this iteration
learning-from-failed-validationscenario;- generation of a
Learning Recordfrom aPolicy Evaluation; - proof that validation failure can become useful learning instead of only a block.
Recommended next step
After this expanded baseline:
- consolidate the initial documentation for the public repository;
- prepare the extraction blueprint for
AletheIA; - separate what belongs in
framework core,starter-pack, andpilot materials.