git:20260906.021b41c to git:20260908.fa6b0b0

---

name: implement

description: 'Execute one bounded RED to GREEN experiment from bead or caller intent; return derived subject identity and check facts. Triggers: "implement", "implement this bead", "run the experiment". Full plan-to-validation requests route to rpi.'

---

# Implement

Execute exactly one bounded experiment described by the resolved bead or caller

intent. Implement owns subject edits and factual evidence; the runtime derives

identity and receipts.

## Prompt

```text

Implement bead ag-1234 from its text: acceptance "ao gate check lists

skill.probe-coverage", scope cli/internal/gates/** plus regen outputs, first

check `cd cli && go test ./internal/gates/...`. RED first, smallest change,

return the manifest digest and check receipts, stop.

```

## It's working if

- Every path in `git diff --stat` falls inside the declared scope; an outside

consumer is reported as `file:line`, not absorbed.

- The response carries the `subject-manifest.v1` digest, author context ID,

and verbatim check output; no `git commit` or `git push` appears.

## Workflow

1. Read the intent, acceptance, and scope from their existing source; before

the first write, read `boundaries.md` in the rpi skill's `references`

2. Run the declared first acceptance check before changing behavior. RED-first

applies when acceptance is behavioral: preserve evidence that the check

fails for the expected missing behavior. Relocations, doc merges, and pure

refactors record an honest green pre-change baseline instead.

3. Make the smallest in-scope change that satisfies the active behavior.

4. Run the targeted acceptance checks and capture factual results.

5. Refactor only while those checks stay green. Refactoring does not change the

acceptance test.

6. Have the runtime derive actual changed paths and `subject-manifest.v1` from

the before/after subject.

7. Run `bash scripts/evidence-orphans.sh <changed paths>` over the changed

paths the runtime derived, and put its output in the check receipts the

validator reads, so orphaned evidence arrives as a receipt rather than as a

surprise at verify time. Run it again after every repair round, over the

paths as they stand, because a repair can orphan evidence the first pass did

not. Read the output as written and never hand-list the orphans instead.

8. Return the manifest digest, author context ID, and exact check receipts in the

response or runtime channel. Stop.

Specialists (standards, domain, test, refactor, security) advise only. During

edits, run the smallest deterministic checks that can falsify the change,

reuse exact-input receipts whose subject and tool identity still match, and

run the full suite at the integration boundary unless the intent makes it the

first check.

## Scope conflict rule

On discovering a live consumer of the change outside the declared write scope

(a test asserting the old path, a generated twin, a gate reading the moved

file), stop and report the exact file and line to the caller, who may revise

the intent and start a separate invocation; a different acceptance contract

is a new intent.

Before declaring GREEN, self-audit the diff for mocks, placeholders, TODO

stubs, hardcoded fixture values, weakened assertions, regenerated goldens,

widened tolerances, suppression directives, or specification edits standing

in for real behavior. A changed test, gate, fixture, golden, or acceptance

source must be required by the original intent, with green coming from the

implemented behavior; a check that passes against a substitute or weakened

oracle is not evidence: finish the behavior or report it as not built.

## Boundary

Do not commit, push, claim, close, release, land, reserve, retry, or invoke a

semantic validator. A failed check is evidence for the caller, not permission

to create a packet or validation loop.