implement

Implementation Plan

Creates a structured plan, tracks it with the host agent's todo/task mechanism, and executes with TDD as the default rhythm. When beislid:agent_isolation is configured, load workspace placement plus the current host adapter. Only with that block present, run ensure_orchestrator_workspace before the first repo write and place_mutating_delegate before each mutating dispatch. When the current host is Codex and a subagent dispatch is planned, load Codex delegate context just before dispatch even when agent isolation is not configured. Also load it when a smoke fixture explicitly requests protocol proof.

If the handoff includes an explicit design artifact path from blueprint, read it as your primary input; design artifacts are checkpoint-compatible state seeds for implementation planning. Otherwise, if the matching blueprint_approved latest pointer entry for the current ticket/branch resolves to a readable artifact, read that artifact as your primary input; if not, use the workflow-configured artifact path template when present, then look for a matching design artifact in plans/ using the ticket/feature slug when known (for example, plans/<feature>-design.md from blueprint). If exactly one match exists, read it as your primary input. If multiple candidates remain, ask the user to choose the artifact path. Only fall back to conversation context when no design artifact is available.

If the handoff includes an approved execution-envelope-v0, treat its autonomy boundary as execution context for this agent or an external runner: allow lists pre-approved work, ask creates human approval stops before continuing, and deny is out of scope. The envelope may carry Beislið ProcessProvider semantics such as selected contracts, slices, proofs, gates, guides, model hints, action-policy boundaries, and capability/probe status. Do not reinterpret an envelope as a runtime service, parser, durable run store, Rondo adapter contract, or replacement for Work Contract requirements.

If the user is resuming with phrases such as continue this ticket, continue implementation, or continue from checkpoint, read .beislid/checkpoints/latest.json when present. Prefer an implementation_plan_created checkpoint matching the current branch and ticket ID when known; otherwise fall back to a matching kickoff_context_ready checkpoint or ask the user to choose among matching latest entries. Read the referenced checkpoint artifact as primary context before falling back to conversation context. Missing, unreadable, or malformed latest pointers are non-blocking; warn when malformed, then ignore the pointer and fall back to a matching checkpoint artifact or conversation context. If durable run-ledger state is available, beislid run-ledger resume --flow implement --ticket-id <id> --branch <branch> may identify the latest running/interrupted/failed external run, but checkpoint artifacts/design artifacts remain the primary content seed for implementation planning.

Action-risk decisions follow action-policy-protocol.md; read it before checkpoint writes, workspace edits, dependency installs, local git operations, or configured side-effect hooks. For durable run evidence when ticket/branch context is known, follow the nopal-seam-protocol.md fallback ladder. With mode: off, use beislid run-ledger init --skill implement --flow implement. Otherwise probe(nopal_seam) and, only when the probe is ok and capabilities[] contains ledger, call nopal ledger init --skill implement --flow implement --json. Under mode: prefer, an unavailable probe, missing ledger capability, or failed Nopal call warns and falls back to beislid run-ledger init; under mode: require, the same condition blocks instead of falling back. Record transcript-safe events for plan creation, task-batch starts/completions, verification results, and interruptions. When a workflow checkpoint artifact is written, add a checkpoint through the same seam (nopal ledger checkpoint --json or beislid run-ledger checkpoint) with --run-id <run_id> --flow implement --name implementation_plan_created --resume-hint <resume_hint> so the resume hint stays attached to the run. Ledger failures warn only on a fallback-eligible Beislid path and never replace task tracking, verification, or checkpoint artifact behavior.