Skip to content
quarry Check-in [78fbef9d30]
Login

Check-in [78fbef9d30]

Overview
Comment:ops: say what the forge is doing, not just how fast

The panels were steady-state numbers and said nothing while a fleet came up — which is the window an operator most wants to watch and the one where a forge most looks hung. A multi-repo re-ingest on this fleet was mistaken for a hang precisely because nothing said '23 of 25 stores ready' while it worked.

A phase banner leads the page: starting, indexing, syncing or rest, with stores ready over stores served, artifacts this session, the slowest recent round, and the names of what is rebuilding — which, not merely that something is.

Derived rather than tracked. Every store already reports Indexing, LastOK, LastCount, Total and Stalled; a phase field somewhere would be one more thing to keep true. The test ordering is the reader's priority: rebuilding outranks syncing, and a store that has never finished a round outranks both.

A stalled store is DONE waiting — it needs a person, not time — so it does not hold the fleet in 'starting' forever and does not sit in the bar as pending. Ready and stalled are drawn as two segments of one track, or the bar could never fill.

Timelines: family | ancestors | descendants | both | ops-phase
Files: files | file ages | folders
SHA3-256: 78fbef9d3020586f89d04e40f798e96ca53abc4be3e5f0bfbbd9f3c9445f272c
User & Date: dmestas on 2026-08-25 17:37:13.811
Other Links: branch diff | manifest | tags
Context
2026-08-25
19:03
land ops-phase check-in: 96b30ad4f5 user: dmestas tags: trunk
17:37
ops: say what the forge is doing, not just how fast

The panels were steady-state numbers and said nothing while a fleet came up — which is the window an operator most wants to watch and the one where a forge most looks hung. A multi-repo re-ingest on this fleet was mistaken for a hang precisely because nothing said '23 of 25 stores ready' while it worked.

A phase banner leads the page: starting, indexing, syncing or rest, with stores ready over stores served, artifacts this session, the slowest recent round, and the names of what is rebuilding — which, not merely that something is.

Derived rather than tracked. Every store already reports Indexing, LastOK, LastCount, Total and Stalled; a phase field somewhere would be one more thing to keep true. The test ordering is the reader's priority: rebuilding outranks syncing, and a store that has never finished a round outranks both.

A stalled store is DONE waiting — it needs a person, not time — so it does not hold the fleet in 'starting' forever and does not sit in the bar as pending. Ready and stalled are drawn as two segments of one track, or the bar could never fill. closed check-in: 78fbef9d30 user: dmestas tags: ops-phase

14:58
Accepted. The forge can see itself; the rest is history storage. check-in: 2cacce9b01 user: dmestas tags: trunk
Changes