The causal loop
Watch → Signal → Explain → Air → Move → Resolve → Rank → Follow → (back to Watch)This is a superset of the core loop (Watch → Signal → Explain → Resolve → Rank → Follow). Two steps are inserted — Air and Move — between the call and its settlement. Nothing else changes.
The claim
Section titled “The claim”Denpa routes attention. In culture, attention is not coverage of the outcome — attention is the outcome. “Will X trend,” “will Y chart” are questions whose answers bend toward whatever the broadcast makes visible. Every attention machine has this feedback loop; every attention machine hides it. Denpa instruments it: the loop is timestamped, receipted and scored, so “directing reality” is a measurement, not a metaphor.
The steps
Section titled “The steps”| Step | Layer | What happens |
|---|---|---|
| WATCH | L5 media | live media bound to a market |
| SIGNAL | L3 + L4 | a YES/NO call locked with a snapshot |
| EXPLAIN | L5 take | judgment with a face on it |
| AIR | program clock | momentum earns a segment; airing is a protocol event with provenance |
| MOVE | snapshot Δ | the broadcast’s footprint on the market, captured at write time |
| RESOLVE | L6 outcome | the oracle answers; receipts are cut |
| RANK | L7 reputation | correctness, timing, difficulty, beating the crowd |
| FOLLOW | L9 social graph | the audience becomes the director |
Falsifiability
Section titled “Falsifiability”Attention machines sell correlation as causation and are never billed for their predictions. Denpa is billed. Every aired moment carries a settlement date, a receipt and a scored operator. If airing a market does not move it, the snapshots say so.
The line
Section titled “The line”Denpa directs attention. Market reaction is emergent. Never write copy implying Denpa directs prices or that airtime predicts outcomes. SIGNAL, not BET — everywhere, always. The causal loop is a measurement of influence, not a promise of it.
The fork rule
Section titled “The fork rule”The loop closes only where attention is performative. Sports runs the core loop; the causal loop degrades gracefully to it. Which loop a vertical runs is a verticalConfig property, not code.