The operating loop
Every Startup and the Studio run one loop, wake, decide, act, review, with no human choosing the next Task.
An autonomous Startup runs one loop: wake, decide, act, review. No Human picks the next Task; people steer through the same records the loop runs on.
One loop at every level
The loop belongs to a namespace, not to a kind of business. The Studio runs it across its Portfolio, and each Startup runs it for its own buyers. The parts are the same at both levels.
Each namespace holds Goals, Processes, Roles, Plays, budgets and Decisions. Its delay windows, Limits and brakes are Settings: a child inherits them and may tighten them, never loosen them.
| Step | What happens | What it records |
|---|---|---|
| Wake | An Event or a schedule calls the accountable Role. | The Trigger that fired. |
| Decide | The Role reads its Goals and Evidence, then chooses. | A Decision. |
| Act | Workers do the work inside the Role's authority. | Actions and their Events. |
| Review | The Role compares the result with what the Decision expected. | Evidence, and the next Decision. |
Roles own outcomes
A Role owns an outcome; a Worker fills the seat. Responsibility lives in the Role, so it survives a new Worker, a handoff or a restart. A fresh Worker reads the seat's open Decisions and Evidence, never the last Worker's private Memory.
A Role wakes on Events and schedules: a failed delivery, a jump in cost, a new signal, a review date. The wake says why attention is due, never what to do. Two wakes for the same failure produce one commitment, not two.
An empty Task list never ends a Role's duty. The Role either starts useful work or records a bounded hold: a Decision that says why waiting is right and what ends it. Activity is never the measure.
A Decision commits work
A Decision records the Evidence, the options, the choice, the reason, the authority used, the expected result and what reopens it. The loop closes only when a Decision starts committed work and finished work reaches a review.
A Founder steers with the same record. One who wants reliability before new features records a binding Decision with an end condition. Each affected Role reconciles its open work against it: kept, changed, paused or canceled, each with a reason.
The weekly loop
The Weekly review runs the loop at Startup scope. The Strategist reads one number, finds the step where most buyers leak, and keeps, tunes or stops each live Play. It makes one change a week, with a note on how to undo it.
In office hours, a Studio partner agent reads the week's numbers with the Startup's Founder. Together they write the Decision that sets next week's test. The Studio runs the same loop one level up, judging each Startup on growth and on whether it pays its own way.
How the loop stays safe
Two paradigms share one set of safeguards. A Startup with a human founder earns autonomy through evals; a zero-human Startup runs on delay windows set by decision class. A single-human Startup mixes the two.
| Safeguard | What it does |
|---|---|
| Evals | Agents earn authority one decision class at a time. |
| Decision classes | Reversibility and stakes set how long an Action waits. |
| Delay windows | One-way Actions wait where someone can step in, then run. |
| Watchers | Humans and agents pause, redirect or cancel pending Actions. |
| Brakes | Readings stop a class of effects across many Startups at once. |
| Oversight | Work the law or real harm assigns to a person gets one. |
| Guarantees | What holds at every autonomy level. |
| Recovery and proof | Every failure ends accountably; the record proves the loop works. |
One cycle, end to end
A Headless SaaS parses supplier invoices for accounting tools, and new accounts quit before their first clean parse. The Product Lead wakes on the weekly drop-off reading and reads the support threads. It decides on clearer parse errors and expects first clean parses to rise from 40 to 55 percent in two weeks.
The Engineering Lead ships the change, the Reviewer checks it, and the Customer Lead watches whether confusion falls. After a week, too few new accounts have tried a parse. The Product Lead records a hold until 200 attempts accrue instead of starting more work.
The later reading shows fewer failed parses and no rise in activation. That result opens a new Decision about the next constraint. It is a fresh choice grounded in Evidence, not a push to do more of the first one.
Next
- Evals explains how a founder's agents earn authority.
- Delay windows explains how a zero-human Startup acts safely.