Specification body

Create DOC with data.kind=spec. Link idea, research, ADR/glossary and the selected artifact.

## Problem and intended outcome
## Actors and user flows
## Complete scope / explicitly deferred scope
## Settled decisions and terminology
## Behavior, interfaces and state transitions
## Data ownership, privacy and authorization
## Error, offline, conflict and recovery behavior
## Acceptance criteria and verification methods
## Dependencies, migration, rollback and documentation
## Open decisions with owners

Example criterion: “Given the assigned PC is offline, editing the title shows Pending device and does not increment the applied record. After reconnect, the local Markdown and private projection contain one new revision; retries do not create another.”

A useful verification method names browser/API/file observations and replay input. Do not substitute “write unit tests” for an evidence plan. If a model-dependent scenario cannot run until selection, keep it visibly pending rather than deleting it from the spec.