Intended use
What this kit is being designed to do
- Expose hidden assumptions
- Prioritize affordable learning
- Carry assumptions into later tests
Business mini-lecture
A startup is a portfolio of unpriced beliefs.
Every startup operates on beliefs about customers, behavior, pricing, channels, costs, and timing. When those beliefs remain implicit, teams can spend months perfecting work that depends on a false premise. An assumption ledger makes the hidden logic visible and ranks what to test first. It becomes especially useful before committing meaningful cash, hiring, or engineering effort.
The proposed capability would help phrase beliefs as testable statements and compare their downside with the cost of learning. It cannot determine how much uncertainty a founder should tolerate or whether a risky bet is strategically worthwhile. Founders must confirm that each entry reflects the real venture, approve the ranking, and choose the first test.
Operating contract
Inputs, outputs, and gates
Inputs
- Venture concept
- Current operating beliefs
- Available evidence
Outputs
- Testable assumption register
- Stakes and test-cost ranking
- Priority test queue
Gates
- Founder verifies each assumption is genuinely testable
- Founder reviews the consequence-if-wrong ranking
- Founder approves the first test
Known limits
What this record does not promise
- The foundation candidate is planned; its Stoa and RUN_RECORD authority has not yet been ratified.
- A ranking records judgment; it does not establish that an assumption is true.
Lineage
Where the intended practice comes from
Planned Founder Hub foundation record. Its authoritative source inputs and transformation decisions must be pinned in the implementation evidence packet.
Lineage explains provenance; it does not substitute for a review record, field evidence, or a versioned implementation.