MEM-STARTUP · pass
Startup read order
Active startup memory remains explicitly ordered and routes detailed evidence through the pointer ledger.
Open evidenceActive memory plus durable evidence
The dashboard verifies that .uai remains current first-load memory while detailed reviewed material remains under docs/long-term-memory.
MEM-STARTUP · pass
Active startup memory remains explicitly ordered and routes detailed evidence through the pointer ledger.
Open evidenceMEM-MIRRORS · pass
Every canonical active UAI record has a byte-identical public mirror.
Open evidenceMEM-POINTERS · pass
Every pointer-ledger path and section anchor is expected to resolve in release validation.
Open evidenceMEM-SOURCES · pass
Canonical reports retain source hashes, rendered anchors, and durable source copies.
Open evidenceMEM-SUPERSESSION · pass
Claim timelines preserve registered states and append review, correction, contradiction, and supersession events.
Open evidenceMEM-RELEASE · pass
Current active memory routes to 1.6.6-wip while historical release records remain preserved.
Open evidenceMEM-ROOT · pass
The root availability decision, safe policy boundary, and implementation evidence are linked.
Open evidenceAgents load the active UAI startup index first. The pointer ledger routes to detailed reports and decisions only when needed. Durable memory augments active memory; it never disables or replaces it.
Permanent product boundary