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/safety impact, approved `mode: expedited-incident` may parallelise containment verification/review. Gates and authority still apply; name a reconciliation run. ## Loop 1. For substantial+ work, create the canonical `delivery-run` from `../deliver/templates/RUN.template.json`, set profile `software`, and 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. Use `tdd` for observable change, `refactor` for approved behaviour-preserving structure and `diagnose` for unknown causes. Migrations may also need behaviour tests and equivalence evidence. Use `orchestrate` when decomposition or independent coverage helps; adapt topology/order inside authority. For a version-sensitive external interface or migration, apply [source grounding](references/source-grounding.md) and [migration compatibility](references/migration-compatibility.md). 3. Run deterministic checks; map e