System Status: Warming Up
Checking system health.View status
Kahramana
Checking session
Digest

What changed on the public proof ledger.

Built for repeat visits: items currently in the digest window, rows still collecting checkpoints, newly completed outcomes, visible losses, and guarded or blocked setups—without flattening Alpha, Watch, and proof layers.

Public proof uses stored hashes and IDs. Losses and blocked posture stay in-bounds when data exists.
Hashes and verification IDs on published rowsLosses and blocked posture stay in-boundsNo retroactive edits to locked public payloads
Why revisit this page

A fast scan of posture shifts and checkpoint state for the public slice—no implication that every row is Alpha-class or execution-ready.

Losses stay listed with the same rules as radar and performance
Guarded / blocked rows remain part of the recap
Still-tracking rows show what is awaiting checkpoints
Integrity warnings surface when the stored record demands it
Secondary readDaily recapPublic recapBuckets below summarize posture shifts; they are not the live radar feed.
May 18, 2026, 16:24
Rows in window10
Still tracking6
Completed checkpoints5
Losses / caution2
Secondary readWeekly recapPublic recapBuckets below summarize posture shifts; they are not the live radar feed.
May 18, 2026, 16:24
Rows in window10
Still tracking6
Completed checkpoints5
Losses / caution2
Highest-attention rows today

Ranked from stored digest metadata: active, recently completed, or higher-score items that justify a second look—not every Watch-tier row.