Loop Schedule · loop-schedule
Owner directive (2026-07-11), canonical. "meeting of dynamic squads with daily standup (Every 2 hours standup meeting) … Schedule Loops when results are predictable, Loop and Upload to Library (git) with a log at the Venture Book." [src: wiki/development/prompts-archive/INDEX.md:0]
Content
The cadence squad-hyper-build and squad-hyper-review run on. A Loop is scheduled only when its result is predictable; otherwise it is worked live in the Workstation and reviewed before it becomes a standard.
| Beat | Interval | What happens |
|---|---|---|
| Standup | every 2 hours | each squad reports its current loop per activity; blockers surfaced |
| Build loop | per predictable unit | dooit: PREPARE → METHOD → EXECUTE → DELIVER an atom; ditto gates it |
| Review pass | one per build loop | squad-hyper-review poses questions on the new/changed concepts |
| Upload | on loop close | commit to the Library (git); log the decision at the venturebook |
| Standard | on approval | the atom is benchmarked and refined in the Academy; standard updated |
Loops are dispatched in the dispatch.json model (pb-003-run-dispatch, sop-003-run-dispatch): a run holds cycles, cycles hold ticks at a fixed intervalSeconds. The Venture Book is the reflection of the build-up and decisions — particle augmentations, approvals, reviews, quality, standard updates.
Composition
- uses: dooit, ditto, sop-003-run-dispatch, pb-003-run-dispatch
- used-by: run-020, squad-hyper-build, squad-hyper-review
See also
- sop-001-loop-execution — how a single loop executes
- venturebook — the log every closed loop writes to