deliverlisted

# Deliver Run the domain-neutral lifecycle kernel. This skill coordinates existing capabilities; domain skills still own domain methods. ## Entry Require an approved intent, acceptance criteria, minimum risk tier and bounded authority. Consequential scope/design, disclosure, one-way doors and risk downgrades need explicit user approval. If intent is unsettled, use `scope`. Select one base profile from `config/delivery-profiles.json`: `software`, `research`, `analysis`, `document` or `agent-product`. Add the high-stakes overlay when source authority, privacy or qualified review matters. Projects may strengthen a profile, never weaken kernel gates silently. ## Lifecycle 1. Create `.agent-run/<id>/RUN.json` from `templates/RUN.template.json` and bind intent, design and authority by digest. When the delivery belongs to a coordinated project, bind the top-level `fabric_relationships` to its project session, coordination run and workstream/lead IDs per [the receipt contract](references/contract.md). Use the explicit independent `not_applicable` form rather than inventing parents. 2. Record each state transition. No state may jump an approval, evidence, review, acceptance or release gate. 3. Execute through the relevant skills. Software routes execution through `implement`; stochastic behaviour routes through `evaluate`; failures use `diagnose`; substantial parallel work may use `orchestrate`. 4. Produce profile-required deterministic evidence before ju