---
status: ready-for-dev
slug: story-slug
parent-spec: SPEC.md
owner: human
created: YYYY-MM-DD
---

# Story: <name>

One bounded, dispatchable work unit. A story is coherent, independently finishable,
and carries everything the implementing agent needs without inventing decisions.

## Context

- Parent spec or intent contract (link).
- The slice of the contract this story owns.
- What is already true in the codebase (verify, do not assume).

## Acceptance criteria

- Observable, binary outcomes (PASS/FAIL possible).
- Each criterion traces to a contract capability or constraint.

## Boundaries

- In scope.
- Out of scope (and where deferred items are tracked).
- Architecture decisions already made that this story must preserve.

## Implementation notes

- Files or components expected to change (draft; the implementer verifies).
- Commands with non-obvious prerequisites.
- Known pitfalls observed in this area.

## Verification

- Tests to run (focused first).
- Evaluations or manual observations required.
- Independent review needed? (separate evaluator where risk warrants it)

## Status history

- `ready-for-dev` — passed readiness.
- `in-progress` — implementation underway.
- `in-review` — review/triage underway.
- `done` — completed and accepted.
- `blocked` — cannot continue safely; routing signal.