Learn · Module detail
soft launch vs full launch
Use a soft launch when the ledger, member message, fulfilment, or support process still needs evidence. Move to a full launch only after the controlled release shows that the promise works end to end.
## The mechanism
Define the qualifying event, value change, owner, correction path, and member explanation. Keep eligibility, liability, fulfilment, consent, and reversal as separate rules. The operating control must be testable from the ledger.
## Worked example
Illustrative arithmetic: a soft launch with 25 members produces 50 earn events and 10 redemption events. A later release with 200 members would produce 400 earn events at the same activity rate.
## Do it
State the rule in one sentence. Map the event that starts it, the event that changes value, the exception path, and the review action. Test ordinary, cancelled, duplicated, and disputed cases before release.
## Common mistakes
- Measuring activity instead of the target behaviour. Name the counterfactual. - Treating face value as operator cost. Price fulfilment and correction. - Hiding exclusions or expiry. Put the boundary beside the decision. - Automating an undefined rule. Resolve ownership before implementation.