# Foundation Sprint Brief: [Initiative name]

<!-- One-page pre-sprint artifact. The team and Decider sign off on this as the contract for the next two days. -->

## Initiative Statement and Stakes

[One paragraph. Four sentences max. What is the team sprinting on? Why does the direction matter? What would a wrong direction cost?]

## Decision the Sprint Must Unlock

[Single sentence framing the open strategic question the sprint resolves. State it as a binary or bounded choice: "X vs Y," "which of [list]," "should we commit to [direction] or its alternative."]

## Sprint Logistics

| Element | Value |
|---|---|
| Dates | [Day 1 date] and [Day 2 date] |
| Hours | [start]:[end] each day |
| Location | [In-person address / Remote video / Hybrid with details] |
| Format | [Workshop with shared whiteboard / Pure remote / etc.] |
| Tools | [Whiteboard tool, video, decision log location] |
| Daily rhythm | [Standup time, lunch, day-end review] |

## Team Roster

| Attendee | Role | Day 1 AM | Day 1 PM | Day 2 AM | Day 2 PM |
|---|---|---|---|---|---|
| [Name] | Decider | required | required | required | required |
| [Name] | Facilitator | required | required | required | required |
| [Name] | [PM / Design / Engineering / Customer expert / etc.] | [required / cameo / optional] | [...] | [...] | [...] |
| [Name] | [Role] | [...] | [...] | [...] | [...] |

[Cameo experts, if any, listed separately with the specific section they attend.]

## Existing Inputs to Bring

[Bulleted list, 5 items maximum. Each item names the artifact and who owns bringing it.]

1. **[Artifact]** ([Owner]). [What it is; why it matters in the sprint.]
2. **[Artifact]** ([Owner]). [...]
3. **[Artifact]** ([Owner]). [...]
4. **[Artifact]** ([Owner]). [...]
5. **[Artifact]** ([Owner]). [...]

## Success Criteria

The sprint is **successful** if:

1. [Outcome 1, named in observable terms.]
2. [Outcome 2.]
3. [Outcome 3.]
4. [Outcome 4.]

The sprint is **unsuccessful** if [the explicit failure conditions: missing output, ratified hypothesis that is not testable, or scope drift].

## Readiness Reaffirmation

[The Go verdict from `tool-foundation-sprint-readiness` was issued on [date]. Has anything changed since?]

- [ ] Decider availability still confirmed for both days.
- [ ] Preconditions from the readiness assessment (if any) are closed.
- [ ] No new risk factors have surfaced (e.g., key team member out, scope creep).
- [ ] If Conditional Go: the named yellow flags have been addressed.

If any box is unchecked, the brief is incomplete; close the gap or postpone the sprint before proceeding to Day 1.

## Decider Checkpoint

**Decider sign-off required before Day 1 begins.**

- [ ] Decider confirms scope: the named Decision the sprint must unlock is the deliverable.
- [ ] Decider confirms team roster and attendance windows.
- [ ] Decider confirms success criteria.
- [ ] Decider acknowledges that the sprint will NOT preserve all directions at the end of Day 2; one becomes the top bet, the other becomes the backup or is dropped.
- [ ] Decider commits to attending the Day 2 closing session where the Founding Hypothesis is ratified.

**Signed:** [Decider name, role], [ISO date and local time]
