Stress-Test Triad
Baseline · Optimized · Crisis
Three Runway Zero instances running in parallel. Each pillar is pre-seeded with a different set of assumptions — and keeps its own state from there. Adjust any column to see how far apart the Zero Dates can drift from the same starting cash.
Baseline is your current trajectory. Optimized trims burn and pushes revenue. Crisis zeroes revenue and asks how long pure cash decay buys you.
How the triad works
Each pillar is a namespaced Runway Zero instance. Scenario states live in separate localStorage
keys (runway-zero-v1__baseline,
__optimized,
__crisis). On first visit the
triad pre-seeds each with its starting assumptions; after that your edits persist.
Any Pipeline Boost you've set upstream (Subscription Purge, Gig-Net Floor, Geo Arbitrage) feeds all three columns simultaneously — because the session-context field is shared, not namespaced.
The most useful read is the distance between columns. If a small burn reduction moves the Zero Date more than a revenue assumption, cost control is the near-term lever. If crisis collapses immediately, the next decision is reserve, collection speed, or a fallback income path.