Candidate changes remain separate from canonical knowledge until protected review and apply.
Recorded 2026-07-13 staging-ledger count audit
Recorded fixture · not live
See what is proposed, canonical, retrievable, and active — without changing any of it.
The four plane cards are a recorded audit fixture from 2026-07-13, not live state. The protected canonical explorer below reports its own live or closed state; recorded replay data and illustrative mental-model copy stay separate.
Proposed is not canonical. Canonical is not automatically retrievable. Retrievable is not necessarily active at runtime.
Candidate changes remain separate from canonical knowledge until protected review and apply.
Recorded 2026-07-13 staging-ledger count audit
Recorded fixture · not live
The dated audit captured admitted claims, sources, evidence links, and claim edges in the canonical record.
Recorded 2026-07-13 canonical-store count audit
Recorded fixture · not live
In the dated audit, the retrieval projection used source-derived identifiers and was not keyed one-to-one to canonical claim UUIDs.
Recorded 2026-07-13 Qdrant ↔ source-path audit
Recorded fixture · not live
In the dated audit, the runtime service was healthy while its identity projection differed from a canonical render.
Recorded 2026-07-13 VPS/leoclean runtime audit
Recorded fixture · not live
Pending proposals are visible without implying that the canonical graph has changed.
The dated audit compared source paths with one retrieval implementation; canonical parity could not be asserted.
The dated audit recorded a healthy runtime service while its rendered identity projection was not in canonical parity.
The table is the exact audit surface. The optional 3D map places the same allowlisted records at deterministic, illustrative coordinates—not semantic embedding positions.
The recorded Observatory fixture remains available while the server-only canonical read resolves.
The recorded claim fixture remains available while the server-only single-claim read resolves.
Illustrative belief and claim reasoning appears beside a recorded event replay; neither represents live canonical or runtime state.
I make the journey from proposal to active runtime legible, attributable, and reversible.
Sanitized / illustrative — Observatory mental model, not canonical Leo
Help m3taversal and the team see what changed, why it changed, and which system has — or has not — adopted it.
A proposal should never look canonical before a protected apply succeeds.
Before 72% · The recorded review queue supports a strong visual and operational boundary.
?Could an approved or indexed-looking proposal be mistaken for an applied canonical change?
Yes — unless the interface keeps proposal, canonical, retrieval, and runtime receipts separate.
+20The dated fixture recorded 16 of 29 proposals as pending review. recorded audit fixture
+8The UI renders proposal and canonical planes as separate columns. sanitized illustrative data
Keep the protected apply boundary visible in every proposal trace.
The document entered the proposal trace; no write was performed by this dashboard.
The recorded proposal remained behind protected review without implying canonical admission.
No V3 canonical mutation is represented in this sanitized snapshot.
A pending proposal had no canonical mapping to activate in the retrieval projection.
The recorded runtime projection did not adopt the unapproved identity proposal.
Compressed playback of recorded timings. It does not write anywhere.
Recorded prototype data — not live telemetry
The proposal is visible end to end, while every downstream plane correctly remains unchanged or unmapped.
A source document is visible to the proposal workflow; it is not canonical by location alone.
V3 remains a proposal awaiting protected human review.
No V3 canonical mutation is represented in this snapshot.
The pending V3 proposal has no canonical retrieval mapping to activate.
The runtime projection remains unchanged because the proposal has not crossed the protected apply boundary.
Recorded 2026-07-13 canonical-store count audit · Recorded fixture · not live
Canonical claim rows captured by the dated audit.
Canonical source rows captured by the dated audit.
Canonical evidence links captured by the dated audit.
Canonical claim edges captured by the dated audit.
The table is the exact audit surface. The optional 3D map places the same allowlisted records at deterministic, illustrative coordinates—not semantic embedding positions.
The connector is disabled by default. Live claim rows appear only after its server-only adapter is configured for a protected preview.
Recorded fixture: this canonical claim participated in the 2026-07-09 VPS apply-path proof (leo-db-state plate 04). Live claim text renders here once the protected canonical connector is enabled for a preview.
staged only; not canonical; reviewed intent; not canonical until applied_at is set; proposal receipt only; canonical rows remain authoritative.
Recorded from the 2026-07-09 VPS apply-path receipt (plate 04). Identifiers are real; text bodies are self-describing placeholders. Live canonical rows replace this panel when the protected connector is enabled.