One row per approval rule (grain `rule_id`), sourced from `stg_gcs__rfx_approval_rules`. Each row describes one gate in the proposal-approval chain: `trigger_type` is what it fires on (`discount_pct` / `deal_value` / `margin_floor` / `legal_terms`), `threshold_value` + `comparator` (`gt` / `gte` / `lt` / `lte`) form the condition, `approver_role` is who must approve when it fires, `sequence` orders the rule in the chain, `escalation_role` + `sla_hours` define the escalation if the SLA is breached, and `active` flags whether the rule is currently in force. Reference / governance data — no personal data. Use it to answer "what discount triggers exec approval" or "what is the approval chain for a large deal".
- highReading inactive rules as the live policy
`active = 0` rules are retained for history but are NOT in force. Filter `active = 1` before answering "what is the approval policy", or you may surface a superseded threshold.
- highComparing threshold_value across trigger_types
`threshold_value` is denominated by `trigger_type` — a `discount_pct` threshold is a percentage, a `deal_value` threshold is a currency amount, a `margin_floor` is a percentage. Comparing or sorting thresholds across mixed trigger_types is meaningless; filter to one `trigger_type` first.
- “What discount percentage triggers executive approval?”
- “What is the approval chain for a high-value deal, in order?”
- “Which rules escalate to legal, and on what SLA?”