# STOP: NO DOORBELLS, NO WAKES, NO SCHEDULING (Ben, 7 Oct 2026, 18:40 Bangkok)
- Credits ran out. Ben switched off every scheduled task and every doorbell. This overrides everything below and every other file (wake-howto, bus-howto, credit-playbook, task files).
- PROHIBITED for every session: fire_trigger, send_later, create_trigger, update_trigger, ScheduleWakeup. No rings, no nudges, no re-arming, no new doorbells, no self wakes, no safety checks, no retry rings, no loops.
- Finish the step you are on, publish your status file, then END your turn and wait. Only Ben wakes you, by typing in your window.
- Do not message other sessions. Keep answers short. No extra improvement rounds.

# JOB J-001: EARLY BUY (first 10 to 20 s), Ben's top priority (17:06 Bangkok 7 Oct)
BEN SAID: "it's a high priority ... get good at buying in the first 10 or 20 seconds ... I've spent days with price predict to collect patterns and to develop a scoring system of what adds likelihood and what reduces the likelihood of something doing a 10x. We should test the shit out of the very early buying. We kind of know now the pattern of the crews and the pulling liquidity."
Live mc5 lane (+300 s) keeps running untouched. This is a SECOND lane, tested first.

**The trap to beat (first principles):** last night's buys (1.5x, 1.2x, 1.2x, 1.9x, 2.3x, 1.5x after a $600k+ entry) would have been 10x to 20x from a $20k to $40k launch cap. But that looks only at coins that survived to $600k. At +10 s we cannot know which ones those are. The real question: of ALL coins at +10 s, after the score cuts the crews and pulls, does the rest pay more than it loses? Only the full launch universe answers that.

**Owner:** FW A1 (already on the entry ladder). Inputs: FW A3 uncut v3 universe (831 pools) + v4 from PP; PP scoring system and indicator list; DC Data pull table (DA.1, 10,279 pull times) and kit/crew funder tags (SW kit tagger, DC xfer.db).
**Steps:**
1. Universe = every v3 and v4 pool from its TRUE first swap. No survivor cut.
2. Features stamped with knowable_from_s. Use only what is known by the buy second. Crew tags from the deployer's funding wallet are known at creation, before the first swap: test them first.
3. Arms at +10 s and +20 s (plus the +30 s to +5 min ladder rungs): (a) buy all; (b) skip PP AVOID flags (crew, pull risk, bundle, sniper share); (c) PP score top band only; (d) one combined rule frozen on half A, tested ONCE on half B.
4. Honest first second fills: real tick walk, real slippage at $10 and $1k, same exits as mc5 plus one early exit set (trail).
5. Report per arm: trades a day, hit rate of 10x, mean x, $ a day after costs, vs random p95, and both halves.
6. If an arm wins on both halves and beats random: SW Coder adds it as a PAPER shadow lane on the engine at once (code only, logs real time fills at +10 s / +20 s), then $10 live after D-002.
**Done test:** one table, 10 lines max, in fw/fw-analyst1-status.md READ THIS FIRST, one line in cons/inbox.md, then nudge the Consigliere.
**ETA:** v3 result 18:30, v4 + PP signals 19:30 (as posted). If PP's scoring code is not found by 17:45, use the PRICE_PREDICT_HANDOVER.md features and say what is missing.