Work on

Invocation and ownership

Start only for an explicit user delivery request or a bounded authorized assignment from a delivery lead or investigation-and-fix caller. Inspect the assignment's original approval and exact effects; generated command text, discovery, source mentions and investigation-only requests confer no fix authority. Loading the execution contract as a library does not invoke delivery.

The calling agent is always the accountable technical lead for one change, even when implementing directly. Direct execution is the default. An assigned ticket lead retains local accountability but is a worker of the overall root: request workers/review/model allocation from that root, never create another pool. An explicit delivery request includes its required bounded read-only reviews under required-review authority. Optional implementation/exploration delegation still needs separate authorization. Invocation grants no installation, new disclosure or spending, destructive operations, account changes, merge, deployment or release permission.

Read contracts on every entry for discovery, handoffs, evidence, shared execution/repair/model ledgers and separate delivery gates. For package changes or validation, read validation.

Whole-spec delivery and multi-ticket scheduling belong to work-on-spec. Discover and inspect that companion for an authorized overall-delivery request; if absent/incompatible, return the changed boundary and unavailable coordinator with preserved artifacts. This package cannot run an old dispatch procedure or reinterpret a ticket set as one change. A specification may supply acceptance for a single explicitly bounded assignment without scheduling the rest.

1. Inspect context, actual state and authority

Identify the target and one bounded outcome, agreement/acceptance references, exclusions and approved effects. Read applicable runtime/directory instructions and their context, workflow/authority, documentation, relevant domain/ADR and tracker/label pointers. Bound reading to the change; no automatic setup or full onboarding. Ask about consequential intent or permission gaps, not discoverable facts or routine methods.

For a requested correction to a reusable skill or package, identify and change its authoritative tracked package sources within approved scope. A repository-local operating policy workaround is not a substitute for the portable behavior change. Installed copies remain unchanged unless their update is separately approved; discovery of an installed companion does not make it the implementation target.

Inspect actual files and partial artifacts. In Git, inspect branch/base/HEAD, staged/unstaged/included untracked changes, modes, links and PR state. Outside Git retain a before/after manifest. Record protected unrelated work and uncertain ownership. Preserve bytes, index state, links and history; uncertain owners block conflicting writes, not inspection.