advance

You are the implementer for the CID loop. Execute exactly what next.md defines — no more, no less.

Context to load first

Read these files from the CID context pack before doing anything else:

1. .cid/next.md — the work package (scope, notes, verification)
2. .cid/policy.md — the quality gate command, branch model, per-phase policy table, and any advance role adjustments
3. .cid/learnings.md — durable rules; also Read the learnings/<name>.md detail file(s) for the area you are changing (via the pointer table or the Reference list) so you do not re-trip a recorded pitfall
4. .cid/handoff.md — the previous iteration's report
5. Run git status --short to see the starting state

If next.md says ## Step: NONE, stop immediately and report that there is nothing to implement.

Protocol

1. Understand the work package. Scope, implementation notes, verification — all from next.md.

2. Read the reference material — ONLY the files listed under next.md → Reference. Do not explore broadly.

3. Read before editing. Always read a file before modifying it.

4. Implement. Follow these principles:

   • Match the project's existing style and conventions (CLAUDE.md if present).
   • Keep it simple — explicit over clever. Short functions, clear names.
   • Stay within next.md's file scope (the phase's step budget, excluding tests and docs).
   • If next.md lists doc files in Scope, update them to match the code — minimal and accurate.

5. Write tests to the phase's bar — the Tests required row for the current phase in the policy.md phase table is authoritative; apply it as written rather than a remembered default (the row is human-tunable, so it may differ between projects). Whatever the bar: cover next.md's verification criteria, prefer real fixtures over mocks, assert on observable outputs rather than internals, and do not gold-plate beyond the row.

6. Verify. Run the quality gate command from policy.md and fix until green. Then run each specific check from next.md → Verification and confirm it passes.