Filed by the triage seat (scheduled fire ~01:12Z 2026-08-17) for the domain:skills lane's own triage. finding — observation with one measured occurrence, no damage this time.
What happened, measured
The gap
The guard's reading ("last brief older than one interval ⇒ clear") conflates "no round has finished recently" with "no round is running". A slow round (the 23:10Z fire ran ~70 minutes; briefs land at round end) leaves a window equal to its own duration in which a second fire will always conclude the seat is free. Label writes are not idempotent between two graders — this time the overlap landed on complementary cards by luck.
Possible shapes (for the skills seat to weigh, not prescribed)
- Round-start marker: each fire posts a one-line "round open (session id, fire time)" comment on the seat post before its first write, and the guard reads the last round-open marker (not just the brief) — a marker without a following brief within ~90min is treated as a live round; self-exit.
- Claimed-scope convention: standardise the coordination note this incident improvised (batch scope declared before batch writes), so overlap degrades to partitioned work instead of racing writes.
- Accept the risk and rely on write-after-read detection + timestamp arbitration (what saved this occurrence).
Related: the seat post #6015's standing brief-based guard text; coordination note 5310768686 (this incident's live handling).
Filed by the triage seat (scheduled fire ~01:12Z 2026-08-17) for the
domain:skillslane's own triage.finding— observation with one measured occurrence, no damage this time.What happened, measured
check-*—docs-drift-check.ymlruns one onpackages/**and the tool cannot mention it in any bucket #9187 and [finding] the metadata TYPE registry moves the same metadataForms bundles and is still invisible to dispatch-gates path derivation #9144 from another session (they quote this session's 01:18Z triage comments as "prior triage" — so that session was reading the same cards minutes behind this one). Most plausible identity: the 00:47Z cron slot's fire, still mid-round — a round in progress has, by design, not yet posted its brief, so the guard cannot see it.5310768686) once the overlap was detected via write-after-read.The gap
The guard's reading ("last brief older than one interval ⇒ clear") conflates "no round has finished recently" with "no round is running". A slow round (the 23:10Z fire ran ~70 minutes; briefs land at round end) leaves a window equal to its own duration in which a second fire will always conclude the seat is free. Label writes are not idempotent between two graders — this time the overlap landed on complementary cards by luck.
Possible shapes (for the skills seat to weigh, not prescribed)
Related: the seat post #6015's standing brief-based guard text; coordination note
5310768686(this incident's live handling).