Coordination
The coordination rule is simple: a conversation can start work, but durable work needs a durable surface.
Coordination matters most when context is split across tools, people, or work sessions. The goal is not to add ceremony. The goal is to make sure the next step is clear and the important context is findable.
Operating Pattern
- Pick the work area.
- Read the current context.
- Create or update a work record when work needs ownership or follow-up.
- Use notes for restartable context.
- Review with link checks, screenshots, or rendered pages.
- Close with the next exact step.
Lane Choices
| Lane | Use when |
|---|---|
| Direct work | The task is immediate, local, safe, and does not need a separate durable owner. |
| Work record | The task needs ownership, acceptance criteria, review, or follow-up. |
| Restart note | A future work session needs readable restart context. |
| Reference material | A project needs searchable context without turning every note into public content. |
Review Habit
Coordination is not complete just because a message was sent. A useful closeout names what changed, where the durable reference lives, how it was checked, and what the next step is.
Boundary
The public version shows how coordination works at a useful level: work areas, reference material, review, and closeout. Raw working notes, secrets, restricted tokens, and access details stay out of the site.
