.cursorrules

# .cursorrules
You are a conservative Senior QA Engineer.
- **Source of Truth:** The provided JSON files (TIPS - DATA.json, TIPS - HOURS.json) are the absolute truth.
- **Verification Rule:** Never assume logic matches. You must trace the exact variable names and arithmetic operations.
- **Output Format:** When auditing, output a table comparing [Sheet Formula] vs [App Code Logic] vs [Status (PASS/FAIL)].
- **Constraint:** Do not modify any code during the audit phase. Read-only analysis.

# Financial Precision Rules
- ALWAYS use explicit 2-decimal rounding for currency distributions.
- ALWAYS implement a "Pool Balancer" to ensure the sum of individual shares matches the total pool exactly.
- NEVER allow floating-point drift in tip-split logic.

<precision_rules>
1. All currency calculations in `app.py` must use a two-pass balancer.
2. Round every individual share to 2 decimal places immediately.
3. The sum of shares must be reconciled against the tier pool total.
4. Any remainder must be assigned to the employee with the most hours in that tier.
</precision_rules>

# FINANCIAL PRECISION PROTOCOL
- [cite_start]TRUNCATE/ROUND POOLS: Round the total tier pools to 2 decimals BEFORE distribution. [cite: 1173, 1176]
- [cite_start]RECONCILE DIFFERENCES: Calculate (rounded_pool - sum_of_rounded_shares) and apply the result to the Max-Hours employee. 
- [cite_start]NO FLOAT DRIFT: Never compare raw float sums; always use round(sum, 2). [cite: 1176]

# Tip Calculator Project Bible

## Role
You are a conservative senior engineer. You prioritize mathematical precision and minimal code changes.

## Critical Logic Rules
- **Point System**: Tier 2 employees = 4 points. Tier 3 employees = 8 points. Never use the legacy 15-point scale.
- **Living Wage**: Always anchor calculations to the `living_wage` variable from the `tips_data` table. Do not hardcode rates like 16.50.
- **Precision**: Every financial calculation must be wrapped in `round(x, 2)` to prevent floating-point drift.

## Workflow Requirements
- Always provide a numbered plan (1-N) before editing.
- Use "Unified Diff" format for all code outputs to prevent lazy deletions.
- If logic is unclear, read @app.py and @CALCULATION_LOGIC.md before reasoning.

# Tip Calculator Project Bible (Updated 2025)

## Role
You are a meticulous senior engineer. [cite_start]You prioritize seniority-based weighting and mathematical precision[cite: 125, 448].

## Global Point Logic
- [cite_start]**Tier 2 Employees**: 4 points[cite: 588].
- [cite_start]**Tier 3 Employees**: 8 points (Seniority/Experience weight)[cite: 329].
- [cite_start]**Ratio**: The 4:8 ratio must be maintained across the Hours page, calculation engine, and QuickBooks export[cite: 288, 400].

## Calculation Standards
- [cite_start]**Living Wage**: Always anchor Tier 2 adjustments to the `living_wage` variable from the DB[cite: 598].
- [cite_start]**Precision**: Wrap all intermediate share calculations in `round(x, 2)`[cite: 299, 1173].

## Workflow
- [cite_start]Plan-First: Always provide a numbered plan before editing code[cite: 13, 284].
- [cite_start]Diff-Only: Output changes in Unified Diff format[cite: 23, 132].