Executive Summary
Treasury inflow — a configured percentage of realized profit-close events — is allocated across five configured jurisdictions and, within each jurisdiction, split between a grant-capital sub-pool (the large majority of the inflow) and an operations sub-pool (the remainder). Every disbursement drawn against a jurisdiction's grant-capital is reserved against that jurisdiction's outstanding pre-clearance verdicts in real time, so a jurisdiction can never authorize disbursements beyond its own allocated and available capital.
The closed-loop element: funds recovered through a multi-stage recovery-case workflow route back into the SAME jurisdiction's grant-capital pool, not a general or shared treasury, so a jurisdiction's own enforcement recoveries directly replenish its own future grant capacity. Every allocation and recovery event is recorded to an anchored, tamper-evident ledger.
Problem Statement
Single-pool global treasuries have no jurisdictional segmentation: one jurisdiction's misconduct or under-recovery dilutes every other jurisdiction's available capital. Traditional grant-management software typically treats recoveries as generic accounts receivable, with no automatic re-routing back to the originating jurisdiction's own capacity, breaking the accountability loop between enforcement and future grant-making.
Why Existing Solutions Are Insufficient
- Single-pool global treasuries: no jurisdictional segmentation, so one jurisdiction's misconduct dilutes every jurisdiction's capital alike.
- No reservation discipline: obligations tracked informally, capable of exceeding available capital before anyone notices.
- Recoveries dumped into a general fund: breaks the jurisdiction-level accountability loop between enforcement and future capacity.
- Manual reconciliation of grants vs. recoveries: error-prone and not continuously anchored to a tamper-evident ledger.
Technical Architecture
| Jurisdiction | Role in the Allocation Set |
|---|---|
| United States | One of five configured jurisdictional grant-capital pools |
| Switzerland | One of five configured jurisdictional grant-capital pools |
| United Arab Emirates | One of five configured jurisdictional grant-capital pools |
| Singapore | One of five configured jurisdictional grant-capital pools |
| Brazil | One of five configured jurisdictional grant-capital pools |
Inflow and Split
A configured percentage of each profit-close event becomes treasury inflow. That inflow is apportioned, independently for each jurisdiction, between a grant-capital sub-pool receiving the large majority of the allocation and an operations sub-pool receiving the remainder.
Reservation Discipline
Every outstanding pre-clearance verdict issued for a jurisdiction reserves a corresponding amount against that jurisdiction's grant-capital balance, reducing its disbursable capacity in real time. This prevents over-commitment: a jurisdiction's already-authorized-but-not-yet-disbursed obligations are always reflected in what it can newly authorize.
Recovery Re-Routing
A multi-stage recovery case — detection through final reconciliation — tracks funds previously disbursed from a jurisdiction's grant-capital sub-pool. On successful completion, the recovered amount is routed back into the grant-capital pool of the SAME jurisdiction from which the original disbursement was made, recorded against a dedicated recovery-routing field and anchored to the evidentiary ledger, closing the loop between enforcement and future grant capacity.
Prior Art Differentiation
| Approach | Jurisdictional Segmentation | Reservation Discipline | Recovery Handling |
|---|---|---|---|
| Single global treasury pool | None | Ad hoc | Generic fund top-up |
| Traditional grant-management software | Varies | Manual reconciliation | Generic accounts receivable |
| Sovereign-wealth-fund-style allocation | Jurisdiction-level | Varies | Not systematically closed-loop |
| JIL Sovereign | 5 configured jurisdictions | Real-time, verdict-reserved | Closed-loop, origin-jurisdiction re-routing |