Skip to content

The run record of a complete task

Every task an agent carries out leaves its run record, the complete audit trail. This one is for a banking task: the agent’s plan, who approved it, every change on the core with who authorized it and with which account, and the rules applied, with hashes to verify it.

  • 6 min 3 sDuration
  • 2 and 2Reads and changes
  • 2 of 2Changes approved by someone else
  • 73f640c5ed65…Plan fingerprint

The run, step by step

Pick a step to see what the run record says.

Record the source-of-funds proof that has already arrived for TRX-RET-9002 and release the transfer.

Banking core in COBOL and CICS at Bank of Z, a sample bank

Completed
Agent
Banking operations
Started by
Lucía Prieto · Back office
Approved the changes
Andrés Molina · Operations lead
Duration
6 min 3 s
Started
November 4, 2026 at 10:41:58 GMT+1
Status
Completed
From
Agents
Rules
Version 7

Plan ·

Plan proposed, checked and signed

The agent proposes 2 reads and 2 changes. Reelease checks the agent and its rules and signs the plan: if anyone alters it, it doesn't run. Whoever starts the task reviews and approves it.

Proposed by
The agent, with the system's AI model
Steps
4 (2 reads and 2 changes)
Plan approved by
Lucía Prieto · 10:42:31
Plan hash
73f640c5ed65…

The plan

What the agent proposed before touching anything, turned into a Sealed Plan: the platform sealed it with this hash, and what ran is what was approved.

Version 1
The agent, with the system's AI model
Plan approved by
Lucía Prieto · 10:42:31
Comment
Plan reviewed: two reads and two changes, RTRY last.
Hash
73f640c5ed6544313b8bb0789015683d48f26bac07d5aaa082c4090ff5b814fe
  1. 01

    Read transfer TRX-RET-9002

    GTRX

    Status, amount and accounts of the transfer with GTRX.

    Read only

  2. 02

    Check why it is held

    GRET

    Hold reason and missing documents with GRET.

    Read only

  3. 03

    Record the source-of-funds proof

    RTDC

    Mark SOURCE_OF_FUNDS as received with RTDC.

    Changes data: waits for someone else

  4. 04

    Retry the transfer

    RTRY

    Release it with RTRY, the last step, once no document is missing.

    Changes data: waits for someone else

Who decided what, and when

Every decision a person made, with the rule that applied.

  • Approve the plan

    Approved
    Requested
    Lucía Prieto · Back office · 10:42:04
    Decided
    Lucía Prieto · Back office · 10:42:31
    Rule
    —
    Comment
    Plan reviewed: two reads and two changes, RTRY last.
    Exceptions
    None
  • Approve “Record the source-of-funds proof”

    Approved
    Requested
    Lucía Prieto · Back office · 10:42:41
    Decided
    Andrés Molina · Operations lead · 10:47:12
    Rule
    Someone else, never the requester
    Comment
    Source-of-funds proof checked on the customer file. Go ahead.
    Exceptions
    None
  • Approve “Retry the transfer”

    Approved
    Requested
    Lucía Prieto · Back office · 10:47:15
    Decided
    Andrés Molina · Operations lead · 10:47:58
    Rule
    Someone else, never the requester
    Comment
    No document is missing. Release it.
    Exceptions
    None

Every action on the core

The agent’s calls, in order. Each change carries the approval that authorized it and the hash of its parameters, never the data.

  1. Read transfer TRX-RET-9002

    GTRX
    Via
    Reelease integration gateway, with Lucía Prieto’s account on the system (LPRIETO)
    Outcome
    Done
    Approval
    Not needed: read only
  2. Check why it is held

    GRET
    Via
    Reelease integration gateway, with Lucía Prieto’s account on the system (LPRIETO)
    Outcome
    Done
    Approval
    Not needed: read only
  3. Record the source-of-funds proof

    RTDC
    Via
    Reelease integration gateway, with Lucía Prieto’s account on the system (LPRIETO)
    Outcome
    Done
    Approval
    Per action, by Andrés Molina · 10:47:12
    Parameters hash
    e23737b7f0fe21a2aac075a49d9e3bb16c4bc14b6369c5b1be684b9321dffb81
  4. Retry the transfer

    RTRY
    Via
    Reelease integration gateway, with Lucía Prieto’s account on the system (LPRIETO)
    Outcome
    Done
    Approval
    Per action, by Andrés Molina · 10:47:58
    Parameters hash
    5ff4ce51c3fc8f8d6d9a95b78e83965766063384fd627493cf7b41f588125ada

The rules that applied

The version of the agent’s rules the plan was signed with. If an admin changes the rules later, this run record still says which ones applied.

Version
Version 7
Source
The agent's rules on the platform, signed with the plan
Who approves changes
Someone else, never the requester
Where the rule comes from
System rules
System rules version
3

The hashes that prove nothing changed

The sha256 hashes the run record keeps. The plan hash can be recomputed from its steps: if it doesn’t match, the plan was altered.

Plan hash (sha256 of its steps)
73f640c5ed6544313b8bb0789015683d48f26bac07d5aaa082c4090ff5b814fe
Parameters hash · Record the source-of-funds proof
e23737b7f0fe21a2aac075a49d9e3bb16c4bc14b6369c5b1be684b9321dffb81
Parameters hash · Retry the transfer
5ff4ce51c3fc8f8d6d9a95b78e83965766063384fd627493cf7b41f588125ada
Rules hash
e0d448d1756de21705299b15e53315b06588d9ce39aa81040b20508fb059d199
System rules hash
23a243fb739e4475a5bef28939d84ceadb6bab116ff2c8b4ef78234887f64693
Signed manifest hash
2910b6b1d7489e141af89190624857378aed915274cf28f8b48386afd7cd4543

Check it yourself

Recompute this record's fingerprints in your browser, with the same code Reelease uses, and see that they match. Nothing leaves your device.

Recomputes the fingerprint of the approved plan, the fingerprint of each change's exact values and the manifest's Ed25519 signature with the example public key.

See the values and the key being checked

Approved values of each change, by approval:

{
  "approval:action:registrar-justificante:e23737b7f0fe21a2": {
    "endpointId": "bank-of-z.RTDC",
    "payload": {
      "transferId": "TRX-RET-9002",
      "documentType": "SOURCE_OF_FUNDS",
      "documentRef": "DOC-88412"
    }
  },
  "approval:action:reintentar-transferencia:5ff4ce51c3fc8f8d": {
    "endpointId": "bank-of-z.RTRY",
    "payload": {
      "transferId": "TRX-RET-9002"
    }
  }
}

Example public key (reelease-ejemplo-publico-2026):

-----BEGIN PUBLIC KEY-----
MCowBQYDK2VwAyEAQwyydBst0o6q58QTCLhwHI6nkCuxd01KnDZoZ8JK4eg=
-----END PUBLIC KEY-----

A sample task carried out with demo data from Bank of Z, a fictional bank: no real people or accounts. The plan and change hashes are computed as on the platform; the rules and manifest hashes are examples. Every task your agents carry out leaves a run record like this one.

Back to Controls and evidence

Want to walk through security with us?

You choose the cookies

We use technical storage to remember your choice and, only if you accept, analytics cookies (Google Analytics) to understand how the site is used. You can change your choice at any time. Learn more in our cookie policy.