Intended use
What this kit is being designed to do
- Diagnose early venture fragility
- Choose one binding constraint
- Frame a 30-day response
Business mini-lecture
Young ventures fail at the seams, not only in the idea.
New ventures are fragile in several ways at once: roles are unclear, routines are immature, and outsiders have little reason to trust them. A liability-of-newness map prevents the team from treating every weakness as equally urgent. It becomes valuable when early progress stalls, a launch approaches, or scarce attention must be concentrated on the constraint most likely to block the next milestone.
The proposed capability would organize signals and compare plausible constraints, but it cannot decide which weakness the company should accept. Founders must define the venture boundary, weigh evidence from customers and operations, and choose the response that fits their strategy and risk tolerance. The map should sharpen that judgment, not disguise a preference as an objective diagnosis.
Operating contract
Inputs, outputs, and gates
Inputs
- Venture concept
- Evidence about routines, roles, and relationships
- Founder constraints
Outputs
- Three-dimension diagnostic
- Binding-constraint rationale
- Thirty-day action
Gates
- Founder confirms the venture boundary
- Founder approves the binding constraint
- Founder accepts the proposed action
Known limits
What this record does not promise
- Implementation is blocked until the exact Assumption Ledger foundation bytes pass a different-vendor gate; composition has not yet been demonstrated.
- The diagnostic cannot substitute for evidence from customers or operations.
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.