docs(governance): census 02 — has each instrument ever fired? + PENDING-95..98

Closes the scope gap census 01 declared for itself: the seven instruments it
named as uncensused. Pre-registered before any source or config was read,
with predictions and a discrimination condition.

Census 01 asked whether an instrument had a real negative instance — a
question about CAPABILITY. Census 02 asks whether it has ever engaged in
real life. Those come apart exactly at the drift-checker's shape, and
2026-08-04 found the gap six times (retrieval_count = 0 across 19,915 nodes
for four months; two replay modules that have never processed an event).

VERDICT: every instrument a human runs by hand has a rich firing record;
every instrument that runs by itself has none — and the two guarding the
engine's output have no consumer at all. The record divides by whether a
human is in the invocation path, not by age, quality, or importance.

verify-before-compose fired exactly twice (2026-07-17, 2026-07-18), evidence
surviving only in harness transcripts; and it CANNOT fire on 31 of 59 guarded
files, including the live constitution, because it folds the existing file's
contents into its search for the attestation. audit_cruft, verify_conversion
and apply_char_glyphs are exemplary. resolve_archived_source is healthy at
349/349 and has zero log entries. studium verify-quote and
fidelity_equivalence@2 have no production call site at all.

Prediction 5 inverted for the second census running, for a new reason.
Census 01: decay, not construction, is the failure mode. Census 02: the
recording is attached to the human, so an instrument's record vanishes the
moment it is automated — which is when it starts running often enough to
matter.

Two of my own candidate findings died to their controls and are recorded as
such: probing the resolver with engine source_ids against the chamber's
canonical_slug key space (one sentence from "the resolver is inert"), and
reading character_as_image at the wrong YAML nesting (nearly "zero glyph
maps declared"; there are two sources and a 63-item census).

Filed together: PENDING-95 [HARDENING] the hook cannot fire on the
constitution · PENDING-96 [HARDENING] "SILENCE — ✓ warranted" certifies the
index and claims the answer · PENDING-97 [PROPOSAL] FTS AND-s bare tokens
with no semantic layer, recall dies as questions lengthen · PENDING-98
[HARDENING] firing history exists only where a human invokes.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WuMjg3ipEVa3n8CoSzoyvc

claude/memory/session-ledger-2026-08-04.md

@@ -70,3 +70,22 @@ metadata:
 ## Sub-agent dialogues
 
 ## Bypasses
+
+---
+
+# Second sitting — 2026-08-04 (post-clear)
+
+## Returns
+
+- **2026-08-04T13:40 CEST — corrected the inherited resumption path rather than following it.** The wrap named `chamber-library/_curation/fool/census-01-negative-instances-RESULT.md`; that directory does not exist. The census lives at `~/dotfiles/claude/governance/fool/` (RESULT + PREREGISTRATION). Found by `find`, not assumed. A wrap-authored path is a claim like any other; the cheapness of the check is the point.
+
+## Confidence to recalibrate
+
+- **Standing, inherited and unchanged:** *a number that matches a constant is not a cause* — four refutations yesterday, all resting on arithmetic agreement with a code constant. And *knowing the name of a failure class confers no immunity to it*. Both bear directly on today's thread, which is precisely about instruments that report success without ever having engaged.
+- **Not yet substrate-checked:** the 13 open PENDING items were carried from the wake digest, not re-verified against their own disposition. Three were filed today (92/93/94) and are verified by authorship. The other ten are **unverified — last confirmed at filing**.
+
+## Open horizons
+
+- **PULLING THREAD (inherited, confirmed):** census 01 against the seven uncovered chamber/engine gates — `verify-before-compose` · `audit_cruft` · `verify_conversion` · `resolve_archived_source` · `apply_char_glyphs` · studium `verify-quote` · `fidelity_equivalence@2`. Question: has each ever produced a positive result, and does a record exist that could tell us either way?
+- Parked hard: the 2.32 events/min rate (needs a controlled measurement, four theories lost).
+- Awaiting steward: PENDING-92 annotation before its local 3-commit branch moves.