Intended use
What this kit is being designed to do
- Reduce a concept to one testable behavior
- Design evidence before building
- Precommit to outcome decisions
Business mini-lecture
Learning speed beats feature volume.
Startups often build too much before learning whether the behavior they need will happen. A minimum-feature prototype isolates one important claim and creates the smallest honest experience capable of testing it. The value appears when a team can state the user action it needs to observe but does not yet need a complete product, polished infrastructure, or broad feature set.
The proposed capability would connect an assumption to a prototype, evidence criteria, and a decision rule established before results arrive. It cannot decide which customer behavior matters strategically or whether qualitative evidence is persuasive enough to continue. Founders must approve the claim, represent the artifact honestly, and decide in advance what support, refutation, or ambiguity will trigger a change, another test, or a stop.
Operating contract
Inputs, outputs, and gates
Inputs
- Priority assumption
- Target user behavior
- Test budget and constraints
Outputs
- Test-ready prototype or faithful mockup
- Support and refutation criteria
- Outcome decision rule
Gates
- Founder approves the claim being tested
- Founder confirms the prototype is represented honestly
- Founder accepts the decision rule before the test
Known limits
What this record does not promise
- The kit has not been implemented or tested with users.
- A mockup must not be represented as a functioning product.
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.