Correctness

Run the review once per reference file. Do not merge lenses.

Scope

1. If the user names files or directories, use that scope.
2. Otherwise review the whole codebase.

References

1. Data Representation
2. Contract Invariants
3. Leaky Abstractions
4. Timing Correctness
5. Concurrency
6. Build Reproducibility
7. Fake Coverage
8. Flag Debt
9. Global State
10. Idempotency
11. Reliability
12. Silent Failure
13. Observability Gaps
14. Security & Trust Boundaries
15. Cache & Freshness
16. Single Source of Truth
17. Schema Evolution
18. Online Migrations
19. Time & Locale

Process

1. Pick the review scope.
2. Read one reference file.
3. Review the chosen scope only against that reference.
4. Repeat for every reference file in order.
5. Keep each reference as its own report.
6. If a reference has nothing material, write No findings.

Output

Emit one section per reference, in the same order as the list above.

Each section must include:

• Reference: the reference title
• Scope checked: files, directories, or areas reviewed for that reference
• Result: findings or No findings

For each finding, include:

• what is wrong
• evidence
• impact
• recommended fix