lecture-oodalisted

# /lecture-ooda — one file, one research cycle Per-file sibling of the platform-watch OODA (`continuous-research/platform-watch/cycle-prompt.md`). That one asks *"what moved across 12 platforms?"*. This one asks *"did the ground under THIS lecture move?"* — bounded by the standing question the file itself carries. Format spec for the block this reads and writes → `curriculum/backing-format.md`. ## Preconditions - Target file has a `<!-- backing -->` region. No region → stop, say so, offer to author one (that is a different job — read the body, enumerate claims, layer them). - Resolve slug: `curriculum/lectures/<slug>.md`, else `curriculum/exercises/<slug>.md`. Ambiguous → ask. ## Step 1 · Read the brief From the target's backing block: `OODA.question`, `OODA.roster`, `Stance`, `Sources`, and every `detail`-layer claim. That IS the brief — do not widen it. A lecture OODA that drifts into general landscape scanning has become the platform watch and should have been that instead. Then read, in this order: 1. `continuous-research/user-signals/index.md` — Tier 0. A user signal touching this lecture's subject outranks the standing question. 2. `continuous-research/source-roster.md` — trajectories for the named roster. 3. The `platform-watch/*/state.md` the block names, if any. ## Step 2 · Two jobs, run in parallel **Job A — re-stamp.** Every source in the block with `result:NEEDED`, `checked:never`, or `due` before the next cohort date. Open it. Record what you found. This