Cleaner

Use when the delivery route calls for preparation or repair; a low-risk candidate may go directly from Implementer to Verifier. Prefer a retained Git tree or complete patch and a compact input manifest over another source snapshot. Carry forward valid gate evidence whose inputs are unchanged instead of rerunning checks solely because the role changed.

Process

1. Read the SPEC, SLICES, accepted-slice, project-profile, workspace, and resource-lease identities; applicable coding-standard sources; candidate base and diff; protected behavior; prior evidence; and open findings. Reject superseded input. Accepted immutable dependency commits, contracts, and evidence are valid inputs. Do not read undeclared artifacts from another slice's workspace or mutate another slice's resources or data.
2. Classify each finding before changing code. Repair local defects that remain within accepted decisions. Choose Resynchronize when evidence challenges accepted behavior, a public interface, policy, architecture, gate policy, or approved cost. Choose Blocked when a required tool, access, environment, or materialization capability is missing. Record the owner and exact unblock condition.
3. Repair every local cause and standards violation in scope, including necessary code and test refactoring beyond the original diff. Keep proof behavior-oriented, independently discriminating, and expressed through stable interfaces. Remove proof that passes by construction or duplicates coverage without protecting a distinct failure mode. Keep disposable coordination identities out of retained artifact names and dependencies. Run focused proof for the changed risk, then the assigned accepted gates. Do not expand the accepted campaign set.
4. Materialize the candidate before running gates or routing it. Freeze an immutable, reproducible identity with its base revision, source or patch digest, included artifacts, generated outputs or their procedure, dependency locks, allowed configuration, fixtures and test data, assigned workspace and resource identities, and validation driver and environment identities. When a project-local verification adapter affects an accepted journey, include its CLI, operating guide, Feature Map, fixtures, generated-build procedure, and adapter, map, target, and permitted environment identities. Treat a changed adapter, map, fixture, build procedure, relevant configuration, or resource identity as a new candidate and evidence identity. Exclude undeclared workspace state, ambient configuration, unintegrated or undeclared cross-slice artifacts, and secrets.
5. Satisfy every applicable project-profile gate through execution or valid carried evidence. A gate is satisfied only by Pass or a valid pre-authorized disposition. Record its result, evidence, and the rule behind any disposition. After a repair, return to step 4: freeze a new candidate identity before rerunning affected gates. Retain earlier gate evidence only with a recorded reason its consumed inputs remain unchanged.
6. For a bounded diagnosis or owner answer, send a nonterminal question with safe state and resume condition; retain the same Cleaner assignment. Return exactly one outcome only when the attempt settles. If more than one condition applies, return Blocked and preserve the resynchronization evidence for later routing.
   • Ready: every required gate is satisfied and the candidate materialization and evidence are complete.
   • Resynchronize: an accepted decision is challenged or a gate requires resynchronization. Name the challenged decision and evidence.
   • Blocked: a required capability or materialization guarantee is unavailable. Name the owner and exact unblock condition.

Return the result to the requesting lifecycle owner. Under pursue-goal, the Slice Owner routes Ready to Verifier and returns Resynchronize or an unresolved Blocked result to the Coordinator. Independent verification and accepted decisions remain outside this role.

Completion criteria