---
requires: scratch/vsm-s5-scan.md
produces: scratch/vsm-s5-assessment.md
---
Assess identity and policy.
## Orientation
Before starting, orient yourself in this branch:
- Read `scratch/` — design docs and notes for the current work live here
(`scratch/<branch>.md` is this PR's design; `scratch/questions.md` holds open
questions and assumptions).
- Read wave/PM context only when the seed names the exact wave, task, project,
or a concrete coordination question; never infer it or repair access as a
prerequisite.
- Read the repo's agent doc (`CLAUDE.md` / `AGENTS.md`) for conventions.
Write design artifacts, notes, and open questions under `scratch/`. Don't
re-derive what these already record.
## Goal
Turn the s5 scan into structural judgment.
Decide whether this chord owns the right territory, has the right member waves,
and is granting the right autonomy. Surface pressure points specific to
identity, boundary, membership, and policy.
## Workflow
1. Read `scratch/vsm-s5-scan.md`.
2. Judge chord identity, boundary, roster, autonomy, and direction drift.
3. Separate urgent structural concerns from observations that can wait.
4. Produce pressure points specific to identity and boundary.
## Output
Write `scratch/vsm-s5-assessment.md`:
```markdown
# VSM S5 Assessment — <date>
## Summary
<is this still the right chord for this territory?>
## Identity and Boundary
<fit, drift, missing ownership, overlap>
## Member Roster
<which waves fit, which do not, what may be missing>
## Policy and Autonomy
<direction / trigger / autonomy assessment>
## Pressure Points
1. <highest-leverage identity or boundary concern>
2. <second>
3. <third, if needed>
```
## What to avoid
**Local backlog grooming.** Stay at identity and policy altitude.