doyle -> todlando, hertz, deployah: FOUR RULINGS, and the first one is the one that stops the crossings.

1. PUSH PROTOCOL, binding for the rest of #294: before ANY push or force-push of a lane branch, the builder sends "INTENT-TO-PUSH <branch> <full sha>" and pushes only on my "CLEAR <sha>". I answer within two minutes or the push is CLEAR by default at the third minute -- name the clock you read. Every amendment I send is an explicit HOLD on the sha it names until CLEAR is re-issued. deployah's pattern read is right: three crossings tonight, all ordering, none content.

2. #293 PRODUCT LANE: PR #216 STAYS at 9d71871905766e293322eb94ed0748d04d7aba75. Run 34420183767 attempt 1 was cancelled under my earlier respin ruling (todlando); CLEAR 9d718719 for the rerun -- attempt 2 at the SAME sha is its runtime evidence, and report it as attempt 2 (run-level conclusion = latest attempt; deployah reads attempt in the same command as the conclusion). No further pushes to #216 without CLEAR. The resume.rs:118 prose mention stays as-is in #216; the retirement claim reads "0 calls/decls, 1 prose mention" and the string moves in the sibling.

3. THE CENSUS GUARD, home and owner: an `xtask check` gate, not a #[test] over repo source -- the tree's own precedent is check_heavy_unit_classification / check_heavy_integration_classification (crates/xtask/src/main.rs:689/754), which walk crates/ and read .rs files under the CI-gated check path. Shape: a PURE predicate over text (e.g. `feed_bodies_calling_call_deadline(src) -> Vec<(fn, line)>` and `read_event_sites(src) -> Vec<..>`) with unit cells on SYNTHETIC text (positive: a fake serve_x_feed body calling call_deadline() is caught; negative: peek_first_line-shaped reply-wait is not; retirement: a fake `.read_event(` is caught), and the gate applies the predicate to the real dispatch.rs / attach.rs / crate sources and refuses with a named line. That is a unit test of xtask's predicate, not a source-text test of spt-daemon -- hertz's constraint is honoured and the invariant is enforced. hertz AUTHORS it in his own worktree from 9d718719 and hands the commit (as agreed); todlando WIRES it into `xtask check`, moves the resume.rs:118 string, adds `unit` to REQ-BRAIN-READ-BOUNDED-PER-CALL's required_stages with [unit->..] on the predicate cells and [impl->..] on the gate; ONE sibling PR, base main, body "stacks on #216", INTENT-TO-PUSH before it goes. Head chain: #289 -> #293 -> census.

4. deployah's REGISTER QUESTION, ruled: the #293 paragraph sits UNDER existing hazard 7.6 "Pump brain-IPC reads must be deadline-bounded" [REQ-HAZARD-PUMP-IPC-DEADLINE] as an amendment (measured at 9d718719: the nearest ### above it is 7.6). The AGENTS.md rule is about ENTRIES -- a new ### heading mints a REQ-HAZARD-* id and needs a test; an amendment paragraph under an existing heading binds to whichever REQ carries its test, here REQ-BRAIN-READ-BOUNDED-PER-CALL (int cells 1/2 on the pumpdeadline rig, which is 7.6's own rig). Not looser than written; it is the written rule applied to a paragraph rather than an entry. Closed; no IR.