Visst · the line

Is the engine going to be built on time?

as of · main · assembled by A4 from origin
Verdict

20 December milestone · encoding burn-up

Rules encoded against the line needed for 20 December

Encoded on main Projected at the last 7 days' rate Needed for the director's core + VAT + EIS by 20 Dec
Ultimate goal · all 16 categories

Where the whole corpus stands

Stages: authored = rule files merged to main; verified = the category cycle closed; fixtures = a statute-derived fixture suite locked; encoded = rules in the Rust kernel; computing = the kernel passes that category's fixtures. Only NI has a fixture suite.
The 16 categories

Authored → verified → fixtures → encoded → computing

Rule counts are root-level *.yaml files per category directory at main ; the five unstarted categories have no directory yet. D&S is host-embedded (2 new rules, 20 extended).
Money

What the work is costing, and when to top up

Update the balances after a top-up (stored only in this browser)
Sources: your Usage and Billing screenshots of 19 Sep 10:50 BST. Burn per day = month spend ÷ days elapsed. The API side can be read live once the Console account is an organisation (Admin API); claude.ai plan usage has no official API, so that field is yours to update.
Quality · the degradation gauge

Blind verifies: blocking findings per unit

If speed goes up and this goes up with it, we slow down. Engine and machinery units are the units that must stay at zero; corpus verification slices are meant to find blocking findings in authored text, so their count is the instrument working, not degrading.
The line now

Four counting slots, the exempt slot, and what is queued behind them

Queue depth per lane (ready or drafted rows)
Seat and utilisation
On you

Things only you can do

    Continue or stop

    Tripwire criteria, written in advance