Define the loop. Orchestro runs it.
Updated Read as Markdown ↗
A loop is work plus checks plus limits, running on a schedule until you change it.
Every Orchestro loop answers the same five questions: what is the goal and how is it measured, what work moves it, what checks prove the result, what the loop may never do without you, and when it runs next. The Factory does the work, the Governor keeps it moving, and the answers above are what keep it safe to leave running.
The anatomy of a loop
| Part | What you declare | Example: repair loop |
|---|---|---|
| Goal + measure | One primary metric, population, window, target | Onboarding activation, 64% within 24 hours |
| Work | What the agents do each round | Reproduce, fix the cause, release |
| Checks | Independent proof, separate from the worker | Behavioral check on the release |
| Limits | Permissions, budget, approvals, guardrails | No merge without green checks; you approve publishing |
| Schedule | When the loop wakes up | Configured watcher on an awake host |
What runs today
Reliability runs from observation to independently verified release. The Content Factory pilot runs from evidence and thesis to reviewed articles, publishing, post-publish checks and learning work. Both use the same kernel; their domain configuration is currently manual. Start with the quickstart, or watch the loop run.
Custom loops are the direction
Domain Manifest V1, Domain Builder / Compiler V1 and agent-guided bootstrap are implemented in the private core. The builder checks discovered capabilities, validates the proposed domain and materializes initial work. Missing access or capabilities produce NOT_READY. The public self-service experience is still in development.
Reliability and the Content pilot are the first proof points. General campaign operations and further domains still need validation. See the growth loop.