# Shared consequence storyboard

Previous setup: Establish the actual problem and label any untested interpretation.

| Unit | Audience arrives with | Headline / point | Substance + status | Closing beat | Audience leaves with | Connection to next | Layout/use and alternatives | Missing input / format limit |
|---|---|---|---|---|---|---|---|---|
| 1 | The reader regards the issue as belonging only to the immediate participant. | A late return can delay someone else. | The intermediate relationship earns the shift. The final question now invites a service response instead of a generic reminder campaign. Fictional, not proof. | How might the service protect the handover? | The reader sees a second affected party and can judge whether the intervention should address their relationship. | Test a reservation handover that helps both households. | S06 / shared-consequence; alternative S90 | HTML only; real evidence required. |

Suggested next headline: Test a reservation handover that helps both households.

Copy says: Widening the view to a related party can reveal a more useful reason to act.

Image adds: The middle beat makes the affected next household the hinge between an individual deadline and a shared service question.

Together: The reader sees a second affected party and can judge whether the intervention should address their relationship.

Medium: editable HTML diagram and typography; no generated artwork needed. Canvas: 16:9 desktop; free-height responsive document on phone. Reading order follows the relationship and ends with the implication. Qualifications stay visible; no client assets.

Selected treatment: Three connected beats retain the S06 hinge, with the relational beat emphasised. A compact complete view compresses a paced reveal.

Alternative: S90 Before and after. Faster comparison, but the causal middle may disappear. Use only when that relationship is already established.

Count: Three reasoning roles are fixed: initial frame, relationship, revised question. See reuse.json for actually checked instances.