From b001b1b11de58c4a08ced8774ce971b449fe2696 Mon Sep 17 00:00:00 2001 From: type-two Date: Wed, 29 Jul 2026 13:01:22 +1000 Subject: [PATCH] [ui] note v9.3: notice.pos stays out of the fax, by? is next round's firewall log Co-Authored-By: Claude Fable 5 --- fktry/lanes/LANE-UI.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/fktry/lanes/LANE-UI.md b/fktry/lanes/LANE-UI.md index 002e1ee..fb9a07c 100644 --- a/fktry/lanes/LANE-UI.md +++ b/fktry/lanes/LANE-UI.md @@ -861,3 +861,11 @@ Re-verified against HEAD rather than against my own commit: survive a broken verb. Rewritten to carry no verb that has to agree: "A CLEAN COPY OF YOUR SHIPPED FIRST. THE LEDGER IS SATISFIED." — which also states the mechanic. Pinned with a plural-item test. + +**v9.3 note (landed as I pushed):** `notice.pos?` and `repaired/mirrored by?` are +RENDER's cues and my lane re-verified clean against them (tsc clean, 277 green). I am +deliberately **not** surfacing `notice.pos` anywhere in the fax: the round-7 ruling is +that a notice gives no grid reference, and the field existing for the renderer's +materialisation cue doesn't change what the paper is allowed to say. `by?` is the first +thing that could make the FIREWALL LOG per-UNIT rather than per-tile (round 6's honest +compromise) — happy to take that next round if you want it.