ONE TREASURY SPINE. NO ACTION DEFINES ITS OWN AUTHORITY.
The Treasury Execution Rights Engine is a generic infrastructure for deterministic domain determinations over bound financial, institutional and external states. Factoring is not the engine itself; it is Action Type 01: FACTOR_RECEIVABLE.
Two phases. One hard execution boundary.
The Rights Pipeline may issue a bound capability. It does not own actual execution. Beyond the Execution Boundary, an authorized external executor verifies the capability and performs the action.
PHASE 1 · TREASURY RIGHTS PIPELINE
- Action Proposal
- Normalization
- State Binding
- Action-specific domain determinations
- Execution Policy
- 5-Dimension Rights Closure
- Freshness Validation
- Capability Issuance
PHASE 2 · AUTHORIZED EXECUTOR
- Capability Verify
- Actual Execution
- Execution Result
- Execution Receipt
- Evidence Binding
Ten domain determinations. None of them is execution permission on its own.
The factoring adapter supplies domain results to the Spine. External ratings, legal assessments or accounting states may inform the determination, but they do not acquire authority by doing so.
Economic Arbitrage
Net arbitrage against an institutionally defined minimum threshold. Monetary arithmetic uses integer minor units.
Liquidity Constraint
Liquidity floor, minimum buffer and available headroom after the modeled transaction.
Counterparty / Debtor Risk
Bound credit/risk state against authorized thresholds. A PUBLISHED_RATING remains an external input.
Concentration / Exposure
Debtor, sector, country and provider limits as integer basis points.
Contract / Assignment Eligibility
Assignability, dispute state, duplicate assignment and permitted contractual parameters with provenance references.
Accounting / Balance-Sheet Effect
Pro-forma metrics and a bound derecognition state. Accounting qualification remains a referenced input.
Sanctions / AML / Entity State
No absolute “sanctions-free” claim: the bound source state and its freshness are evaluated.
Temporal Validity
Discount, offer, credit, policy and other time-bound states. UNKNOWN fails closed.
Jurisdiction Closure
Seller, debtor, factor, payment, governing law and account location. Cross-border cases may require review.
Execution Policy
Institutional triggers such as amount thresholds, cross-border status or recourse. Policy remains separate from domain determination.
Five dimensions. No shortcut.
No action type may define this semantics itself. Only the Spine resolves whether all required dimensions are closed for the specific action.
A capability must not outlive any state it depends on.
The effective validity bound is derived from the earliest relevant limit. For freshness-sensitive external states, observation time, freshness window, derived and explicit bounds, and the effective bound are documented separately.
ISSUED is not EXECUTED.
The Spine produces a Capability Issuance Receipt. Only the actual executor produces a separate Execution Receipt after a real action. Permission and actual execution therefore remain evidentially separate.
What the Spine records
Action type, bound state references, domain determinations, closure, freshness, validity window and SHA-256-bound determination. ISSUED ≠ EXECUTED.
What the executor records
Capability reference, actual execution time, execution result, settlement reference and a separate evidence binding for the real execution.
Rules no action type may bypass.
Domain Determination ≠ Execution Authorization.
No capability without closed Authority, Rule, Jurisdiction, Time and Dependencies for the specific action.
Probabilistic or external inputs may inform, but do not acquire authority by being consumed by the system.
Every unresolved required state fails closed and produces no capability.
An override does not mutate the original determination; it creates a new attributable state.
A Treasury action type may define its own domain gates. It may not define its own execution-rights semantics.
Action Type 01 is implemented. Additional Treasury actions can use the same Spine.
The following action types are architectural targets and are not presented as already implemented production functions.
| # | Action Type | Domäne | Status |
|---|---|---|---|
| 01 | FACTOR_RECEIVABLE | Receivables financing / factoring | IMPLEMENTED |
| 02 | TAKE_EARLY_PAYMENT_DISCOUNT | Early-payment discount / working capital | PLANNED |
| 03 | DRAW_CREDIT_LINE | Credit line | PLANNED |
| 04 | REPAY_CREDIT_LINE | Credit line | PLANNED |
| 05 | MOVE_LIQUIDITY | Liquidity management | PLANNED |
| 06 | EXECUTE_FX_HEDGE | FX Hedging | PLANNED |
| 07 | EXECUTE_RATE_HEDGE | Rate hedging | PLANNED |
| 08 | INITIATE_CASH_POOL_TRANSFER | Cash pool | PLANNED |
| 09 | INITIATE_SUPPLIER_FINANCE | Supply chain finance | PLANNED |
| 10 | EXECUTE_DYNAMIC_DISCOUNT | Dynamic discounting | PLANNED |
| 11 | CREATE_INTERCOMPANY_LOAN | Intercompany funding | PLANNED |
Not another Treasury dashboard. An explicit authorization boundary before execution.
The relevant difference is not an unsupported claim that other systems “cannot do this.” It is the explicit separation of domain determination, external authority, rights closure, capability issuance, actual execution and evidence.
Domain gates bring domain logic. The Spine owns execution-rights semantics. The external executor owns the actual action. Evidence keeps the respective states separate.
What this architecture does not claim.
Processing can be deterministic even when individual external inputs originate from ratings, assessments or institutional sources.
The engine does not create regulatory, judicial or statutory authority. Authority remains external and must be bound.
SHA-256 binds payloads and makes changes detectable. Stronger evidentiary properties arise only through the intended signed or append-only evidence infrastructure.
A capability permits execution within its bound scope. Only a separate executor can perform the actual transaction.
Fail-closed is a technical and institutional execution rule, not a judicial determination.
Cryptographically bound evidence improves traceability and attribution but does not create automatic liability exclusion.
From proposal to capability. From capability to separately evidenced execution.
For institutional review, architecture discussions and controlled technical due diligence.