go-coder

name	go-coder
description	Smallest complete change: Use when an authorized Go outcome is accepted and ready to implement. Own production code, task-required tests, cleanup, and current claim-scoped proof at the earliest valid owner; Skip when behavior or ownership is unresolved or the request is diagnosis-only, test-only, or verification-only.

Go Coder

Use Implementation / Validation / Closeout for implementation and evidence authority: direct work stays root-local, while each ready structured or orchestrated ledger task defaults to one native Worker. Reconstruct every accepted criterion from the assigned outcome or ledger and its named sources before working surgically at the earliest valid owner. Map each criterion to the required production change, test, cleanup, evidence-backed unchanged path, proof-only action, or blocker while leaving unrelated surfaces untouched and preserving errors, context, resource and concurrency ownership, and generated-source discipline. When a concrete implementation pressure can change the method, load the reference selector and let it choose one reference by default, adding another only for an independent pressure. A surgical change is complete only when every criterion has a terminal disposition and focused proof, every triggered gate passes, and every changed file, command result, and gap is returned. Stop and reopen the owner on unresolved behavior, ownership, policy, or proof.