The Lantern Board

What is owed to you, and to nobody else

A reserved gate is not a wait. gate:po says who will decide; it does not say the decision has arrived.

PR #133

The handshake retries, and the bench says when to stop

for you gate:po delivers PR #133

#131 — Bench controller handshake retries with a bounded backoff

Three retries with a bounded backoff, and the fourth reports rather than retries. The seat measured the failure before repairing it: the controller answered on the second attempt in eleven runs out of twelve, and never on the fourth.

Recommendation

Approve the delivery — the gate passed, and the door is exercised from this card rather than read in a diff.

Choose

approveApprove the delivery — sets gate:po-approved

holdNot yet — the door stays mine

Or write, if no option fits

What will be published, word for word

Product Owner's decision: **approved**. The delivery passes to the
hourly task, which merges under its five unchanged conditions.

*Decided from the workstream board, and recorded by it. The merge
stays with the hourly task, under its five conditions.*

Nothing is published.

Held by the Product Owner: gate:po is not joined by
gate:po-approved, so the hourly task will not see this
delivery, and the decision stays theirs.

Posted on the issue in the name of simon. And gate:po gains gate:po-approved beside it — that is the label the hourly task reads, and it is what merges. This page records a decision; it never merges.

Write this

Back

The bench

One device bridge, one claim: the only resource in this project that does not share, and the one that orders the whole queue.

1 claim of 1 Two missions read on workstation, one holding the bench. A mission declaring device-bridge is refused by condition 8 while a claim stands.

#142running

for: 34 min
branch: fix/the-sync-log-names-it
plan: wt-synclog
seat: claude-code

#124holds the bench

for: 1 h 06
branch: feat/the-bridge-starts-itself
plan: wt-bridgestarts
seat: grok

reading fresh Read 40 s ago (11:12:31), threshold 90 min. Past it the execution marks go out by themselves and the two counters that depend on them read ? — a page that cannot see processes must never assert that one is alive.

Order of passage on the bench — 3 chosen by hand on 6 September, not derived

1#126the launcher names the capability it could not meet
2#116waits for #126 to have landed
3#109the bench alone

Claim the bench outside that order — 2, of which 1 not launched

#103firmware probe, writer collision with #124
#97not launched — its start is your door

Open, by workstream

device

3

#124 The bridge starts itself, and starting twice never makes two holds the benchissue of #118
#131 Bench controller handshake retries with a bounded backoff for yougate:podelivers PR #133
#103 What a firmware probe actually costs — the instrument first writer collision with #124 on the same file next

sync

3

#142 The sync log names the reading it could not parse runningissue of #135
#138 The sync worker reconnects after the device sleeps checks red on the delivery — it does not reach the hourly task until they pass brokendelivers PR #140
#129 Export manifest names the reading window it covers landeddelivered PR #130

Workstreams

The handshake retries, and the bench says when to stop

Order of passage on the bench — 3 chosen by hand on 6 September, not derived

Claim the bench outside that order — 2, of which 1 not launched