Financial Decision Authority
Finance-first pack for transaction routing, payment authorization, override governance, and audit-grade decision traceability.
- Key
- finance
- Version
- finance-v1
- Rules
- 3
- Domain
- FINANCIAL_ROUTING
Rules, in the order the evaluator tries them
Highest priority first. The first rule whose conditions all hold decides; with none, the decision is a REVIEW.
Escalate high-value payment authorization
priority 160high-value-authorization-escalation · PAYMENT_AUTHORIZATION
When- intake.amount ≥ 100000
ThenESCALATE → ESCALATE · urgent · SLA 10 min
Manual override requires deterministic reason code
priority 150manual-override-reason-required · FINANCIAL_GOVERNANCE
When- override.requested = true
ThenREQUEST_INFO → REVIEW · urgent · SLA 15 min
Manual overrides without structured reason codes create escalation ambiguity and audit fragility.
Policy snapshot required for routing decisions
priority 140policy-snapshot-required · FINANCIAL_ROUTING
When- policy.version exists
ThenREQUIRE_REVIEW → REVIEW · elevated · SLA 30 min
Routing decisions must carry an explicit policy snapshot to remain defensible in audits.
Evaluate under it
Locally, with @decionis/mcp: the payload becomes the request's context, and its action the decision type. On the hosted protocol, once the bundle is stored for your organization, name vertical_pack, policy_version and require_exact_policy_version: true.
decionis_evaluate arguments
{ "policy_pack": "finance", "payload": { "action": "<decision type>" } }In a hosted evaluate-decision request
"vertical_pack": "finance",
"policy_version": "finance-v1",
"require_exact_policy_version": trueWhat its rules read
Every fact below comes from the request's context.
- intake.amount
- override.requested
- policy.version
Signals it maps
- routing_policy_drift_ratecore_banking_orchestrator
- auth_decline_anomaly_ratepayment_switch
- credit_routing_override_ratiocredit_decisioning
- override_without_reason_countmanual_approval_console
