Startup foundation · 01
Assumption Ledger
A planned ledger that makes a venture's testable assumptions visible and ranks them by stakes if wrong and cost to test.
Collection 01 · Startup foundations
The operating questions every young venture meets.
Nine Planned capability records for turning assumptions, experiments, economics, delegation, and governance into work a founder can inspect.
Nine recurring problems
From hidden assumptions to governed execution.
Each record names a business need, declares a proposed operating contract, and makes the remaining implementation and review work visible.
01
02
Startup foundation · 02
Liability-of-Newness Map
A planned one-page diagnostic for identifying a venture's most binding liability of newness and one near-term response.
03
Startup foundation · 03
AI Pre-Mortem
A planned adversarial pre-mortem that compares founder-identified risks with failure modes surfaced through four hostile perspectives.
04
Startup foundation · 04
Minimum-Feature Prototype
A planned workflow for creating the smallest test-ready artifact that can probe one behavioral claim.
05
Startup foundation · 05
Stochastic Unit Economics
A planned unit-economics model that tags every line item by what is known, variable, or still unknown.
06
Startup foundation · 06
Monte Carlo Runway
A planned simulation workflow for showing a distribution of contingency runway rather than a single confident forecast.
07
Startup foundation · 07
Task-Allocation Map
A planned map for assigning venture work across founders, hires, contractors, partners, and agents using task characteristics.
08
Startup foundation · 08
Orchestration Map
A planned operational map linking task assignments to oversight, recovery, and escalation paths.
09
Startup foundation · 09
EIA Governance Artifacts
A planned kit for drafting a disclosure architecture, data provenance map, and audit-agent specification that can constrain venture choices.
Build discipline
A useful sequence is not a readiness claim.
The foundation must prove composition
Assumption Ledger is the proposed harness proof. Only after its frozen bytes pass a different-vendor gate does Liability of Newness become the first composition proof. Both records remain Planned today.
Start with the decision
Define the founder question and the cost of a wrong answer before specifying agent behavior.
Make the interface visible
State the inputs, outputs, permissions, failure states, and human gates the capability requires.
Earn maturity
Keep every record Planned until the runnable artifact and review evidence can be inspected together.
One capability map