Banking & payments
Where an unauthorized transfer cannot be un-sent
A payment that leaves is gone. Recovery is a commercial process, not a technical one, which is why the decision has to happen before the instruction is transmitted rather than after it is observed.
The actions that are not recoverable here
Governance is worth its cost where the effect cannot be undone by correcting a record.
Payment initiation
An agent that can initiate a transfer needs the limit reserved and the destination checked before the instruction is transmitted, not reconciled afterwards.
Counterparty and beneficiary changes
Adding or altering a payee is the action most often targeted, because it converts a permitted payment into a loss without breaking any limit.
Ledger and position adjustments
Corrections that move balances need an approver who is not the requesting system, and a record that survives the system that made them.
Customer data and account state
Status changes — freezes, releases, limit changes — carry the same authority requirements as money movement.
What a reviewer will ask
Each of these is answered by an artifact rather than by a description of a process.
Who authorized this specific instruction, and under which policy version
Answered from the signed decision record: acting identity, principal, policy version, decision, approver where one exists, and the execution result.
Whether a human approved it, who they were, and what exactly they approved
Answered from the signed decision record: acting identity, principal, policy version, decision, approver where one exists, and the execution result.
Whether the record could have been written by the system that made the payment
Answered from the signed decision record: acting identity, principal, policy version, decision, approver where one exists, and the execution result.
What happened to instructions in flight when authority was withdrawn
Answered from the signed decision record: acting identity, principal, policy version, decision, approver where one exists, and the execution result.
The controls that answer them
Pre-execution authorization
ProvenEvery governed action is authorized before it executes, not observed after. The decision to allow, hold or deny is taken against the active policy inside the same write transaction that reserves the budget and consumes the approval, so a policy change lands entirely before or entirely after an action — never halfway through one.
Human approval, bound and single-use
ProvenAn action held for approval produces no effect until a separately authenticated human with the required role approves that exact request. The approval is bound to the payload and the envelope, is consumed once, and cannot release a different action or the same action twice.
Budget and action limits
ProvenSpend and action limits are reserved atomically inside the authorization transaction. A limit lowered below what is already spent stops further spend without rewriting history, and the change is recorded as a signed configuration record naming the principal who made it.
Revocation of agent authority
ProvenAn authorized operator can revoke an agent. Its next request cannot execute, and an action it had already had approved but not yet dispatched cannot execute either — revocation reaches work already in flight, not only new requests.
Signed, hash-linked evidence
ProvenEach decision, authorization, outcome, refusal and configuration change is written as a signed record in a hash-linked chain. The record carries the request identity, the policy version, the decision, the approver where one exists, timestamps and the execution result.
Offline independent verification
ProvenEvidence is verified by a portable verifier with no database, no signing key, no network and no product installation on the path. Deliberately altered evidence — an edited amount inside a signed body, a stripped signature, a broken chain link, a checkpoint re-signed by the writer's own key — is refused, and a verifier that cannot run reports an instrument failure rather than a refusal.
Limitation · The verifier was written by the same party as the system it checks. Verifying with it confirms signatures, linkage and key separation; it is not a substitute for an independent implementation of the documented record format.
Relevant frameworks
EU AI Act, ISO/IEC 42001, ISO/IEC 27001 control mappings. Coverage is stated control by control, with gaps named. ApexClaw holds no certification and displays no certification badge.