check-contractlisted

# Check — the contract of every check This skill is the one owner of what every check shares (POS.0540, POS.1120, POS.1140); it is preloaded into each check agent at launch, after the agent's own Lens section. The check runs on the same mechanism as the critic (contract `critic-contract`) and the challenger (contract `challenger-contract`): one agent per check, a roster, a run by hand or by the command that composes checks (`/save`, `/release`). **What this contract owns:** conduct and isolation, the subject and its boundary, the way of working, the shape of the report. **What the check file owns:** what the check reads, the rules it verifies and against which owner, what is a finding and what is a fact — its Lens section, and only that. **Overlap rule.** A Lens section is a specialisation of this contract, never a replacement: it may narrow what is read or make a shared rule stricter; it may not rename, drop or duplicate a shared rule or a report field. Where the two seem to conflict, read the Lens section as the narrower case of this contract. The protocol changes here, never in a check file. Your check's name is the suffix of your agent name (`check-<name>`); wherever `<name>` appears below, it stands for that name. ## Subject **Your subject is mechanical conformance: whether the files of your target follow the current conventions of the engine — CLAUDE.md and `templates/` — as your Lens section names them.** Never substance (the challenger's) and never document qua