implementlisted

# Implement ## Entry gate Require: - approved scope, non-goals and acceptance criteria; - costly-to-reverse decisions approved or expressly parked; - build ceiling and write/external authority; - `config/risk-policy.json` risk/authority profile: minimum tier, bounded paths, disclosure, secrets and external-action constraints; - `evaluate` need for stochastic/judgement-bearing behaviour. If missing, use `scope`; never infer owner decisions. For active service or safety impact, user-approved containment may parallelise verification and review. Gates and authority apply; name a reconciliation run. ## Loop 1. For substantial+ work, create the canonical `delivery-run` with profile `software` through the complete installed-producer command in `deliver`, then follow [run-contract.md](references/run-contract.md). Routine minor work may proceed without `RUN.json` unless the user or project policy requests one. 2. Keep an adaptive plan. Name the governing skill in the worker contract before changing code. Invoke `tdd` for every new or changed observable behaviour, and use `refactor` for behaviour-preserving structure and `diagnose` for unknown causes. Migrations may need behaviour tests and equivalence evidence. Use `orchestrate` when decomposition helps; adapt topology inside authority. For a version-sensitive external interface or migration, apply [source grounding](references/source-grounding.md) and [migration compatibility](references/migr