pattern detail
financial-actions-standing
Escalates or blocks money movement, refunds, and payment changes unless an operator has explicitly authorized the action path.
Pattern analysis
doctrinal basis
Positive Identification (PID), proportionality, and standing vs. special ROE.
Use the summary here for context, then inspect the YAML or related patterns for the concrete rule path.
What it catches
- Prompt injection that tries to convert a support task into a refund or wire action.
- Scope creep from “draft the response” into “issue the refund now.”
- High-blast-radius disbursements where the amount exceeds a standing cap.
Related patterns
policy yaml
The downloadable policy stays available below, but the inline YAML now wraps cleanly for narrow screens.
name: financial-actions-standing
version: 0.1.0
doctrinal_basis: >-
CJCSI 3121.01B standing-vs-special ROE; proportionality and PID principles
adapted for agent-executed financial actions.
description: Standing controls for refunds, credits, transfers, and billing mutations.
rules:
- id: deny-financial-default
applies_to:
action_class:
- financial.transfer
- financial.refund
- financial.billing.update
decision: deny
reasoning: >-
Financial action ${action_class} is not authorized by standing policy.
Require an operator-approved pathway first.
- id: escalate-refund-approved-ticket
applies_to:
action_class: financial.refund
decision: escalate
escalation:
requires: human_approval
via: finance-ops
reasoning: >-
Refund request for order ${order_id} must be approved by a human before execution.
- id: escalate-high-value-financial-change
applies_to:
action_class:
- financial.transfer
- financial.refund
conditions:
- type: blast_radius_max
parameter: amount_usd
threshold: 500
decision: escalate
escalation:
requires: both
via: finance-ops
reasoning: >-
Requested amount ${amount_usd} exceeds standing threshold for autonomous action.