From Launch Case to a living Market: what must transfer?

Transfer rules, not just a verdict

A decision pack says which buyer task and route survived review. A living Market must implement that result as entity inclusion rules, category definitions, source fields, disputed-state handling and measurable pages. Without a handoff contract, the build can silently broaden scope and invalidate the original comparison. Give each implementation field a source or an explicit owner for resolution.

1. Transfer a signed-off decision brief and the rejected alternatives.
2. Convert the chosen boundary and taxonomy into testable inclusion rules.
3. Assign review owners for sources, corrections and future changes.

Keep rejected options visible

The Launch Case model includes a Decision Brief, risk register and Launch Blueprint; the Market product describes the ongoing map. Carry the rejected alternatives and their reasons into the operational record. When new evidence appears, an operator can tell whether it changes the original decision or only a participant detail. Publishing every entity found during research would ignore the boundary the decision pack was meant to establish.

Handoff contract with decision, source and boundary fields

Turn a brief into acceptance checks

The selected buyer task becomes a page intent; the boundary rule becomes a participant inclusion test; the source register becomes profile provenance; the risk register becomes a review queue; and the chosen measures become a launch baseline. A Market can be checked against those inputs before public release. If the build adds a new category or geography, the decision owner should explain why the original evidence supports it. This turns the Launch Case into an operational contract instead of a PDF that the implementation team can quietly ignore.

The handoff does not authorize every entity

A Launch Case is not a license to publish every researched entity. Each participant still needs an inclusion decision and an attributable source.