Instructions

An "active user" is defined as a user with at least one session 
in the last 30 days. Use this definition for all activity-based metrics.

When analyzing customer data, always use the `customers_prod` table 
instead of `customers_staging`. The staging table contains test data.

The `status_code` column in the orders table uses these values:
- 1: Pending, 2: Processing, 3: Shipped, 4: Delivered, 5: Cancelled, 6: Refunded

MRR = SUM(subscription_amount) WHERE billing_frequency = 'monthly'
+ SUM(subscription_amount / 12) WHERE billing_frequency = 'annual'
+ SUM(subscription_amount / 3) WHERE billing_frequency = 'quarterly'

When joining tables on *_id fields, always cast integer IDs to strings 
or vice versa to avoid type mismatch errors. Example:
JOIN table2 ON table1.user_id::text = table2.user_id

Always search data source metadata resources (dbt, markdown) 
before selecting tables.

If user asks about financial tables, be extra cautious 
and ask for clarifications.

For Sales metrics, default to bar chart by category or time
unless user requests otherwise.

Place key KPIs at the top. Prefer bar/area charts for trends.
Avoid raw tables unless specifically requested.

---
alwaysApply: true
references:
  - customers
  - orders
---

# Customer Lifetime Value

CLV = SUM(order_total) WHERE customer_id = X AND status = 'completed'
Use 12-month lookback window from analysis date.

---
alwaysApply: false
references:
  - transactions
  - accounts
---

# Financial Data Dictionary

## Transaction Types
- CREDIT: Money coming in
- DEBIT: Money leaving
- TRANSFER: Movement between accounts