Failure Atlas (diagnosis history and cross-trajectory patterns)
JARVIS keeps an atlas of past failures and the patterns they share, so it can recognise a repeat.
LIVE-PROVEN , rung 6 of 8 Recorded 23 September 2026. Advanced Systems branch, not merged into production.
Technical
What it is
RegressionQueue.experience_patterns (jarvis/maintenance/sentinel.py) and Failure Atlas routes (jarvis/maintenance/commands.py); belief marked INFERRED_FROM_REPORTS.
Truth ladder
Where it stands
Rung 6 of 8: LIVE-PROVEN
A bounded probe ran the real code path on a booted JARVIS on the real machine and recorded evidence. The project treats live evidence as expiring after 24 hours, so every live reading here shows the date it was taken.
Qualified as PARTIAL: part of this capability is not at the rung shown.
Project record: LIVE-PROVEN, PARTIAL
- CONCEPT Designed or specified. No working code yet.
- IMPLEMENTED Code exists. Nothing has demonstrated that it behaves correctly.
- TESTED Automated tests exercise it in isolation, often against fixtures.
- INTEGRATED Wired into the rest of JARVIS and tested across component boundaries.
- PRODUCTION-REACHABLE The owner can reach it through the real runtime path, not only through a test harness.
- LIVE-PROVEN A bounded probe ran the real code path on a booted JARVIS on the real machine and recorded evidence. The project treats live evidence as expiring after 24 hours, so every live reading here shows the date it was taken.
- FORMALLY VERIFIED Its critical property is checked by a proof or exhaustive verification.
- RELEASE-QUALIFIED Passed every qualification gate for a named release.
Limits
Limitations
- Patterns are advisory and labelled as inferred from reports, never as proof of cause.
- Proven on an isolated diagnostic core with synthetic test fixtures, not on the owner’s everyday runtime.
Record
Status history
- INTEGRATED , rung 4 of 8 Recorded state: INTEGRATED_TESTED_OWNER_API_LIVE (handoff); IN-PROGRESS (matrix)
- LIVE-PROVEN PARTIAL , rung 6 of 8 Failure patterns derived from real failed controlled missions survived a restart; a contradicting report removed a pattern.
Only states recorded in the public export are listed. Earlier states may exist in the project’s private ledgers.
Connected work
Connected work
- Changelog Obsidian projection of project memory and a Failure Atlas 22 Sept 2026
- Roadmap Merge Advanced Systems into production INTEGRATING
Neighbours
Related capabilities
- Async event bus An internal message bus lets every part of JARVIS announce what it is doing.
CAP-RT-02· LIVE · OBSERVED · as of 2026-09-17 ·docs/ledger/CAPABILITY_TRUTH.json#CAP-RT-02 - Correlation IDs across every surface Every request carries one tracking ID so its whole journey can be traced.
CAP-RT-03· LIVE · OBSERVED · as of 2026-09-17 ·docs/ledger/CAPABILITY_TRUTH.json#CAP-RT-03 - Health & readiness probes JARVIS can report whether it is healthy and ready.
CAP-RT-07· LIVE · OBSERVED · as of 2026-09-17 ·docs/ledger/CAPABILITY_TRUTH.json#CAP-RT-07 - Resource governor (CPU/GPU/RAM admission) JARVIS rations CPU, GPU and memory so heavy work can't starve the conversation.
CAP-RT-11· IMPLEMENTED · TESTED · as of 2026-08-06 ·docs/ledger/CAPABILITY_TRUTH.json#CAP-RT-11