# Connected MVP: release decision

Project/version: __________  Decision owner: __________  Date: __________

**Decision:** limited pilot / revise / stop

## Product promise tested
Person, trigger and inspectable result: __________

## Evidence
- Cases run and source snapshot: __________
- Acceptance results (attach case IDs): __________
- Observed user behavior: __________
- Outstanding failure or uncertainty: __________

## Conditions chosen before the pilot
Required correctness conditions: __________
Required access conditions: __________
Required user-understanding conditions: __________

## Interpretation
What the evidence supports: __________
What it does not establish: __________

## Next release boundary
Included users and tasks: __________
Excluded actions: __________
Fallback when unavailable: __________
Source owner: __________
Tool owner: __________
Next review date: __________

### Fictional example of a useful revision decision
"Revise the result card before expanding. The eligibility tests passed, but the coordinator could not find the approval date without opening another screen. Add that field to the card, then repeat the uncoached task. No additional tools are needed for this revision."
