Pilots
Real adoption evidence, operation records, and case reports. These answer “what actually happened when X was tried?”
Pilots are labeled field evidence — not canonical content. AletheIA is domain-agnostic (see ADR-006). The pilots below were the first concrete instances of the patterns the framework codifies; they document what happened, not what must happen. Crisis Monitor is the first validation case, not the canonical reference — other consumer projects across other domains are expected.
Operation closeouts (session/task records from Hermes and other runtimes) live in closeouts/.
What NOT to put here: prescriptive guides on how to run a pilot (those go in guides/). A pilot document reports what happened; it does not instruct.
Contents
| Document | What it records |
|---|---|
| pilot-crisis-monitor.md | First real product adoption — Crisis Monitor |
| migration-from-crisis-monitor.md | Operational boundary between Crisis Monitor pilot and standalone AletheIA |
| context-graph-decision.md | Decision record with real test data (3 controlled tests on Crisis Monitor codebase) |
| resource-aware-crisis-monitor-reference.md | Bounded 1.2-track reference using Crisis Monitor evidence |
| resource-aware-operations-review.md | Consolidation of what the 1.2 track proves |
| report-core-operating-path-friction-test.md | Friction test: is core-operating-path.md sufficient for first use? |
| visual-operations-pr-193-retrospective.md | Retrospective reconstruction of PR #193 using the Visual Operations vocabulary |
| visual-operations-usage-pr-200-dogfood.md | First dogfood usage record: PR #200 snapshot supported a post-merge no-new-infrastructure decision |
| visual-operations-usage-pr-201-dogfood.md | Second dogfood usage record: PR #201 snapshot confirmed static closeout utility and no activation threshold met |
| visual-operations-usage-pr-207-dogfood.md | Third dogfood usage record: PR #207 confirmed human-review unavailable is a source-bound design signal, not a UI failure |
| visual-operations-adaptive-skills-dogfood.md | First full-pipeline checkpoint: a real Adaptive Skills execution record becomes a read-only Resource Observatory signal |
| Visual Operations phase closeout | Closure evidence and activation gates after PRs #193–#197 |
Cycle records
Periodic development logs — what shipped in a given cycle, open backlog references in upstream repos, parallel workstreams. Distinct from pilot reports (which test a hypothesis) and closeouts (which conclude a bounded operation).
| Document | What it records |
|---|---|
| dev-handoff-2026-05.md | Cycle record — May 2026 (delivered: AletheIA PRs #120, #123 / Adaptive Skills PRs #21, #23; backlog tracked in upstream issues) |
In flight
| Pilot | Status | Brief |
|---|---|---|
| Crisis Monitor overlay adoption (Epic 7) | Handed off to Crisis Monitor team; friction log pending | guides/pilot-crisis-monitor-overlay-handoff.md |
| Visual Operations AletheIA dogfood | Open for real-use evidence; usage records pending | guides/visual-operations-aletheia-dogfood-protocol.md |
The friction log will land here as pilot-crisis-monitor-overlay-adoption.md once the pilot reports back. Until then, see the brief in guides/ for the test plan and log template.
Closeouts
closeouts/ contains individual operation records from the Hermes pre-pilot and other bounded execution sessions. Each file follows the closeout template.