diff --git a/claude/memory/session-2026-09-10-the-scoping-sitting.md b/claude/memory/session-2026-09-10-the-scoping-sitting.md
index 3263aab..25223e8 100644
--- a/claude/memory/session-2026-09-10-the-scoping-sitting.md
+++ b/claude/memory/session-2026-09-10-the-scoping-sitting.md
@@ -211,3 +211,32 @@ item at the end of a wrap, it has been lost.
 > ⚠ **The failure that will look like success:** finding a defect in this week's entries.
 > They are audited. **A "cannot be checked" answer is the valuable one**, and it is the
 > likely one — today's drafts lived in chat and are already gone.
+
+
+---
+
+## POST-WRAP — the steward noticed the wrap was silent, and the record answers it
+
+**Asked, not starved.** `2026-09-10T20:55:43 wrap silent` in `tarbuckle-draws.jsonl`, with
+`tarbuckle-wrap-fired` stamped the same minute. The seam fired, consumed its occasion,
+generated, and the net or the timeout took the line. He was not mute or off — two `aside`
+utterances spoke earlier (19:02, 20:03).
+
+⚠ **AND THE REASON IS STRUCTURALLY UNRECOVERABLE.** `log_rejection` is inert under
+REVIEWED-136 AMD 1 condition G, so the *why* was never written. `log_event` recorded the
+occurrence — content-free, as designed — which is the only reason we know he was asked at
+all. Ceiling, banned pattern, soul recital or 15-second timeout: gone.
+
+**That field is `reason_category`, PENDING-182's second, a closed enum and content-free by
+construction.** It is drafted and not ruled. ⚠ **One instance is not the case for the
+proposal and the proposal does not rest on it** — but it is the first time the gap has
+surfaced in something the STEWARD noticed rather than something the executor measured, and
+it arrived on the day the proposal was drafted.
+
+⚠ **The `[FIX]` is exonerated by the record, not by reasoning about it:**
+`log_event("wrap", "silent")` is written well past the child gate, after the generation
+returns, so the gate blocked nothing.
+
+⚠ **AND A THIRD NULL TAKEN AS FACT, caught before reporting.** The first `ls ~/.claude/state`
+printed nothing through a pipe and I nearly reported the directory empty. It holds seven
+files. **Third instance in one sitting of a null result that was a fact about the query.**