docs(wiki): the declarations and readings the standard leaves to the operator Five pages beside the README and RULES.md, for what those documents specify precisely and leave to judgement. Choosing a profile and level names the common mistake: declaring L0 on a surface that carries analytics, which produces a permanently red gate describing decisions already made deliberately. The level is a declaration of what the surface is, and a conformant L2 is worth more than a permanently red L0. Reading a report separates the four outcomes and explains why INCONCLUSIVE blocking is the design rather than a rough edge, why UNSCANNABLE emits no score at all so a site that is down cannot look merely imperfect, and why the score is level-relative and environment-sensitive while the medal is the claim. It also flags the practical trap: a CI image without a headless browser silently converts the runtime egress proofs, the strongest evidence in the standard, into INCONCLUSIVE. Fixing the first run gives the order that works, starting from self-hosting because it removes the exfiltration path rather than constraining it and makes the CSP writable. Waivers covers what the four governance rules buy, including the debt ceiling as a forcing function, and where the runner deliberately stops: it governs the mechanics, not whether a justification is true. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>