Proof Ledger

Open Proof Ledger to see how much of your team's work has been captured without a single screenshot, and check whether that record is still intact.

Who this is for

Anyone signed in can open Proof Ledger (it isn't hidden behind a special menu), but seeing what's inside needs the permission that reads the ledger, and none of the default roles besides Owner carry it. A manager or member who opens the page without that permission sees a message that they don't have access, not a list of edges. An owner can grant the permission to another role if they want someone else to see it.

What you'll see

• A badge next to the page title reading Chain verified or Chain broken, once the ledger has loaded.
• A short line explaining the idea: work is recorded as signed, typed edges instead of screenshots, and no frame of your screen is ever stored.
• Three tiles below that. A Locked constant tile shows frames stored: a count that can never rise, because this way of tracking work never takes a screenshot in the first place. An Edges captured tile shows the total number of typed work edges logged for your org. A work_edge chain tile repeats the chain's health as Verified or Broken, with a Continuous or Broken pill beside it.
• A short note on why this is different from screenshot-based monitoring: no growing archive of screen images is kept anywhere.
• If your org has any history yet, a Recent edges list underneath: each row shows what happened (for example opened, reviewed, committed, merged, or commented), what it was about, the day it happened, how many independent witnesses have backed it up, and an evidence-tier pill: Asserted, Corroborated, or Hardware attested. If there's no history yet, this list simply doesn't appear.

What happens next

An edge starts out Asserted: a single signal with no evidentiary weight on its own. When an independent system of record, like a linked pull request or ticket, backs it up, the edge is promoted to Corroborated and its witness count goes up. An edge only appears once something actually happened. Its absence is never treated as proof that work didn't happen.

If it doesn't work

• "Couldn't load the Proof Ledger": the page failed to load; select Retry.
• If you don't hold the permission that reads the ledger: "No access to this ledger" / "You don't have access to this org's Proof Ledger."
• Any other failure shows the server's own message, or, when your session itself is the problem: "Your session may have expired, or you don't have access to this."

Related

• Outcomes (overview)
• Certificates
• Check whether the ledger is still intact
• See how much work the ledger captured