Loop 001
The product contract conformance loop
A product-quality loop that turns a business logic or product contract document into an evidence-backed implementation audit.
Ready-to-use prompt
Copy the loop.
Audit [project] against [product contract document]. First extract every concrete product promise, business rule, permission rule, background job expectation, user-facing workflow, non-goal, and quality bar from the contract into a requirement ledger. For each requirement, find current evidence in code, configuration, tests, docs, jobs, migrations, routes, UI, prompts, queues, and production-safe runtime state. Mark each requirement proved, weak, contradicted, unimplemented, N/A with reason, or blocked with missing evidence. Fix only confirmed high-impact mismatches one bounded slice at a time, preserving unrelated work, adding regression coverage where practical, and rerunning the affected ledger checks. Ask before touching production, secrets, user data, destructive operations, or changing public claims. Stop only when every requirement is proved or honestly classified and the ledger contains no silent gaps.Verify / stop
Every product promise is proved, classified, or blocked.
The requirement ledger has no silent gaps: each rule is supported by current evidence, marked not applicable with a reason, fixed, or returned as blocked.
Use this when
Use this when a product contract, spec, launch note, or business-rule document has become the source of truth and the implementation needs to be checked against it directly.
How to run it
- Extract concrete promises, workflows, permission rules, background jobs, non-goals, and quality bars into a ledger before reading implementation details.
- Trace each ledger item through code, configuration, tests, documentation, routes, UI, jobs, prompts, queues, and safe runtime evidence.
- Classify each item as proved, weak, contradicted, unimplemented, not applicable with a reason, or blocked by missing evidence.
- Repair only confirmed high-impact mismatches in bounded slices, preserving unrelated work and adding regression coverage when it materially protects the rule.
- Rerun the affected checks and finish with the ledger, evidence, fixes made, and any blocked gaps.
Why it works
Product audits often drift into impressionistic review. A contract ledger makes the work concrete: every claim must be proved, repaired, excluded, or honestly blocked.
Implementation note
Ask before touching production systems, secrets, user data, destructive operations, or public claims. Missing access is a blocked finding, not a clean pass.