development-contract-processlisted

# Development Contract Process Find the repo's contract policy file for paths, record locations, lanes, and validation profiles. It owns contract mechanics within the host's instruction hierarchy; it does not override higher-authority task constraints. Inspect a policy/documentation mismatch before deciding which artifact needs correction. This is a process overlay, not a thinking aid. Pair it with the repo's implementation skill for the touched code and any repo-local contract overlay that names the actual policy path and helper commands. ## Activity and authority - Review or planning: inspect policy, records, and enforcement; return findings or a proposed contract without modifying files. Write a record only when the requested output or an authorized implementation workflow requires it. - Implementation: maintain the required record as part of the already-authorized change. Do not ask again for ordinary record updates covered by that scope. - A policy file or declared command does not authorize installation, publication, or other consequential side effects. Inspect commands before running them; executable policy files are code, not inert configuration. ## Policy discovery If the repo-local overlay does not name a policy file, search for likely contract artifacts before guessing: `change-contract-policy`, `feature_records`, `check-change-contracts`, lifecycle helper scripts, and AGENTS/README language about substantive changes or verifier evidence. Once found