Actuating loops
Every measured loop names the Setting, budget or Limit its reading moves, so a number sets the next step instead of filling a report.
Every loop sets the next step. Each measured Process and Play names the Setting, spending budget or Limit its reading moves.
How a loop actuates
A loop names its Metric, its window and its minimum sample. It also names what it actuates, and how the reading moves it. The verifier fails a measured Process or Play that actuates nothing.
Spend state
Runway writes a Forecast every week and after every large money Decision. The latest Forecast sets the Startup's spendState, and every money Limit reads it before a call.
spendState | When | Effect |
|---|---|---|
free | Default alive | Limits apply as set. |
tight | Default dead | Discretionary Limits halve, the Demand Budget included. |
hold | Under 13 weeks of runway | One-way spend stops, and a Decision opens. |
Inside that bound, the weekly mix of Plays moves the Demand Budget toward the Play with the best measured payback.
Other loops
- Customer health below its line starts a rescue in Retention. Use near an Entitlement's bound starts an expansion.
- An error group opens an Issue, and the fix-an-issue Workflow repairs it in a Change preview.
- A Startup Template rollout across the Portfolio halts when a guardrail Metric moves.
- The founder's inbox ranks every ask by the expected value of answering it.
Example
A Startup holds $60,000 and burns a net $5,000 a week. The week's Forecast reads 12 weeks of runway, so spendState moves to hold. A $4,000 sponsorship is one-way spend, so it waits as a Decision for the Founder, while a $40 API call still runs.