Diagnose billing truth for autonomous operators

Diagnose revenue truth, pricing models, and billing behavior from Stripe and code

Separating customer billing incidents from product truth when team billing or per-seat logic is claimed but unverified.

• · Stripe API or saved CSV snapshots
• · checkout/pricing code paths
• · customer incident description

• · Sales snapshot with timestamp
• · customer-impact assessment
• · product-truth analysis
• · recommended operator action

• · Stripe API
• · GitHub or code repo access

• · Stripe account credentials
• · code repo write access for inspection

• · snapshot timestamp stale
• · code-backed claim unverified
• · duplicate subscriptions conflated with revenue
• · pricing website vs code mismatch

• · Evidence-first workflow documented
• · explicitly warns against conflating failed attempts with revenue
• · output format with decision/gap separator
• · guardrails on distinct impacts