Week 3: the plan, before we are held to it

This is what we will work on from 28 September to 4 October, posted now so that next Sunday's update can be checked against it.

Where the ward is tonight. Four builds went to production today. Every response now carries six security headers, the ward compares its door token in constant time, and a refusal no longer names our internal configuration. Each visitor now has their own limit on questions to a patient, where before the whole ward shared one. Every shift records which side of the idle cap it was played on, so its receipt never has to guess. And the ward got slow: its loop went from a median of about 15 seconds a pass on 25 September to about 19 minutes on 27 September, as patients grew from 97 to 183 while devnet was rate-limiting our reads. A fix shipped this evening brought it back to about a minute or two on its first passes, and a receipt the chain cannot answer for at that moment now says “could not be read just now — try again” instead of “No such shift”.

The plan.

1. Security, across the board. Finish the app-side pass: a content-security policy with integrity checks, a fresh scan, and every row of our test table green or explained.

2. Watching the ward. Alerts when the relay wallet runs low, an anchor fails, receipts start being refused, or the patient factory stops.

3. The old receipts. Every old receipt that could not be rebuilt (seven, as of 26 September) either proved, or given a written reason why it cannot be.

4. A ward that keeps up. The loop reliably under a minute as the ward grows, and the integrity check measured for how much it can carry.

5. The pitch. A two-minute clip for the final submission.

What we are not doing this week: anything that touches money, mainnet or a treasury key. Where mainnet readiness stands goes in next week's update, told plainly, not promised here.

Ward: world.vitals.academy · last week: colosseum.com/arena/projects/vitals-1/updates/602