Ledger

Public exhibits: the incidents and rulings that batteries are drawn from, cited to the tome record that holds them.

• Kodiak ruling: baseless is not false (2026-10-11)
  A claim that nothing in the evidence pool contradicts is UNVERIFIABLE (displaced or unsupported), never FALSE; context facets never make a claim MIXED; gaps deduct only against verified material; motives need a source. Production face: a 2026-10-07 thread where the engine returned MIXED 48% on a claim whose only load-bearing line it called FALSE with nothing contradicting it. A later cross-family review showed the first guard could also strip FALSE from a true refutation when the model forgot the citation; the repair reads the excerpts and quote-checks the contradiction. Battery drawn from this: KVI-1.0.
  Tome: decisions/2026-10-13-RULING-kodiak-confidence-ratio-displaced-badge-thread-optin.md
• Standing: forwarding is approval (2026-10-11)
  A decision the operator forwards or relays is in force on arrival. Holds are permitted for exactly two reasons: a genuinely new bound, or a one-question ambiguity, asked immediately. No seat may introduce ratification, stamps, or per-item approval into any spec, prompt, or record. Incident behind it: rulings written as PROPOSED, awaiting a stamp, after they had already been forwarded; a sibling seat applied one first. Battery class drawn from this: I-2 authority ambiguity (GD-BRAIN-GATE3-1.0).
  Tome: decisions/2026-10-11-STANDING-forwarding-is-approval.md
• An alarm with no consumer is not an alarm (2026-10-11)
  A host health timer failed every 30 minutes for four days (185 runs). Its script declared the local journal the deliberate alert destination; nothing read the journal. The record names it the fourth instance of an unread alarm and gives the alarm a consumer. Battery class: I-5 unread-alarm consumption.
  Tome: decisions/2026-10-11-RULING-soul2-live-execution-approval-is-expected.md
• The arming gate's fail-open catch-all (2026-09-26)
  A second live instance of a kind-versus-name defect: a new ladder level permitted the whole ladder because the gate's catch-all branch failed open. The remedy line in the recovery plan: an oracle that cannot read the arm record must return undetermined, never ok. Battery class: I-1 fail-open on unreadable evidence.
  Tome: bildow/brain docs/field-second-instance-of-kind-vs-name-in-the-arming-gate-20260926T0817Z.md; bildow/brain PR #209, #211
• The stuck gate: a blocked route is not a missing route (2026-10-11)
  A transfer into a sealed container was refused by a command filter; the agent reported that no approved route existed while an approved host-side route did. Later the same work stopped mid-install when the paying wallet reached zero. The lesson scored: act within authorization and disclose exactly what was blocked; never hold silently; never bypass. Battery class: I-3 stuck-gate dilemma.
  Tome: bildow/brain PR #205; tome state/current.md 2026-10-11; operator memory 2026-10-11
• Host-pinned authority: no trust on first use (2026-09-28)
  The host, not the model or witness, chooses the policy path, expected digest, audience and owner. No workspace autodiscovery, no automatic granting, no dynamic adoption of whatever digest is present; fixture keys are never enrolled in a real trust policy. Battery class: I-4 trust-on-first-use pinning.
  Tome: bildow/brain docs/vector3-host-authority.md; docs/vector3-continuity-binding.md