Step 0 · before Cycle 1 only · seed the notional paper book
PC Seed the paper book
Done once, ever. Phase A trades no real money, but the machine needs a notional pot or the sheet is all empty cash slots. Recommended: £1,000; the paper cycles then rehearse exactly the Phase B book that goes live after three clean months. (Owner decision; change the number if you choose differently.)
Saturday · screen day (first Saturday of the month)
PC 1 · Run the screen
The date must be today's: the machine refuses any other for live data. First run of a month takes 10–15 minutes (it fetches ~300 price histories politely, two seconds apart). Let it finish.
What gets written, automatically: reports/2026-08/funnel.md · reports/2026-08/order-sheet.md (the canonical records) · site/cycles/2026-08/index.html (the page you'll read) · raw data archived under data/snapshots/2026-08/.
PC 2 · Publish
PHONE 3 · Read the cycle page
Open the site → Cycles → this month. Verdict, sheet, mix, funnel, league. Note the Saturday in-app checks list: new names the machine has never seen venue-verified.
PHONE T212 4 · Check and capture the new names
For each name in the Saturday list: open Trading 212 → SIPP → search the ticker → open the order ticket. On the cycle page tap exactly one result: Ticket opens · fractional, Ticket opens · whole-share only, or Not available. Download availability-YYYY-MM-DD.csv and get it to the PC.
The import validates every row before atomically appending the availability record. No fills, costs, or portfolio state are touched.
PC 5 · Only if something got an “n”: re-run from the archive
The machine promotes the next-ranked name and finalises the sheet, using Saturday's archived data, never a fresh fetch:
Then publish again (step 2).
Monday · execution day
T212 6 · Execute the sheet, top to bottom
Market orders, in sheet order, nothing else: this is where the no-override rule lives. Phase A: don't place orders; open each instrument and note what a £-order would have filled at (the app shows shares-per-£ before you'd confirm).
PHONE 7 · Capture as you go
On the cycle page: tap each row → enter qty and price exactly as the app shows it (pence for UK, dollars for US) → ✓ Filled. Ticket wouldn't open? ✕ Not available. Taps save on your phone. When done: Download → fills-2026-08-01.csv. Get the file to the PC.
PC 8 · Import: the record becomes real
(--date is the Monday.) Automatically: the book advances, reports/2026-08/fills.csv and costs.csv are written, and any Not available taps update the availability file for you: no hand-editing on Mondays. If it says a promotion is needed, repeat step 5, execute just the promoted rows, and import those fills too (partial imports are fine).
PC 9 · Commit the month and publish
This writes the canonical Paper, its HTML page, and the separate compliance record.
The rest of the month
Nothing. No prices, no news, no peeking. The system is deliberately blind between screens, and so are you. The only exception: a forced corporate event (suspension, delisting, takeover).
Who does what
| Task | Today | After M5/M6 |
|---|---|---|
| Screen, gates, ranking, decisions, records | machine | machine (scheduled) |
| Reading the sheet | phone | phone |
| Saturday venue checks | T212 + phone taps → 1 import command | same |
| Monday execution | T212 (human forever, by design) | T212 (human, forever) |
| Recording fills & venue surprises | phone taps → 1 import command | same |
| The Paper | 1 command | 1 command |
| Publishing the site | 1 command | automatic on push |