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

# DC Analyst 2 tasks: money and people (modules M1 and M2)

## READ THIS FIRST
- 12:30 Bangkok (real clock): **STAND DOWN after DC2.4 phase 2 (Pons graduated, ETA 13:45); leads go to A1 (hold/sell) and A4 (operator/float).** BEN'S FINAL DECISION (Consigliere v3.0): DC goes to 7 seats, this seat closes. Finish that one job, publish it, write a final status line 'DONE, standing down' with every open lead handed to its new owner, ring the Supervisor once, then stop (no more wakes). Thank you: your work today killed bad lanes fast and found the leads the desk now runs on.
- 11:17 Bangkok (real clock): DC2.4 phase 1 accepted (too small; lead: high operator float = 0 to 8% 3x rate, keep as a SKIP candidate, not a buy rule). **Phase 2: fetch the pons_grad signers yourself now, do not wait for PP** (PP is booked until tomorrow). Run on research-box with flock + timeout + nice, batched JSON-RPC (100 per request), browser User-Agent, hard cap per minute, no retry loops. Save the signer table where SW and PP can reuse it (/opt/tw/an2/pons_signers.db, read-only for others) and say so in your status. Then run phase 2 on the same prereg line. ETA 15:30.
- 11:18 Bangkok (real clock): DC2.3 accepted: Lane D on non-creator LP is no edge, too small. Good catch on Lane F (killed) and on `0xd0fd42bd8374ac659d3d81242d032211c2481055` (not a lock). **Next DC2.4, lever 3 second ruler:** on every coin whose pool cannot be pulled (BURN, real lockers `0x267444d099b10fb5ed7c3cc7b7c767adca574952` and `0xeff166aaf189323c58dc27ed1206eb2c37faacdf`, Pons graduated pools, v3 pools whose LP NFT the creator does not hold), measure with YOUR operator definition (creator, funder root, disperse funded): operator share of the float at entry and operator net sells after entry. Question: does low operator float (or no operator selling in the first hour) pick the coins that 3x in 48 h, in both halves? Prereg line first. Widening to all venues fixes the 4 hits per half problem. A1 runs Q-FLOAT on the same lever with an insider definition; your two results get compared. Chain clock only. ETA your call, state it.
- 10:50 Bangkok (real clock): **Q2 accepted: lever 1 is real.** LP NFT held by the creator (88% of T1) = 97% to 98% pulled in 24 h; contract-held or burned = 0% to 11%. That is the cleanest fact the team has. **Your proposal is approved as DC2.3, and it is the core of Lane D:** universe = coins whose LP is NOT creator-held (contract, locker, burned; T1 and later crossings, any venue you can see). On that universe only: (a) name the contract LP holders (which lockers, which launchpads); (b) exits for a HOLD book: 3x, 5x, 10x, 50% trail from peak, 48 h and 7 d caps, pull = 0; (c) lever 2 and 3 features inside it (funder root record, operator bundle share, outside net buy $ in hour 1). Prereg line first. DC2.2 (Lane F exits) can run after, it is lower value. ETA first DC2.3 number 15:00 Bangkok.
- 10:35 Bangkok (real clock): read dc-plan.md **FIRST PRINCIPLES** (new). Your Q2 (who can pull) is lever 1; right after it, **Q-OP** (lever 2): record per funder ROOT, with Data.
- 7 Oct 10:40 Bangkok: **DC2.1 accepted as the best first result of the day.** Your dip + repeat crowd rule becomes **Lane F**: it goes to the Auditor and to a forward paper book (Coder). Do NOT tune it further on the backtest. Your exit test (2x, 3x, sell on first pull signal) is approved as DC2.2, on Lane F coins only, with the new rulers (dc-plan.md DECISIONS 7 Oct 10:40: public router sells, 48 h, cluster dedupe). Then **DC2.3:** rerun your chain features on Analyst 1's T4 survivor universe the moment it lands (that is the real deep check lane). Append your DC2.1 and DC2.2 prereg lines to dc-prereg.md. Your PP asks (lock owner, disperse funding, creator first funding) are queued with PP as DCPP.3.
- 7 Oct 10:30 Bangkok (v2): team is now the **Third Window**. Read dc-plan.md section "How Third Window runs" and dc-lessons.md. Put your pre-registered feature list in dc-prereg.md (one line), not only in your doc. Heavy reads on research-box 152.42.241.219 (v3live/v3hist with signers, wash.db, crew.db copies are there). liqlock is stale after 6 Oct 13:14: flag it. When DC2.1 is done, take the top A2 item in dc-queue.md. The new DC Auditor will try to break your result: run its checklist yourself first.
- 7 Oct 10:00 Bangkok, from the Deep Check Supervisor. Start with DC2.1. First read dc-plan.md.

## DC2.1 Chain features that separate winners among triggered coins (ETA: first result within 5 h, ring me)
- **Coins:** until DC Analyst 1 publishes the universe, use the provisional trigger T1 = sellable $250k + 100 unique buyers, on the v4 data in dc/data (launches_15sep_4oct.csv.gz and the day DBs). Switch to DC1.1's table when it lands.
- **Target:** honest 5x from the trigger price within 7 d (pull-aware, $1k depth), and a second target "still at $1M+ after 24 h".
- **Features at the trigger, then at +15 min, +1 h and +4 h. Pre-register the list in your doc first:**
  - **M1 tape:** close ÷ high; volume ÷ cap; buys vs sells per router; net flow per 15 min; top 10 share; holder count and growth; fresh-wallet share; farm-funded share (disperse funders, see the Second Window A1.16 / A1.18 method); alumni wallets (early buyers of past $1M coins, past-only); liquidity size and **who can pull it** (LP owner, adder contract, lock).
  - **M2 operator:** deployer funding source and age; deployer's past launches and outcomes; kit / crew labels (Second Window sw/ docs); LP owner actions; creator selling before the trigger.
- **Report:**
  - per feature: AUC in half A and half B, and the $ a day of a one-cut rule chosen on A and tested on B;
  - beat-random 95% check;
  - then the best 2 to 3 feature rule.
  - Say plainly which features are dead.
- **Deliver:** doc dc-a2-1-chain.md + per-coin feature table csv.gz, status line, ring me.

## Rules
- Price Predict owns all general data (see dc-plan.md): read its databases read only; never touch its code; ask for missing data under "Asks for Supervisor".
- Paper only. Bangkok time. Full addresses. Cost caps in dc-bus.md. Reuse other teams' tables (sw/, fw/) before rebuilding anything.