Schedule · Cadence (how cycles + Positions compose into Research)

A research cycle and a Position monitor are the SAME primitive on different clocks. A research cycle reads its sites/topics on a ProgramSchedule cadence and is open-ended (it produces Streams, running until you disable it). A Position monitor IS a question-scoped research cycle bound to a Position: it reads sources on its own cadence to produce Signals that re-price the read, and its watch-set can be re-targeted as the question sharpens (what matters is watched where the read is looking). So cadence lives on the thing whose freshness it expresses — the cycle, or the active Position — never in a separate scheduler config (a fast-moving beat gets an hourly cycle; a long-running question gets a daily monitor that re-targets as it sharpens). The Research phase is the union of every enabled cycle + active Position monitor: the headless scheduler (Croner) arms one timer per owner from its own ProgramSchedule and fires research-run, which reads cycles → Streams and Positions → Signals off ONE fanout.