describelisted

# Describe the running system A rule settled in conversation has no way to reach `WSS.record.behaviour` on its own. Every other route into that record is a side effect — an inspecting or building caller dispatches to the writer when it happens to notice a gap, and none of them fire because someone decided how the system should behave. This flag is that route. **This skill decides nothing and writes nothing itself.** It resolves the record and hands the work to [`writers/WSS.BEHAVIOUR-WRITER.md`](../../wss/workflow/writers/WSS.BEHAVIOUR-WRITER.md), which is the sole writer of `WSS.record.behaviour` per [`WSS.OWNERSHIP.md`](../../wss/workflow/WSS.OWNERSHIP.md). The whole of what to write, how much, and what that record may not hold is that procedure's — read it rather than restating its rules here. **Project facts come from `.claude/WSS.WORKFLOW.json`**: `WSS.record.behaviour`, with the fallback in [`WSS.MANIFEST.md`](../../wss/workflow/WSS.MANIFEST.md). Say which you used. ## What reaches this flag, and what does not `WSS.record.behaviour` holds **what the system does at runtime** — auth rules, ownership rules, state transitions, visibility rules, error statuses, ordering guarantees. Three neighbours are routinely handed here and each belongs elsewhere: | Handed here | Actually | Route | |---|---|---| | *Why* the rule is that way | reasoning | `--wss-log` | | A rule decided but not built | a plan, not the running system | `--wss-log` | | Stack, architecture, data model,