# Response gate storyboard

Previous setup: Define the purpose of the service and the requests within its remit.

| 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 assumes every incoming opportunity needs a response. | Respond when the contribution is useful. | The instruction evaluates value before format, and makes doing nothing visibly part of the process rather than an accidental omission. Fictional, not proof. | No useful contribution means no response. | The reader can distinguish a qualifying opportunity from one that should receive no action. | For a qualifying request, choose one response and assign an owner. | S58 / response-gate; alternative S73 | HTML only; real evidence required. |

Suggested next headline: For a qualifying request, choose one response and assign an owner.

Copy says: Checking contribution before selecting a response prevents activity from becoming an end in itself.

Image adds: One shared question governs two labelled outcome columns. Response methods appear only within Yes, with an explicit choose-one instruction.

Together: The reader can distinguish a qualifying opportunity from one that should receive no action.

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: Conditional-table variation of S58: a single governing criterion and explicit No/Yes outcome columns. It is not the default package comparison or a reproduction of source geometry.

Alternative: S73 Step rows. Makes process order explicit but does not encode a gate. A branching process would need a separately reviewed composition, not a fill of its linear rows.

Count: Two fixed outcomes; the repeatable count is response methods inside Yes. See reuse.json for actually checked instances.