Approval Tiers — Proposed Guide
Planned API — Reference OnlyApproval Tiers: Tiers can route review according to amount or another explicit risk criterion. Thresholds must be interpreted with a defined currency and…
Overview
Tiers can route review according to amount or another explicit risk criterion. Thresholds must be interpreted with a defined currency and boundary rule.
Key concepts
Specify whether a threshold is inclusive and whether currency conversion precedes tier selection. Use minor units.
Implementation considerations
Do not compare unlike currencies without a documented rate basis. A missing tier should block routing rather than grant approval.
Illustrative data model
This local fixture shows a possible representation for the concepts above. It is not an endpoint response, production configuration or a claim that the described capability is implemented.
JSON fixture
{
"reference_only": true,
"topic": "Approval Tiers",
"tier_id": "tier_example_123",
"amount_minor": 12550,
"currency": "USD",
"reviewer_ids": [
"usr_example_123"
]
}Design review checklist
- Document which organization owns the approval tiers representation and which actor may view or change it.
- Test the boundaries of tier id, amount minor, currency, reviewer ids using synthetic values, including missing or inconsistent references.
- Before future implementation, obtain an approved contract and review failure behavior. This documentation does not authorize production activation.
Proposed data types
| Name | Type | Description |
|---|---|---|
| tier_id | string | Stable fictional tier reference; not a secret and not evidence that a resource exists. |
| amount_minor | integer | Monetary amount in the documented currency minor unit; 12550 represents USD 125.50, not USD 12,550. |
| currency | string | Uppercase ISO 4217 currency code. Determine its minor-unit exponent before monetary conversion. |
| reviewer_ids | array<string> | Fictional reviewer references; validate ownership and avoid duplicate membership. |