Prototypes

Deliberate prototypes are generated from completed product and market cases:

/deliberate case <id> prototype

A product case gets a native-medium prototype of the primary journey. Match the artifact to how customers actually experience the product rather than defaulting to a web page.

A market case gets a testable customer-touchpoint artifact, such as:

• a landing or pricing page;
• a message or campaign sequence;
• a sales narrative;
• a partner offer.

The strategy and platform cases do not force prototypes. Their decision record, recommendation, commitments, and revisit conditions are the reviewable output.

The resulting artifact belongs beside the evidence and reasoning that produced it. This keeps the prototype tied to the case rather than treating a demo as self-validating proof.

A useful prototype:

• walks every shaped product-journey step in order or tests one decisive market hypothesis at its real customer touchpoint;
• includes the meaningful failure, recovery, objection, or alternate path rather than only the happy state;
• reuses the product’s real visual, command, API, agent-tool, brand, and copy conventions from connected sources;
• uses believable, project-grounded content;
• makes every promised interaction reachable and clearly distinguishes mocked data from evidence;
• remains inspectable without a proprietary hosted tool;
• records which case and assumptions it represents;
• can be reviewed and replaced without losing the decision history.

Prototype polish should match the fidelity needed to learn. Higher fidelity is not automatically better evidence.