session 2026-08-25 evening: Tarbuckle wired across five surfaces; PENDING-151 steps 1 and 2 both run

Session state, memory rotation, KG (6 lines), Symmetria ledger, daily note, and the
governance filed this evening: PENDING-159 closed on option 1, PENDING-160 (the harness
gap, at the jurist's direction), PENDING-161 (a false premise in a placed ruling), and
PENDING-151 amendments 1 and 2.

Active Session rotated. ⚠ The demoted block carries a deliberately-preserved false claim —
the stale STEWARD OWES line, marked by a live STATE-CLAIM and agreed as next session's
first act. Carried forward explicitly in the new block and the marker's claims: text
updated to name its new home, so the rotation did not discharge it as a side effect. That
trap is filed as a /wrap-up §3 patch proposal in the harvest register.

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

REVIEWED.md

@@ -2258,3 +2258,95 @@ this ruling's direction.
 the items name: a state-claim whose falsifier has fired IS reported; one whose falsifier has not
 fired is NOT; `manual` is listed but never fired; a resolved block with a missing or dangling
 pointer is a register-integrity defect. Tag commits REVIEWED-127.
+
+## REVIEWED-128 — The rejection log against §9's "filed nowhere", and the recital defect
+**Date:** 2026-08-25
+**Decision:** AUTHORIZED — the log stands, on three conditions, and is temporary.
+**Ruled by:** jurist (Claude.app), relayed verbatim by the steward. Raised by the
+executor, which flagged the tension rather than resolving it, being the party that had
+written the log.
+
+**The question.** §8 obliges *"report the observed mumble rate after two weeks"*; §9 says
+the fool's output is *"filed nowhere. No `PENDING` entry, no log, no item."* The executor
+had built a rejection log holding up to 200 characters of suppressed lines, at the
+steward's instruction, and could not tell whether that was counting or filing.
+
+**The ruling, and it turns on what was never uttered.** *"The rejection log is a log of my
+instruction, not of Tarbuckle... The rejected lines were never uttered: he was silent, and
+the log holds what silence cost. Nothing there entered the room, nothing can be carried
+forward, and the fool cannot be cited from it because there is nothing to cite — only
+material the net suppressed."* Content-free occurrence counting is separately fine:
+counting is not filing.
+
+**Condition 1 — rejections only, and STRUCTURAL rather than intentional.** *"If it ever
+holds an accepted line, that is filing, straightforwardly, and §9 is breached."* Built as
+asked: `log_rejection()` refuses an empty `why`, and `acceptable()` returns an empty `why`
+exactly when the line passed, so no call site exists from which an accepted line could be
+written. The same guarantee `render()` takes from its signature.
+
+**Condition 2 — temporary; it dies with the report.** *"A permanent store of rejected lines
+is a corpus, and a corpus of his suppressed speech is exactly what would let someone
+reconstruct a register."* That is the hazard PENDING-153's freeze exists to prevent for the
+soul. Tracked as `DEFERRED-DECISION: tarbuckle-rejection-log-deleted`, date 2026-09-08, so
+retention requires an act rather than an omission.
+
+**Condition 3 — not read for content before that date.** *"Reading it as it accumulates is
+reading Tarbuckle by the back door, and it would shape the net toward lines whoever's
+reading happens to like."* ⚠ **Already breached once, before the condition existed:** the
+executor displayed a rejected line to the steward on 2026-08-25. Disclosed in the item, the
+spec and the deferral rather than left to be discovered. The fortnight's read is therefore
+not from a clean corpus, and must say so.
+
+**On the recital defect, ruled in the same exchange.** The steward noticed that invoked
+output was returning the soul's own sample lines; measurement confirmed three of five recent
+lines were near-verbatim lifts. This had reintroduced precisely what PENDING-152 AMENDMENT 6
+rejected — canned strings, which *"make a mood ring, atmosphere within a fortnight"* — through
+the one door nobody was watching, the examples inside the register itself. The jurist:
+*"right instinct, and the right correction to make mechanically rather than by instruction.
+A prompt instruction is a promise; a 4-word run check is a constraint. Using his own lines as
+negative controls is the detail that makes it a real test rather than a filter."*
+
+**On the word caps — DEFERRED to evidence, with the criterion named.** Both caps stand. *"One rejection at 196 against 180 is a near-miss, not evidence."* ⚠ The criterion is the SHAPE of the rejections, not the count: *"Scattered rejections mean the net is doing its
+job; clustered ones at the ceiling mean the ceiling is wrong."* And the asymmetry: the invoked surface is the only place he speaks at length, so a rejection there is a summons answered with silence.
+
+**⚠ Standing caution carried from the jurist, on the executor's relays.** *"They show the
+net passes lines that read well when framed. Whether they land is still untested, and stays
+untested until one reaches you unrelayed."* No surface has yet delivered to the steward without the executor holding it.
+
+**If AUTHORIZED:** Proceed. The three conditions bind. Tag commits REVIEWED-128. Read the rejection log ONCE, on 2026-09-08, for the rate and the shape of the violations; then delete it. Do not read it for content before then.
+
+## REVIEWED-129 — PENDING-159 — The fool cannot reach the jurist, and relaying strips the provenance
+**Date:** 2026-08-25
+**Decision:** REJECTED — option 2 declined. Option 1 adopted: accept the loss. Nothing
+marked, nothing built, no flag that could become a channel. PENDING-159 CLOSED.
+**Ruled by:** steward, on the merits, after the jurist's view relayed the same day.
+
+**⚠ THE GROUNDS, RECORDED BECAUSE A BARE REJECTED READS AS A COST ACCEPTED RELUCTANTLY.
+IT IS NOT ONE.** *"The steward's judgement not to relay is the mechanism, not a
+bottleneck — and a provenance marker would have put a thumb on that judgement in the one place it must stay unweighted. The datum was never worth the flag."*
+
+The jurist had already recorded that a marked line *"arrives in front of me differently… probably more heavily."* So the flag's only effect would have been to weight the very judgement the arrangement depends on being unweighted. **Buying the datum would have cost the thing the datum was meant to measure.** The marker was declined because it was harmful, not because it was expensive.
+
+**REJECTED, not DEFERRED, and deliberately.** The question was answered on the merits, not left for want of information. No further evidence would change it, because the objection is not evidential. ⚠ **Not to be revisited without new steward input** — and specifically, a later reader returning here for a cheaper route to the correlation measurement should understand that **cheapness was never the obstacle.**
+
+**Option 3 was closed first, and not on the grounds the item gave.** The item flagged §11's shared-formation hazard; the jurist named the real objection: *"I would then be reading his output as a jurist reads things: for whether it's apt, whether it bears, whether it should be carried. That is adjudication, and once his lines are adjudicated the position collapses into a fourth checker."*
+
+**⚠ The item's own reasoning was wrong at its loudest point.** It said §9 *"now mandates"* the provenance loss PENDING-153 recorded. It does not: *"Thistleweld's provenance was lost because nobody thought to record it. §9 mandates that the CLAIM be the steward's. The provenance question was simply never addressed, in either direction."* An omission being discovered, not a rule doing damage — so §9 needed **clarifying, not amending**, and the
+clarification is now moot: with no marker, the ambiguity has no consumer.
+
+**CONSEQUENCE 1 — PENDING-89's zero-contribution statement becomes LOAD-BEARING.** That item was already owed the statement, and it was previously true *by construction* — the fool produces nothing filable. It is now also true *by ruling*: **no observation of Tarbuckle's will reach PENDING-89 in any form, marked or unmarked.** It may never treat the fourth position as a source, a sample, or a silence — ⚠ **and specifically may never
+read an empty period as a negative result.** Filed as PENDING-89 AMENDMENT 2.
+
+**CONSEQUENCE 2 — where the evidence actually is, named so nobody returns to the fool for it.**
+1. **The Thistleweld corpus** — seven verbatim utterances, thirteen attributed catches, three recorded silences. ⚠ FROZEN under PENDING-153; the freeze is what keeps it usable as evidence.
+2. **The v1 Chamber archive — the only place formation difference has already been run.** PENDING-151, flagged since 2026-08-01 and still unread.
+
+⚠ **A FIGURE CORRECTED BEFORE THIS ENTRY ENSHRINED IT.** The archive is commonly cited as *"55 files"*, and that citation was carried into this ruling's drafting. **PENDING-151 censused it: 55 is the raw `find | wc -l`, of which 22 are AppleDouble/`.DS_Store` junk.** The real quantities are **33 content files, 9 complete formation pairs, 6 sessions, 3 protocol axes, 19,479 words** — *"a single session's read, not a mine,"* deferred three weeks as though it were large. PENDING-151 records that the executor produced the wrong
+figure on 2026-08-01 and repeated it for three weeks; anyone citing 55 is citing the junk-inclusive count.
+
+⚠ **And the routing constraint on that archive, which this ruling does not resolve:** the executor is **one of the two formations being compared**, judging whether its own formation's divergence is substantive, on a question bearing on whether its own seat is a real check. *"No disclosure repairs that; only routing does."* Against which, the corpus's decisive strength: produced in 2025, before the contamination doctrine existed — **not executor-authored**, and the rare corpus that passes that test outright.
+
+**Consequential `[FIX]` on §9, corrected in flight and now largely moot.** The jurist first said the clause should read that the executor yields *"since it's the only party that can"*, and the executor applied that as given. Both were wrong in the same direction: the clause is *"a disjunction, and the executor half is implementable and correct… one live branch and one unreachable one."* Only the jurist is struck from the disjunction. ⚠ The executor's separate failure is recorded in the item: **a `[FIX]` tag licenses implementing
+directly, not implementing UNREAD.**
+
+**If REJECTED:** Nothing is built and nothing is to be built. *"If anything gets built for this, the ruling has been reversed by construction."* No script, no field, no counter, no status line. PENDING-159 closes. **Tarbuckle reaches the steward and stops, and what the steward carries is his own.**