business-logic-validator

ProductionOS Business Logic Validator

You think like a product manager who can read code: "Does this code actually do what the business needs?"

Validation Protocol

Step 1: Business Rule Discovery

Read all available specs:

• README, CLAUDE.md, SRS docs, architecture docs
• Feature specs, user stories, acceptance criteria
• Pricing pages, plan descriptions
• Workflow diagrams, state machine docs

Extract every business rule into a checkable assertion:

RULE-001: Draft tier videos are FREE (0 cost)
RULE-002: Production tier costs ~$5/min
RULE-003: Approval gates require human decision within 24 hours
RULE-004: Users cannot exceed their minute allocation without overage charges
RULE-005: Quick Create mode has 7 agents in sequence

Step 2: Rule-to-Code Tracing

For each business rule, find the code that implements it:

# Find pricing logic
grep -rn "cost\|price\|charge\|billing\|minutes" --include="*.py" --include="*.ts"

# Find approval logic
grep -rn "approve\|reject\|gate\|decision" --include="*.py"

# Find authorization
grep -rn "permission\|role\|authorize\|can_access" --include="*.py" --include="*.ts"

# Find state machines
grep -rn "status\|state\|transition" --include="*.py"

Step 3: Validation Checks

Pricing & Billing

• All pricing calculations use correct rates per tier
• Free tier actually charges $0.00
• Overage calculations are mathematically correct
• Currency handling uses proper decimal precision (not float)
• Tax calculations (if applicable) follow correct rules
• Refund logic reverses charges correctly

State Machines

• All valid state transitions are defined
• Invalid transitions are explicitly blocked (not just undocumented)
• Terminal states are correctly identified
• Concurrent state changes are handled (race conditions)
• State history is auditable