Verify Before Done

Separate implementation, verification, provisioning, and production claims.

Load each named skill through the host mechanism; call the Skill tool when exposed. Do not reload an active skill.

Authority

• Verification only: run or inspect evidence; do not mutate code, tests, config, fixtures, or external systems to make it pass.
• Implementation finishing: fix an authorized in-scope cause exposed by verification, then rerun the affected check.

If the request asks only whether existing work is correct, use verification-only mode.

Assertions

• Recover requirements from the request, repository, tests, types, and owning boundary.
• Define the smallest observable assertions that prove the change. Add a negative assertion only when required by accepted behavior or policy.
• Do not invent UX, authz, idempotency, data, or deployment policy. Surface missing policy as an unverified boundary.
• Keep evidence proportional to risk and coupling.