Proof Compliance Audit

Context

Use this skill when the repo contains proof templates, attestation levels, compliance workflows, or regulated-industry evidence handling. It is most useful when specs, Prisma models, Zod validators, and service logic may have drifted apart.

Patterns

• Review the proof cluster together: templates-attestation-spec.md, proof-taxonomy.md, proof-vault-spec.md, sharing-spec.md, rbac-api-spec.md, and app-spec.md.
• Confirm the six top-level proof types before looking for missing concepts. Most gaps are subtype, lifecycle, or policy gaps rather than missing top-level types.
• Treat attestation as how proof is established and proof taxonomy as what is being proven.
• Check whether schema optionality undermines regulated behavior. Nullable or free-text proof classification is usually a compliance risk.
• Treat expiration as an immutable historical event plus next-cycle work, never as evidence erasure.
• Require separation of duties for Level 4 validation and prohibit proof-type-invalid attestation combinations.