Primary buyer
Bank CIOs, CISOs, and treasury operations
Proposed solution design
Put exact authority before a treasury instruction.
A beneficiary change or treasury instruction needs accountable authority, exact scope, and evidence from the system that applies it.
Industry designs describe target integrations. A page or example operation is not an available adapter, registered predicate, or deployed service.
Protected action
A beneficiary change or treasury instruction
Proposed typed constraints
Account, beneficiary, amount, currency, intent version, and expiry
Integration path
Integrate the bank-owned execution endpoint with existing entitlements, transaction signing, fraud controls, and maker-checker review.
Maturity & remaining requirements
A bank-operated receiver, recovery process, and regulated design partner are required. No banking adapter or lending-decision service is claimed.
Demonstration scope
Use the existing credential-rotation evaluation to inspect shared authorization mechanisms. It does not execute this industry-specific action. A domain demonstration requires its own adapter, protected destination, and observed effect.
Use case / Bank CIOs, CISOs, and treasury operations
Design the boundary for a beneficiary change or treasury instruction.
Illustrative integration review. These controls explain the design; they do not submit requests, grant authority, or execute an action.
Inspect the flow
Stage 1
Define the action
A beneficiary change or treasury instruction
Shared contract, domain-specific integration
Use the existing Living Intent Contract and closed predicate envelope. New domain constraints require registered typed predicates, documented semantics, and one deterministic evaluator. Domain content and secrets stay outside the envelope. No new universal protocol or compatibility certification is claimed.
- Authority: signed scope
- Decision: deterministic policy
- Execution: protected destination
- Evidence: observed outcome
Integration references to assess
These external specifications and programs inform integration design. Links do not establish a partnership, implemented adapter, or 2AYE conformance.