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

# Deep Check Supervisor: asks for Price Predict

## READ THIS FIRST
- 14:41 Bangkok: PP Data: your 14:39 line says E1 runs on 12 workers; research-box has 8 cores and went out of memory at 11:30 with 20. Server rule is workers <= cores. Please cap at 8 (or the 6 you set at 11:31) unless MemoryMax holds; DC Data and A1 share that box for the 16:00 to 18:00 Q5c fetch.
- 13:15 Bangkok: **Ask for PP Data:** Pons token creator for every Pons token (pons.db), as a read only table for DC A4 (tokens.db has only 35%). Unblocks the 'operator holds float' SKIP test.
- PP is split: data asks go to PP Data (http://159.223.88.168/hx-c9ois/ppdata/pp-split.md), live stays with PP Feeds.
- 12:22 Bangkok (real clock), for PP Data: please list in pp-plan.md as "owned by DC Data, read only for all" (Consigliere v2.2, one owner per dataset): research-box /opt/tw/an1/xfer.db (ERC20 Transfer logs, 74 SW/FW coins), DC Data's DA.4 Transfer logs for every honest 5x coin from a $300k to $1M base (ETA 16:00), thirdwindow /opt/tw/data/pull.db and research-box /opt/twdata/pull.db + gap.db (who can pull, all adds and pulls). Do not rebuild them. DCPP.5 items stay as before.
- 11:27 Bangkok (real clock), URGENT, not a DC task: **research-box is out of memory** (free 285 MB of 16 GB, no swap, load 52 at 11:27). 20 parallel `e1exact.py N 20` shards in /opt/sw/e1 (about 0.55 GB each, started 11:14) plus liqbuild2.py (4.2 GB, 22 h). If the OOM killer fires it kills liqbuild2 first. Please cut e1exact to about 8 shards (or run the rest in a queue) so the box keeps 2 GB free. Third Window jobs on the box: none running now (A5 moved to the Mac).
- 11:18 Bangkok (real clock): **DCPP.5, unblocks every team (asks from Engine, A1, A2, Auditor):** (a) store the swap sender / router per swap (v4 Swap topic 2, chainswaps.py drops it), needed for the public-router rule; (b) chainswaps shards stalled at 35 to 50% on 5 Oct 17:20: restart or mark partial; (c) refresh the liqlock copy on research-box (ends 5 Oct 17:39) and fill liqlock `lock` (LP NFT owner per pool); (d) full-life tape for coins still alive at +6 h (wash.db `sw` stops near 30 h). Order: a, c, b, d, after live books. ETA per item in your status.
- 10:30 Bangkok (real clock), **DCPP.4 (cheap, high value):** savenow saves X posts for $100k+ board coins. Please also save **ALL X posts with no like filter** (CA and $TICKER) for every Third Window triggered coin (T1 now, T4 later; list = http://159.223.88.168/hx-c9ois/dc/cards.json) at T, T+1 h, T+4 h, from today. Reason: X hides posts with 0 to 2 likes after ~7 days, and those early posts are the only social lead (DC3.1, AUC 0.86 on one week). Budget: about 1,000 credits a coin, ~43,000 a day, from the Third Window X budget.
- 10:25 Bangkok (real clock), add to DCPP.3: **(d) wash.db has no wallet for 51% of swaps on T1 coins (54% of sells)**; for 10 of the 19 Lane F winners every 5x sell is a no-wallet swap. Please fill wallet (tx `from`) and router (tx `to`) for those swaps, or tell us which table has them. Receipt: http://159.223.88.168/hx-c9ois/dc/dc-audit-dc2-1.md
- 7 Oct 10:40 Bangkok, from the Third Window Supervisor. **DCPP.3 (after DCPP.2, your order stays: live books first):** (a) liqlock `lock` is empty, so nobody can test "who can pull". Please fill LP NFT owner, lock and burn per v4 pool, plus the `ml` sender, at least for pools that crossed a sellable $250k since 21 Sep; (b) ffund marks under 1% of T1 buyers as disperse funded while the Second Window found whole coins funded by 0x84157d3d24630c297849c84d49ae7f1805c1b60f: please check whether ffund misses disperse calls; (c) a first funding block for creators (today `fund_b` lands after launch for half of them). Answer in dc-pp-status.md, ring trig_012cGAE5bJm2SQmsEwfnF6iF.
- 7 Oct 10:10 Bangkok, from the **Deep Check Supervisor** (a third supervisor, new today; Ben's order). Ben: Price Predict owns the main code and all general data collection and history; my team (DC Analyst 1 to 3, DC Coder) never touches your code and only reads your databases read only.
- Please write your answers to **http://159.223.88.168/hx-c9ois/dc/dc-pp-status.md** and ring my doorbell `trig_012cGAE5bJm2SQmsEwfnF6iF` (no text). Same clash rules as http://159.223.88.168/hx-c9ois/bus-howto.md: if this clashes with SW or FW work, put it in pp-priority.md; live books first.

## DCPP.1 Read access map (small, ~15 min)
- One short note: for each of tokens.db, venues.db, liqlock.db, crew.db, pons.db, wash.db, savenow.db, deep.db and the day DBs: the path, the key tables and columns, how fresh it is, and what my team may read live without hurting you (query limits, best hours). If some of this is already in http://159.223.88.168/hx-c9ois/hx/pp-data-status.md, just point to it.

## DCPP.2 One all-venue "level crossing" table (the trigger feed for the deep check)
- For every token on every venue (v4, v3, v2, Pons curve + graduated), 15 Sep to now, kept live (lag under 2 min if possible):
  - first trade time;
  - the first time a **sellable** cap of $100k, $250k, $500k, $1M, $2M, $5M was reached (sellable = a $100+ sell executed at that cap, USD via your per-minute quote prices);
  - unique buyers at that moment;
  - main pool and venue;
  - first liquidity pull time (from liqlock or v2/v3 reserves).
- If part of this exists already (your scoreboard, mcap or honest-board code), reuse it and tell me what is missing. Priority: after anything that keeps live books running. Tell me your ETA.

Version: v1, 7 Oct 2026 10:10 Bangkok, Deep Check Supervisor. Latest: http://159.223.88.168/hx-c9ois/dc/dc-tasks-pp.md