referencelisted

# Record what the project is A fact about the project's shape settled in conversation has no way to reach `WSS.record.reference` 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 settled what the stack, the data model or a convention is. This flag is that route — the same shape as `--wss-describe`, for the record one column over. **This skill decides nothing and writes nothing itself.** It resolves the record and hands the work to [`writers/WSS.REFERENCE-WRITER.md`](../../wss/workflow/writers/WSS.REFERENCE-WRITER.md), which is the sole writer of `WSS.record.reference` 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.reference` — an **array of paths**, not one — with the fallback in [`WSS.MANIFEST.md`](../../wss/workflow/WSS.MANIFEST.md). Say which you used. ## The file this reaches may be the project's landing page `--wss-describe` can never rewrite a README; this flag can, and that asymmetry is the one thing to hold in mind before anything is written. A manifest may map `README.md` into the reference array — that mapping is consent, and the writer's "never take over a README that was not offered" section is t