Changelog
Read the product-level evolution summary and find the canonical technical change record for AletheIA.
This is a concise guide to meaningful AletheIA evolution. The complete technical record, including maintenance and status-only changes, remains in the canonical CHANGELOG.md.
Version 1.0.0 — stable operating baseline
Released 2026-04-09Version 1.0 established AletheIA as a portable operating overlay for bounded, reviewable AI-assisted work.
1.x evolution highlights
| Area | Reader-facing change | Status |
|---|---|---|
| Domain governance | AI Agent Security and Web App Security packs became reusable advisory guidance. | Delivered as manual guidance |
| Evidence posture | Real S28/S29 usage records and sufficiency reviews clarified what counts as evidence. | Delivered; reusable controls remain evidence-gated |
| Observability | Resource and Work Observatory guidance established source-backed read-only projections. | Delivered baseline; expansion remains gated |
| Documentation | Blume Pages validation, output audit, publication smoke tests, English policy, and a progressive public journey improved access to the corpus. | Delivered; publication stays manual |
| Continuity and learning | Restart, context-hygiene, cross-repository compatibility reviews, and the governed pilot report template clarified future boundaries. | Delivered as manual/review guidance; pilot report template is Markdown guidance, not schema authority |
How to read technical changes
Not every repository change is a product release. The technical changelog can include:
- evidence capture and status reconciliation;
- documentation repairs;
- dependency maintenance;
- small validation or source-link fixes;
- closed reviews that preserve a blocked boundary.
Use it when you need exact history. Use the Current state page when you need to know what is safe to claim or use now.