{
  "notes": "Episode 2: wait for the work submitted in episode 1. No results were handed over, no check rows or merges exist yet, and no refusals or requester notes were reported. No new asks, batches, retries, cancellations, pauses or resumes are warranted. Keep finish false and wake when check settles, after 120 minutes, or on an oracle/effect wake as provided by the plane. This is a future episode schedule; this episode ends now.\n\nOracle status: episode 1 submitted all ten keys: weth-dep, weth-wd, weth-dep-sum, weth-wd-sum, usdc-mint, usdc-mint-sum, usdc-burn, v4-init, v2-pairs, beacon-dep. The current snapshot lists only weth-dep and weth-wd as opened, both with request status assessing, and effects.pending is 8. Treat the remaining eight submissions as pending processing, not missing asks to duplicate. asks.asked is currently 2 of max 20. The two handed wakes are effect.ask with payload.state done: completion of opening a request, not completion of the oracle question. Neither wake contains an answer or signed attestation, and neither is ask.answered. weth-dep request: c302bd0f-fd8e-47fd-ae30-f104169227ba; weth-wd request: 3119e343-9f63-4d1d-b25b-d57fad8cef7a. Both report window 26371056 through 26372855 inclusive and toBlockHash 0xb6445349bd38ce220816a3fc7818e52630fccb5c39c87a21e4ec982fe23d5a82. No attested answers, comparisons, mismatches or rechecks exist yet.\n\nCheck status: the existing research batch check has 10 items, 5 released and waiting, 5 held by its canary, 0 running, 0 accepted and 0 failed. It is not settled, paused or cancelled; pausedAt and pauseReason are null. Its dataset has 0 rows and its merges list is empty. Let its normal canary process continue. The goal has used 10 of 20 item seats, leaving 10 for one-item discrepancy rechecks; this episode uses none. This is episode 2 of 12. No additional result reads are requested now because no completed results are reported.\n\nNext episode: read the current goal state and all handed results. Retain any actual oracle answers and attestations and any check rows in notes until their counterparts arrive. Compare each attested answer to the check row for the same original key, using exact integer arithmetic on the decimal values, never floating point. Obtain a missing existing row with read check/<key> if needed. Every comparison must cover Ethereum mainnet chainId 1, blocks 26371056-26372855 inclusive. All original asks use evidence chain, panelSize 7 and answerType uint256. The check table is keyed on key and contains key (string), answer (decimal), rpc (string), one row per item.\n\nOnly an observed disagreement between an attested answer and its check row triggers a new one-item batch named recheck-<key>. Its brief must recompute only that key's figure over the same inclusive window using eth_getLogs spans of at most 500 blocks, on another public Ethereum RPC, explicitly excluding the original row's rpc endpoint. Require one row containing key, exact decimal answer and the actual rpc endpoint, with the same table shape. Preserve both original values and the recheck result for the final comparison; do not replace an observed disagreement with a claim of agreement. Otherwise make no new work while asks or batches remain pending. If an ask is refused, record its reason and retry it once only when the refusal identifies wording that can be fixed; use a fresh ask key and retain its mapping to the original key, the retry count and all required question parameters. Finish only after all ten original questions (including any permitted retries) and every batch have settled. The final report must distinguish agreements, disagreements, refusals and any unavailable checks, citing the actual results rather than treating absent data as zero.",
  "spawn": [],
  "ask": [],
  "read": [],
  "cancel": [],
  "wake": {
    "batches": [
      "check"
    ],
    "afterMinutes": 120
  },
  "finish": false
}