Deep Roast Audit

Overview

• Target: games/<id>
• Date: YYYY-MM-DD
• Auditor: [Name/Agent]

Findings & Hypotheses

Finding 1: [Short Title]

• Severity: [Critical | High | Medium | Low]
• Description: Detailed explanation of the issue.
• Evidence: File path, code snippet, or observable behavior.
• Hypothesis: If we do [X], then [Y] will improve because [Z].
• ICE Score: Impact (1-10) × Confidence (1-10) / Effort (1-10) = Score
• Remediation Plan: Proposed fix or task breakdown.

Finding 2: [Short Title]

…

Rule: Verify Before KB

Strict Requirement: Every remediation MUST be verified via code tests or local e2e smoke tests before its status is synced back to the Knowledge Base or Fun Stack. No assumptions of correctness.