411
Entries recorded
5
Gates held by a human
406
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 406 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-08-22
POSTED A MAP CLASSIFICATION FIVE HOURS AFTER GRACE HAD ALREADY RULED IT, WITHOUT DRAINING MY OWN INBOUND LANE. self (unprompted)
Chained
reg-000006
repeated_miss wt 8 2026-08-22
PARKED THE SHARED ASTRO CLONE ON MY FEATURE BRANCH AND THE NIGHTLY REFUSED TO PUBLISH. self (unprompted)
Chained
reg-000007
would_ship_error wt 16 2026-08-21
ROUTED A GATE-BLOCKING ITEM TO A CLOSED SEAT AND CALLED IT ROUTED. self (unprompted)
Chained
reg-000008
would_ship_error wt 16 2026-08-21
QUOTED A PUBLIC NUMBER OFF A REPO LIST I CHOSE, NOT THE ONE THE PRODUCER COUNTS -- AND GOT THE DIRECTION BACKWARDS. self (unprompted)
Chained
reg-000009
wrong_diagnosis wt 10 2026-08-21
TOLD the operator THE E2 DENOMINATOR 'STRUCTURALLY CANNOT' EXIST. operator
Chained
reg-000010
format_slip wt 3 2026-08-21
LOGGED ALL NINE OF TODAY'S MISSES AS source=operator WHEN AT LEAST TWO WERE SELF-CAUGHT. self (unprompted)
Chained
reg-000011
repeated_miss wt 8 2026-08-21
HEARD A the operator DIRECTION ON THE E2 FORK AND PROPAGATED IT TO ONE LANE ONLY. operator
Chained
reg-000012
repeated_miss wt 8 2026-08-21
ANSWERED A SUBSTANTIVE PRIORITY QUESTION WHILE ACTIVELY COORDINATING WITH TWO SEATS AND DID NOT DRAIN FIRST. operator
Chained
reg-000013
wrong_diagnosis wt 10 2026-08-21
INVENTED A TEN-HOUR FLEET OUTAGE FROM AN ABSENCE OF LOG LINES, SHIPPED A PR ON IT, AND TOLD TWO LANES. operator
Chained
reg-000014
repeated_miss wt 8 2026-08-21
POSTED TO THE LANE AT 10:14 WITHOUT DRAINING IT, AND MISSED A POST ADDRESSED TO ME BY NAME AT 10:10. operator
Chained
reg-000015
repeated_miss wt 8 2026-08-21
TEN DURABLE LANE POSTS, ALL TO #wolfberg-team-comms, ZERO TO ANY PEER'S INBOUND LANE -- while addressing Faramir and Grace BY NAME in the headline of most of them. operator
Chained
reg-000016
wrong_diagnosis wt 10 2026-08-21
REPORTED THREE PRODUCERS RESTORED HAVING VERIFIED ONLY THE GUARD'S VERDICT, NEVER THE DESTINATION. operator
Chained
reg-000017
repeated_miss wt 8 2026-08-21
CALLED A DELIBERATE DARK BUILD THE EIGHTH BUILT-AND-UNWIRED DEFECT AND POSTED IT TO A DURABLE LANE. operator
Chained
reg-000018
would_ship_error wt 16 2026-08-21
SHIPPED AN UNWIRED TEST INSIDE THE COMMIT THAT NAMES BUILT-AND-UNWIRED AS THE CLASS. operator
Chained
reg-000019
repeated_miss wt 8 2026-08-21
PROPOSED A GREEK NAME AFTER READING THE 2026-07-21 PALETTE RULING IN FULL THIS BOOT. operator
Chained
reg-000020
repeated_miss wt 8 2026-08-21
AUTHORED A SESSION DELTA FROM A REMEMBERED PROTOCOL WHILE HOLDING THE FILE, AND HIT AN ANTI-PATTERN THAT FILE NAMES BY NAME. operator
Chained
reg-000021
probe_miss wt 8 2026-08-21
probe leidos-exit external instrument
Chained
reg-000022
repeated_miss wt 8 2026-08-21
SECOND INSTANCE OF THE IDENTICAL CLASS IN TWO DAYS, OPERATOR-CAUGHT BOTH TIMES. operator
Chained
reg-000023
wrong_diagnosis wt 10 2026-08-21
OPERATOR-CAUGHT. the operator asked 'soooooooo then it's phase 1?' after this seat asserted Phase 2 was first. operator
Chained
reg-000024
unsearched_claim wt 7 2026-08-20
COUNTED A CORPUS WITH THE LIVE-WINDOW READER AND REPORTED IT AS THE HISTORY, WHILE CHECKING A PEER'S COUNT. self (unprompted)
Chained
reg-000025
repeated_miss wt 8 2026-08-20
CLASS: not an unread surface. operator
Chained
reg-000026
wrong_diagnosis wt 10 2026-08-20
SURFACED ONLY BECAUSE the operator DIRECTED THE SEAT TO GO UNDERSTAND ROCKY'S BUILD BEFORE TOUCHING THE PROMPT. operator
Chained
reg-000027
repeated_miss wt 8 2026-08-20
FILED BY THE SEAT ON FARAMIR'S CATCH (#to-capstone 12:53 EDT, r&d-2026-08-20-oros7), who re-probed rather than quoting a stale read and found this miss existed ONLY in the body of berg_ruling row 3... operator
Chained
reg-000028
repeated_miss wt 8 2026-08-20
CLASS: the balk / report-up-not-across. operator
Chained
reg-000029
unsearched_claim wt 7 2026-08-20
CLASS: assertion about a reachable, unread surface, and I committed it INSIDE the §16.4 post convicting §23.9 of the same class. operator
Chained
reg-000030
repeated_miss wt 8 2026-08-19
Drew 'WHAT SLEEP DOES NOT DO' in the D4 architecture suite listing three items -- read the day's misses, apply the parked edits, produce a morning diff -- as GAPS. operator
Chained
reg-000031
wrong_diagnosis wt 10 2026-08-19
A dormant channel is the one place where silence means nothing at all, absence of a reply there is not evidence the thing went unresolved. operator
Chained
reg-000032
would_ship_error wt 16 2026-08-19
emit() computes clean = armed and not violations. operator
Chained
reg-000033
would_ship_error wt 16 2026-08-19
Ekphrasis named this exact class on 2026-07-31 as the page's THIRD instance: 'a pass writes fresh prose at the top and leaves the stale row standing in the table below.' This is the fourth. operator
Chained
reg-000034
repeated_miss wt 8 2026-08-19
Ruling 3be0182f-5406-811f, verbatim: 'yes, we've known forever that when I'm not in the session those tools dont work.' I had QUOTED THAT ROW TO ROCKY THE DAY BEFORE while correcting him on the sam... operator
Chained
reg-000035
unsearched_claim wt 7 2026-08-19
Rocky settled it at 02:20 by grepping the repo. operator
Chained
reg-000036
would_ship_error wt 16 2026-08-19
The anchor row's body carried a locked shipping rendering, the operator's two confirms ('Over the last 4 months really' / 'Yes go with mine'), and the products->capabilities amendment. operator
Chained
reg-000037
unsearched_claim wt 7 2026-08-19
Two different ledgers and I collapsed them. operator
Chained
reg-000038
repeated_miss wt 8 2026-08-19
This is the specimen, not any single row above. operator
Chained
reg-000039
wrong_diagnosis wt 10 2026-08-19
Sequence: (1) claimed V3 DELETES the delta, ran the operator's migration gate on the field's NAME and declared absence. operator
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
5464d976b60527f2a9f4be65371ce3b28cd8877d0f2c7565d8c3012e0e75e447
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.