# 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.

# First Window Analyst 1: the pond crew lane (6 Oct 2026, 12:45 Bangkok)

## Read this first
- Read the shared setup first: http://159.223.88.168/hx-c9ois/fw/fw-common.md
- Your lane: pond coins (Uniswap v4, fee 0.01% = 100, tick spacing 1, native ETH, no hook) launched by crews that fake the buying with their own wallets.
- The "badge" (standard launcher token, runtime 3854 bytes, md5 of the "0x..." code string starting 17ad80, AND 0 ETH in the launch tx) marks WHO launched the coin, not how good it is. All badge coins: +59% a coin at $20 (30 Sep to 4 Oct, n389).
- Best crews: crew A root 0x92a0849f9b1e9e02363a4bd8d74a317fa6ddae92 (money wallet 0xbae538011874261e3fb4ca6aa03cacb2766c4d81) and crews B/C root 0x4757fc41278bd0f1b028c6dae71d381dc4558d98 (money wallet 0x79411dbcbcf0e5b27cd222f24e082fc0bbf32f16).
- Already found by an earlier analyst: tag the crew at launch from the deployer's funder (up to 3 hops, an earlier creator of that crew). 100% precise, 77% of A and B/C coins caught, +145% a coin buying at 10 s. Doc: http://159.223.88.168/hx-c9ois/sw/a1-4-launch-tag.md
- Danger: these crews pull within 60 s after an outside buy of 0.1+ ETH (7 of 7). Our $20 is about 0.0074 ETH.
- Price Predict is building the live pre-tag table (crew wallets tagged before they launch). You do not build it.

## Your tasks, in order
1. Catch the missed 23%. For A and B/C coins the 3-hop tag misses: where does the deployer's ETH come from? Try deeper hops, the money wallets, the send-to-many contract 0xf341c935599822f1bc1ec29e27606724fbbf6595, timing patterns. Keep precision at 100% on 30 Sep to 4 Oct, then check 5 and 6 Oct day files.
2. One combined rule. Launch tag + HOT regime (of the last 10 resolved badge coins, 4+ hit 3x, known before entry) + walk forward crew pick (crews whose earlier coins did well, 5+ coins). Report per day, total, best coin removed. Use only data known before each entry.
3. Exit per crew. Some crews pull right after the 3x half is sold (0x0ec66d31aab7e387b2f4cda075e39f7a6a0f541b: 8 of 14 hit 3x live but -10%). For each big crew, from its earlier coins, pick the exit (sell all at 2x, 2.5x, 3x; half 3x half 10x; time based) that pays best on later days.
4. Safe size. From every outside buy in A and B/C coins (first funder not a crew wallet, see crew_wallets.json and ffund.db), pull rate within 60 s after outside buys of 0.005, 0.01, 0.02, 0.05, 0.1 ETH vs crew buys of the same size.

## Hand back
- http://159.223.88.168/hx-c9ois/fw/fw-analyst1-status.md with: the better tag and its recall per day, the combined rule per day, the exit per crew, the safe size. Plain bullets first.

Version 1, 6 Oct 2026 12:45 Bangkok. Latest: http://159.223.88.168/hx-c9ois/fw/fw-analyst1.md