Advanced
Advanced
What comes after your first working loop: making it better on purpose, running several at once, and keeping a fleet of them accountable.
What comes after your first working loop: making it better on purpose, running several at once, and keeping a fleet of them accountable.
Read these once you have shipped a loop that runs unattended and survives a restart. Before that they solve problems you do not have yet.
| Page | What it covers |
|---|---|
| Authoring your own loop | Designing a loop from scratch rather than adapting a pattern |
| Hill climbing | Improving a loop's output measurably instead of by feel |
| Loopcraft: stacking loops | Composing loops so one feeds the next |
| Multi-loop coordination | Several loops on one repository without collisions |
| Evals and traces | Knowing whether a loop is getting better or worse |
| Governance | Policy, permissions, and audit for loops that touch real systems |
| Enterprise scale | Running loops across teams and repositories |