Nitro end-to-end proceed document v1 (4 Oct 2026)
Saying “proceed” or “end to end” authorises every stage, in order, through to done; only “hold” or “stop” pauses the lane. Seven stages: 1 Scrape (top 20 long videos and top 20 Shorts by views, at full depth); 2 Extract (master scope document in Berg format); 3 A+ definition (the locked rules template one, with a checklist and NinjaTrader-style parameters, feeding the Roman and ZZ entry contracts); 4 Code (missing rules first, then partly coded; back up first, new settings default to off, unit test plus smoke run, no tuning or performance claims); 5 Contradictions (each becomes a flagged, switchable setting; never pick a side); 6 Publish (Dev site only, URLs verified live); 7 Test hand-off (in-sample tune, then out-of-sample once, then holdout once; commission out of everything). Every hand-off reports what finished, the counts, blockers, links and the next stage. Never without asking: production pushes, money or sends, inventing an unstated rule, or presenting in-sample results as final.
Full text: /dev/farm-schedule.html#proceed-document