Implementer

Role definition

Implements the frozen plan and records RED and GREEN evidence.

Source Roles

Proofline works with Claude Code and Codex beta. Codex is supported in the implementer role. Seen in real use: Claude took over when the Codex limit was reached.

Source Runtime role override

What it does and must not do

• DoesImplements exactly the frozen PLAN.md: smallest correct change, existing patterns.
  Must notExpand scope, touch a path outside PLAN scope:.

  Source Role definition

• DoesRecords RED (unsuccessful for the stated reason), GREEN and optional REFACTOR via agent.sh worker-evidence (the script writes worker-evidence/)
  Must notCount a compile or import error as RED; write a test that cannot fail (hollow)

  Source Role definition

• DoesRespects each tdd_exemption as written in the plan.
  Must notInvent an exemption, disable, skip or weaken a test.

  Source Role definition

• DoesFixes a FAIL finding only within its fix_scope, one round per assignment.
  Must notFix unrelated issues, do unrelated cleanup, refactor beyond the plan.

  Source Role definition

• DoesUses debug-proof for a bug: reproduce, prove root cause, regression test in scope.
  Must notEdit TASK, EVIDENCE, PLAN, QA_PLAN or any review or gate artifact.

  Source Role definition

• DoesAdds only dependencies listed in PLAN Dependencies.
  Must notWeaken security, bypass validation or hooks, add an unlisted dependency.

  Source Role definition

How it works

1. Read the assignment, task, evidence, read-only QA plan, and only the source and tests inside scope. Read the required PLAN sections separately, adding Data, UI, or Architecture only when the assigned scope touches them.

   Source Method

2. Check linked ADRs and whether the frozen plan can be implemented; report a conflicting ADR as a blocking finding. If work needs an unplanned path, dependency, contract change, or destructive operation, stop and report the required addition, reason, and impact for the lead to resolve.

   Source Method

3. For each scoped path, follow tdd-proof in team mode: write the test, record RED and its expected failure, implement, and record GREEN. Include one fenced JSON ledger in the report, with a cycle for each non-exempt path and criterion; record refactoring only when useful.

   Source Method

4. For a defect, follow debug-proof in team mode to reproduce it and prove the root cause, write the numbered debug report, and keep its regression test inside scope.

   Source Method

5. Run the plan verification commands that apply to changed paths and report pre-existing failures without fixing them.

   Source Method

What it produces

• Report with agent.sh submit; the script builds and validates the result header, fingerprint and hashes, assigns finding ids, and returns any rejection immediately. Correct the reported problem and submit again; the final conversational message is not parsed as the result.

  Source Output

• The report lists each resolved finding id, marks it closed, and cites the GREEN record as evidence. It also lists pre-existing failures and any needed scope addition for the lead to address.

  Source Output

Where it acts

Related roles and skills

Source

Source Role definition