[PROPOSAL] Daemon result restated as structural; dormancy claim narrowed (PENDING-152 A1)

Jurist corrections on receipt. No numbers change; what a later reader can do
with them does.

(a) The daemon finding is structural, not a build note: there is no unqueued,
ungated tick available in this architecture. Two independent failures —
delivery-time gating survives generation-time decoupling, and the residue must
be dropped (equivalent to event-gating) or queued (a backlog is state). The
same objection landing twice by unrelated paths is the signature of a limit
rather than an excuse.

(b) My dormancy claim was narrower than stated. The instrument measures gaps in
the EVENT STREAM; I read them as gaps in PRESENCE. Those diverge exactly on the
case §8 aimed at — present and thinking, not generating events, which is when
drift consolidates. Recorded as unmeasured. Fifth instance this week of an
instrument's reach mistaken for a claim's subject; four of five caught by
another party naming the limit.

(c) The proportions condition was met by dissolution, not compliance — recorded
that way so an unchanged number does not read as a condition ignored.

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

PENDING.md

@@ -4123,3 +4123,45 @@ Not dismissed. Costed, and the cost is not the reason it fails.
 
 **Files affected:** none yet. No implementation; §4 order and the transport-not-voice line both hold.
 **Awaiting:** steward and jurist on the 20-minute interval and on the daemon rejection.
+
+### AMENDMENT 1 — 2026-08-22 — the daemon result is a FINDING; the dormancy claim is narrowed; the condition was dissolved, not met
+
+**Jurist, on receipt.** Three corrections to how PENDING-152 states its own results. None change a number; all change what a later reader can do with them.
+
+#### (a) ⚠ THE DAEMON RESULT IS STRUCTURAL — restated as a finding, not a build note
+
+The spec must not read *"we accepted a compromise on cost grounds."* It must read:
+
+> ⚠ **THERE IS NO UNQUEUED, UNGATED TICK AVAILABLE IN THIS ARCHITECTURE.** A daemon decouples the tick at **generation** time, but the delivery surface — the status line — re-renders on session activity, so the gate is **relocated, not removed**. And the residue must go somewhere: **dropped** is behaviourally identical to event-gating at the price of a daemon; **queued** is a backlog, and a backlog is state, which is the exact hazard for which the hard cap was rejected — arriving, additionally, in a burst at session start.
+
+**The two failures are independent, and that is the point.** Generation-time decoupling does not survive delivery-time gating; and separately, the residue has nowhere to go that §8 permits. **The same objection landing twice by two unrelated paths is the signature of a structural limit rather than an incidental one.**
+
+**This is the difference between a limitation and an excuse.** The first is actionable by a later reader — it tells them what to check if the architecture changes (a time-driven delivery surface would reopen it). The second tells them only what we felt like doing.
+
+#### (b) ⚠ THE DORMANCY ARGUMENT IS NARROWER THAN I STATED — an unmeasured case, declared
+
+PENDING-152 says *"a tick that can't fire into an empty room has lost nothing."* **True for between-session gaps. NOT established for the case §8 was actually aimed at:** a long session where the steward is **present and thinking but not generating hook events** — reading, drafting in another window, away from the keyboard mid-problem.
+
+**That is precisely when drift consolidates, and precisely when the tick will not fire.**
+
+⚠ **My instrument cannot see it.** It measures gaps in the *event stream* and I read them as gaps in *presence*. Those two quantities diverge exactly on the case that matters. p90 = 17.5 s bounds the distortion **during active work**; it says nothing about presence without activity, because no event is emitted by a steward who is reading.
+
+**Recorded as UNMEASURED, not as covered by the data.** Fifth instance this week of the same family — an instrument's reach mistaken for a claim's subject (three-store negative · `find` vs `glob` · `55 files` · the dry run that bypassed its own normalization · this). **Four of the five were caught by another party naming the limit rather than by the executor re-checking**, which is the disclosure-of-scope mechanism the correction record names, doing the work Constraint 6 attributes to difference of formation.
+
+*If it needs measuring later:* nothing in the transcript can supply it. It would need a presence signal independent of the event stream — terminal focus, keystroke activity — which is a larger and more intrusive instrument than the question currently warrants.
+
+#### (c) The proportions condition was met by DISSOLUTION, not by compliance
+
+REVIEWED-125 deferred the re-derivation requiring **adjusted proportions**, on the assumption that the burst problem persisted. **It does not.** 73/20/7 was calibrated against a time-uniform tick, and restoring the generator restores their calibrated meaning; adjusting now would correct for a defect that no longer exists.
+
+**Recorded as dissolved rather than met, so the next reader knows why the number is unchanged** — an unexplained unchanged number reads as a condition ignored.
+
+#### Accepted as filed
+
+**20-minute tick — accepted by the jurist**, including the one-way adjustment path: §8 licenses lengthening if it reads as noise, so starting at 30 would require a shortening the path does not permit.
+
+#### Next act on this item
+
+**Run the status-line experiment before any body is built.** Ten minutes; settles §8a's design and REVIEWED-125 cond. 2; the difference between a body that idles visibly and one that only appears to.
+
+**Awaiting:** nothing on (a)–(c). The status-line experiment is the executor's next act and needs no ruling.