# Stage And Owner Worksheet

Use this worksheet to define one observable outcome and the work that produces it. Share the agreed artefacts a receiver needs. Keep private chat transcripts and unrelated context out of the handoff.

## Define The Outcome

- Intended result:
- Audience or receiver:
- Deliverable and delivery requirements:
- Constraints that must hold:
- Evidence that the result succeeded:
- Human who accepts the final release:

## Describe One Stage

| Field | Your Contract |
| --- | --- |
| Stage name | |
| Accepted input and revision | |
| Required prerequisites | |
| Output artefact and format | |
| Next receiver | |
| Judgement or decision required | |
| Acceptance check and its evidence | |
| Owner: human, script, or model | |
| What the owner may propose or do | |
| What requires human approval | |
| What happens if the check fails | |
| Which downstream outputs become stale if this input changes | |

## Worked Illustration

This invented contract models a timed transcript for an animation that follows recorded speech. It is one possible workflow, not a requirement for every video production.

- **Input:** The reviewed voice recording, revision two.
- **Prerequisite:** The recording has passed a listen for pronunciation and completeness.
- **Output:** Words and ordered start/end times tied to that same recording, with declared time units.
- **Receiver:** The person or process creating the animation.
- **Judgement:** Whether captions match the spoken words and intended reading rhythm.
- **Structure check:** Timestamps parse, remain within the audio duration, and have valid start/end ordering.
- **Relationship check:** The transcript identifies the accepted recording revision.
- **Outcome check:** A human compares captions with the recording at transitions and any difficult passages. Sampling alone does not prove every word is correct.
- **Owner:** A script or model may propose alignment; a human accepts the timings used by the cut.
- **Failure:** Return the timing defect to the alignment stage before accepting animation input.
- **Change:** A new accepted recording revision marks the dependent transcript and animation for review.
- **Release:** Publishing the cut still requires human approval.

## Connect The Stages

Write each stage's prerequisites explicitly. Validate the prerequisite itself before using its output. Parallelise work only when it has accepted inputs it can use independently.

For the illustration: Script → Voice → Timed Transcript → Animation → Publish.

Before accepting a stage, ask:

1. Does its output exist and meet the declared structure?
2. Does it use the accepted input revision?
3. Does the receiver have evidence that it serves the intended outcome?
4. Who is allowed to accept it, and who can authorise release?
5. If it changes, can we identify which dependent work needs review?

A check establishes the bounded claim it tests. Keep final review even when intermediate checks pass.