Every printed order is executed. Nothing else ever is.
Nothing on the sheet is skipped; nothing off the sheet is bought. An unavailable instrument is excluded only through the written venue rule and recorded as such.
Project Upwave · Private compliance record · Ola
Upwave runs on rules frozen in advance, not opinions. Its first product is proof: one screen, one order sheet, one execution record, and one Paper every month.
Upwave tests whether a small, systematic process can be followed exactly for three years, with every decision traceable to a frozen rule and a dated record.
It is not a watchlist, a trading dashboard, or a research lab. There are no live prices, alerts, discretionary ideas, or intramonth decisions. If the system trails its primary benchmark after 36 live months, net of costs, it retires and the capital goes passive.
Every screen, order, fill, and report exists to keep these commitments.
Nothing on the sheet is skipped; nothing off the sheet is bought. An unavailable instrument is excluded only through the written venue rule and recorded as such.
If the account read £0.00 tomorrow, no bill changes. Top-ups follow a pre-written schedule, never a losing month.
The machine does the analysis. Ola checks venue facts, executes the printed sheet, and records what happened. Total human time is about 30 minutes a month.
Friday-close data passes through the frozen gates. The run writes the funnel, league, order sheet, and cycle record. Missing data fails closed and is counted.
Open each new buy candidate from inside the Trading 212 SIPP. Record whether the ticket opens and whether fractional shares are supported. This is a rule check, not a judgement.
Execute the sheet from top to bottom at market, then capture the fill quantity and price. Nothing is added, skipped, reordered, or improved by hand.
Import the fills, generate the Paper, and close the loop. There is no price monitoring or intramonth trading except a forced corporate event.
The explainer gives the shortest trustworthy path. The detailed rules, machinery, instructions, and monthly evidence remain on their authoritative pages.
| Question | Page of record | What lives there |
|---|---|---|
| What are the rules? | PRD | Purpose, frozen constraints, milestones, outputs, and non-goals |
| How does it work? | Architecture | Pipeline, modules, data contracts, invariants, and publishing |
| What happened this month? | Cycles | Order sheet, funnel, league, Paper, and provenance |
| What do I do next? | Runbook | The exact PC, phone, and Trading 212 sequence |
Reference definitions stay here for first-time reading, but no longer interrupt the main path.
Yes. The 200-day rule is evaluated on screen day, and that monthly check is the stop. Between rebalances the system deliberately does not monitor prices. Only a forced corporate event can trigger intramonth action.
The unused slots stay in cash. The rules are never loosened merely to become invested.
Because the label is evidence for the three-year review, not a decision input. Letting it change orders would create an override valve.
Process failure is a breach of the no-override rule. Performance failure is trailing the primary benchmark after 36 live months, net of costs; that outcome retires the system.
The £2,000 is tuition, not the prize. The experiment tests whether a small, boring, fully recorded process teaches more than discretionary monitoring.
M1–M5 are built and reviewed. The M6 dress rehearsal is under way: the Saturday leg ran on live data on 25 Jul 2026 (screen, venue checks, availability import — 12 buys, £0.04 remainder). The Monday paper-fills leg, the owner sign-off, and the final calibration checksum complete it.
Cycles 1–3 run the complete process with no capital.
Only after three clean paper cycles.
Only after six consecutive compliant live cycles.
| BUILD | M1–M5 built and reviewed · M6 rehearsal: Saturday leg complete 25 Jul |
| TESTS | 293 passing |
| CAPITAL | £0 at risk |
| NEXT | Rehearsal Monday leg (paper fills + Paper), sign-off, final checksum · Cycle 1 on Saturday 1 Aug 2026 |
| FREEZE | Parameters v1.0 · next amendment window 22 Jul 2027 |