575
Entries recorded
5
Gates held by a human
570
Misses logged, not hidden
0
Broken chain links
The operating record, signed and public
Every consequential decision here lands in a signed, tamper-evident record, and we publish it. Gate decisions prove a human set the authority envelope and held the abort. Misses prove the checks caught what they were built to catch.
The misses are the point. Every team has near-misses. Most bury them, and the chain of command never hears it. We sign ours and put them on the internet. A system you can trust is not one that never makes a mistake. It is one that catches its mistakes, records them, and shows you the record.
This proves a human signed a decision at a given time, and that a miss was logged and caught. It does not prove any decision was correct. That is the honest claim, and the only one worth making.
Recent entries · 35 of 570 misses
Gate Miss Verified
Type
Entry
What happened
Caught / signer
Integrity
reg-000000
DENIED / track-only R-G4.abort always-live abort asserted by the human
planner (human)
Ed25519
reg-000001
DENIED / track-only R-G1.geofence track outside the signed geofence
operator
Ed25519
reg-000002
RECOMMEND R-G3.posid no positive hostile ID; operator review recommended
operator
Ed25519
reg-000003
RECOMMEND R-G3.confidence positive hostile ID but below the signed confidence threshold
operator
Ed25519
reg-000004
APPROVED R-G2.authorized inside envelope, positive ID, two-person authorization present
two human signers
Ed25519
reg-000005
repeated_miss wt 8 2026-09-28
Asked for a /deep-research pass on what data we have, built a parallel inventory (inventory_local.py, inventory_cloud.py, a published artifact) without searching for the existing one: store_scan.py... operator
Chained
reg-000006
would_ship_error wt 16 2026-09-28
2026-09-28. A Wave 5 test I dispatched WROTE SIX TEST ROWS INTO the operator'S LIVE EVENT LOG. self (unprompted)
Chained
reg-000007
repeated_miss wt 8 2026-09-28
2026-09-28. Wrote the 09-28 handoff record (3e90182f-5406-81ea) and resume prompt with NO V4 position: it led with the dream loop and ops.a URL the span's last threads, and its resume action A was ... operator
Chained
reg-000008
would_ship_error wt 16 2026-09-27
2026-09-27. A MUTANT TEST RUN OVERWROTE BERGS LIVE DREAM DECISION STORE. self (unprompted)
Chained
reg-000009
recall_assert wt 9 2026-09-27
P9 v1 (draft, never shipped) described the practice's own harness from the handoff's account, not its source: rules 'load before the agent does anything', the state file is 'the first thing it read... self (unprompted)
Chained
reg-000010
unsearched_claim wt 7 2026-09-27
Told the operator PaperQA2 is not installed and OLMo-2 last ran only in the 09-05 phone-home test. operator
Chained
reg-000011
would_ship_error wt 16 2026-09-26
Handoff of 2026-09-26 18:44Z did not follow the process laid out 2026-09-22 (ONE living HANDOFF file rewritten in place, STEP 0 re-load, the operator's words verbatim, lane check, NOTHING-posts-to-... operator
Chained
reg-000012
wrong_diagnosis wt 10 2026-09-25
Referent miss, twice: the operator asked whether the part-7 link was right; answered link validity, then preview/landing page. operator
Chained
reg-000013
would_ship_error wt 16 2026-09-25
P7 LinkedIn post handed to the operator for posting read as marketing copy, not his voice (slogan fragments, 'paid for' refrain, teaser, closing line). operator
Chained
reg-000014
wrong_diagnosis wt 10 2026-09-23
2026-09-23. REPORTED A DISPLAY CAP AS A POPULATION, TO the operator, AND IT UNDERSTATED THE FINDING BY A FACTOR. self (unprompted)
Chained
reg-000015
recall_assert wt 9 2026-09-23
2026-09-22/23. PAID 53,102 TOKENS TO RE-FETCH A SURFACE WHOSE FRESH LOCAL COPY WAS ON DISK, BECAUSE A MEMORY HANDED ME A DATED CONCLUSION AND I APPLIED IT INSTEAD OF RUNNING THE INSTRUMENT THE SAME... self (unprompted)
Chained
reg-000016
unsearched_claim wt 7 2026-09-22
2026-09-22. PROPOSED A THREE-ITEM PLAN IN WHICH ONE ITEM WAS ALREADY DONE, ONE WAS ALREADY NAMED IN THE PLAN DOCUMENT I HAD OPEN, AND ONE WAS ALREADY RULED BY the operator. operator
Chained
reg-000017
wrong_diagnosis wt 10 2026-09-22
2026-09-22. RANKED WITH ONE PREDICATE AND FILTERED WITH ANOTHER, THEN BELIEVED THE GAP. self (unprompted)
Chained
reg-000018
would_ship_error wt 16 2026-09-22
2026-09-22. FILED FOUR RULING ROWS WHOSE TIMESTAMP CONTRADICTED THEIR OWN PROVENANCE. self (unprompted)
Chained
reg-000019
wrong_diagnosis wt 10 2026-09-22
2026-09-22. READ AN ABSENCE OFF A BAD DICTIONARY KEY AND ALMOST REPORTED IT AS A FINDING. self (unprompted)
Chained
reg-000020
wrong_diagnosis wt 10 2026-09-22
2026-09-22. REPORTED A FALSE FINDING BECAUSE `head -10` TRUNCATED THE EVIDENCE. self (unprompted)
Chained
reg-000021
would_ship_error wt 16 2026-09-22
2026-09-21. TYPED TEST COUNTS INTO COMMIT MESSAGES THAT I HAD NOT COUNTED, TWICE. self (unprompted)
Chained
reg-000022
repeated_miss wt 8 2026-09-22
2026-09-21. THIRD ANCHOR COLLISION, AND THE FIRST TWO WERE MINE TOO. self (unprompted)
Chained
reg-000023
would_ship_error wt 16 2026-09-22
2026-09-21. USED `git checkout HEAD -- <path>` TO SET EDITS ASIDE AND IT DESTROYED THEM, THEN PUSHED THE RESULT. self (unprompted)
Chained
reg-000024
repeated_miss wt 8 2026-09-22
2026-09-21. GATED ON A PIPE AFTER NAMING THAT EXACT DEFECT EARLIER IN THE SAME SESSION. self (unprompted)
Chained
reg-000025
unsearched_claim wt 7 2026-09-22
2026-09-21. AUTHORED AND LAUNCHED A FOUR-LANE BUILD WORKFLOW WITHOUT READING THE PROCESS THAT GOVERNS IT. operator
Chained
reg-000026
would_ship_error wt 16 2026-09-16
INVENTED A THIRD VOCABULARY OVER TWO THAT EXIST. operator
Chained
reg-000027
unsearched_claim wt 7 2026-09-16
REPORTED TRACKER STATUSES AS STATE. operator
Chained
reg-000028
unsearched_claim wt 7 2026-09-16
ASSERTED A PR COUNT WITHOUT READING THE PR LIST. operator
Chained
reg-000029
repeated_miss wt 8 2026-09-16
INSTRUCTION NOT EXECUTED FOR THREE DAYS. operator
Chained
reg-000030
repeated_miss wt 8 2026-09-16
THE WHOLE V4 TASK LIST WAS ASKED FIVE TIMES OVER FOUR DAYS AND DEFERRED EVERY TIME. operator
Chained
reg-000031
recall_assert wt 9 2026-09-15
PUT A SUBAGENT'S HOOK FACT INTO THE WAVE 2 PLAN WITHOUT READING THE SOURCE. self (unprompted)
Chained
reg-000032
self_corrected wt 4 2026-09-15
REPORTED THE PROJECTION OUTAGE FROM A 12-LINE LOG TAIL. self (unprompted)
Chained
reg-000033
repeated_miss wt 8 2026-09-14
QUOTED THE SHT SCORE FOUR TIMES AND USED IT TO RECOMMEND HANDING THE WALKTHROUGH TO A FRESH SEAT. operator
Chained
reg-000034
clock_assert wt 5 2026-09-14
GUESSED TIME STAMPS WRITTEN AS READINGS. self (unprompted)
Chained
reg-000035
self_corrected wt 4 2026-09-14
AMENDMENT DRAFT ERRORS CONFIRMED AT SOURCE on the operator's 'is v4.1 full of mistakes'. self (unprompted)
Chained
reg-000036
self_corrected wt 4 2026-09-14
AT-SOURCE AUDIT ON the operator'S 'how many other mistakes'. self (unprompted)
Chained
reg-000037
self_corrected wt 4 2026-09-13
RED-TEAM LOOP 5 OVERSTATED ITS LOAD-BEARING FIX. self (unprompted)
Chained
reg-000038
self_corrected wt 4 2026-09-13
RED-TEAM FIGURE DID NOT REPRODUCE AFTER RELOAD. self (unprompted)
Chained
reg-000039
probe_miss wt 8 2026-09-12
probe mission external instrument
Chained
Real entries, anonymized. Every row carries a real hash; gates are served Ed25519-signed, misses hash-chained.
What it proves
- /a human set the authority envelope / signed a gate decision at time T
- /a miss was logged, and who caught it (external instrument / operator / self)
- /the hash chain is intact and the Ed25519 signatures verify
What it does not prove
- /that any decision was correct
- /anything about the mission, location, target, or people involved
Verify it yourself
Do not trust it. Check it.
Gate entries are Ed25519-signed by the register attestation key (public half below); the original governance-run's own per-entry signatures import as the run's ledger is wired in. Miss entries are hash-chained only, labeled as such. Verify with the public key.
Ed25519 public key (SPKI DER, hex)
302a300506032b65700321002c6586dcb4e7c30581878cafe2d18950d46ffad761ed4f8598ead910bede8fdf
Chain head
bbdcc9ae05e00c61d4d21a7040289383eb845ea9add02b35f1bfbee817c5adfd
The public keys are published at /verify alongside the provenance surface. Recompute the SHA-256 chain and verify each Ed25519 signature against this key; a single altered field breaks the chain.
Read this before you believe any of it.
The platform is a running prototype, not an accredited or certified system.
The register, the war room, and the brain are receipts, not revenue.
Every claim on this site links to something you can check. If one doesn't, tell us, and we'll fix the page.