AXES Example (Fin) · Financial services · run APRUN-2026-06-09-A

Your branding here

Autonomous Execution Report

An example report produced to the AXES open standard.

This is an example. The branding slots show where your organisation's identity would sit. The standard is open; the report is yours to brand.

This is the forensic view - prepared for dispute resolution and investigations roles.

Read it as you would a report that crossed your desk. The questions at the end ask what it would need to be one you could rely on.

Forensic Execution Pack - APRUN-2026-06-09-A

1. Verification procedure (vendor-neutral)

  1. Read envelopes.jsonl in sequence order. 2. For each envelope, remove integrity.envelope_hash and integrity.envelope_signature; serialise with RFC 8785 JCS; SHA-256; compare to stored hash. 3. Confirm previous_envelope_hash equals the prior envelope’s hash (genesis = 64ב0’). 4. Confirm sequence numbers are contiguous. 5. Confirm anchoring.anchored_subject_hash at each attestation_recorded event equals the chain head before it, and that anchor_requested_at is not before that record’s emitted_at. 6. Re-hash each file in artifacts/ and compare with manifest.json. Steps 1-6 are reproducible from the bundle alone. Step 5 shows internal consistency only: the in-trace anchors are basis_status: simulated. The external existence bound is on the release, not the trace: the release statement committing to this corpus is anchored with RFC 3161 and OpenTimestamps (repository RELEASES.md, VERIFY.md).

2. Envelope sequence (first 24 of 76; full stream in envelopes.jsonl)

Seqevent_kindPay#occurred_atenvelope_hash
0001execution_started-2026-06-09T09:00:00.000Ze38296d9b9d8…
0002context_retrieved-2026-06-09T09:00:04.000Z8994865a0194…
0003plan_created-2026-06-09T09:00:09.000Z516f6dfaa15c…
0004policy_check_performed12026-06-09T09:00:12.000Zbc6b8e2f8757…
0005commit_attempted12026-06-09T09:00:18.000Z5f4777135bd1…
0006tool_invoked12026-06-09T09:00:19.000Z233631960ce2…
0007commit_succeeded12026-06-09T09:00:21.000Z86eee284570f…
0008policy_check_performed22026-06-09T09:00:57.000Z52c2bfef03ba…
0009heartbeat_event-2026-06-09T09:01:00.000Z741e26e97a1e…
0010commit_attempted22026-06-09T09:01:03.000Z7940ca1e390a…
0011tool_invoked22026-06-09T09:01:04.000Zb370697e8d06…
0012commit_succeeded22026-06-09T09:01:06.000Zc4013507b775…
0013policy_check_performed32026-06-09T09:01:42.000Za6b6a30ab223…
0014commit_attempted32026-06-09T09:01:48.000Z8ab9fc75b2b9…
0015tool_invoked32026-06-09T09:01:49.000Z4bd343bf0c05…
0016commit_succeeded32026-06-09T09:01:51.000Zf88ee8003282…
0017heartbeat_event-2026-06-09T09:02:00.000Z4e8dd50fa21a…
0018policy_check_performed42026-06-09T09:02:27.000Z54ee51315be5…
0019commit_attempted42026-06-09T09:02:33.000Z328c47be3dde…
0020tool_invoked42026-06-09T09:02:34.000Z7b7dfab85a1d…
0021commit_succeeded42026-06-09T09:02:36.000Z4e91af83faea…
0022heartbeat_event-2026-06-09T09:03:00.000Z6e803aeed0ed…
0023policy_check_performed52026-06-09T09:03:12.000Zf41632fb5d16…
0024commit_attempted52026-06-09T09:03:18.000Z9c7f0af81208…

3. Payment ↔ artifact ↔ confirmation linkage

#EndToEndIdAmountBeneficiaryInvoicepain.001 hashpacs.002 hashCommitted at
01E2E-CALD-20260609-0001€4,475.00SUP-001INV-2026-3318c659ef7ca0…d356feef09…2026-06-09T09:00:21.000Z
02E2E-CALD-20260609-0002€12,880.50SUP-002INV-2026-3325d456264de2…48e0262e35…2026-06-09T09:01:06.000Z
03E2E-CALD-20260609-0003€23,900.00SUP-003INV-2026-3327946ea07aad…f8eeaf8f88…2026-06-09T09:01:51.000Z
04E2E-CALD-20260609-0004€9,240.10SUP-004INV-2026-3340dfc787e69b…c2608b9f87…2026-06-09T09:02:36.000Z
05E2E-CALD-20260609-0005€3,318.75SUP-005INV-2026-33414ed1ffecc2…11f1eb536f…2026-06-09T09:03:21.000Z
06E2E-CALD-20260609-0006€15,602.00SUP-006INV-2026-33552dd8b1222b…069faded18…2026-06-09T09:04:06.000Z
07E2E-CALD-20260609-0007€7,777.77SUP-007INV-2026-3360a0621cc931…ec4db0b3fb…2026-06-09T09:04:51.000Z
08E2E-CALD-20260609-0008€1,949.99SUP-008INV-2026-3361b3dc070e6b…f0fcc439be…2026-06-09T09:05:36.000Z
09E2E-CALD-20260609-0009€11,025.40SUP-009INV-2026-337237fe631b03…7a48463cb1…2026-06-09T09:06:21.000Z
10E2E-CALD-20260609-0010€6,890.00SUP-010INV-2026-33756af0591413…e845050d96…2026-06-09T09:07:06.000Z
11E2E-CALD-20260609-0011€2,475.25SUP-011INV-2026-3380c0458fef84…0bb554bcb8…2026-06-09T09:07:51.000Z
12E2E-CALD-20260609-0012€8,112.60SUP-012INV-2026-33847deab2e1d7…bafc606a6a…2026-06-09T09:08:36.000Z
13E2E-CALD-20260609-0013€5,230.95SUP-013INV-2026-3390f01e44097d…7fd5a242a1…2026-06-09T09:09:21.000Z
14E2E-CALD-20260609-0014€4,527.87SUP-014INV-2026-33912c53b3a315…daace35cf7…2026-06-09T09:10:06.000Z

4. Topology graph (declared = observed for this run)

Nodes: agent ap-pilot 2.4.1 · orchestrator flowdeck 1.9 · model claude-sonnet-4-6 · gateway toolproxy-3 · connector openbank-gw 2.2.0 · provider first-meridian-bank · erp ledgerworks · runtime aws/eu-west-1. Edges: agent→orchestrator→model (inference); agent→gateway→connector→provider (commit path); agent→erp (context, read-only). No undeclared touchpoints observed (third-party touchpoint set exhaustive for this run; basis: connector egress telemetry) [env:0074 | boundary_assessment.boundary_assessment_basis].

5. Chronology and silence semantics

Run window 09:00:00-09:10:52Z; heartbeats every 60s (10 beats, 0 silent windows); simulated in-trace anchors at 300s cadence (3); EOD reconciliation 18:10Z. Emission fail-closed ⇒ within the declared boundary, absence of an envelope implies absence of a commit-boundary action.

6. Known stubs and limitations (golden trace gt-v2.1)

Signatures are placeholders (envelope_signature_basis_status: stubbed). In-trace anchors are simulated (basis_status: simulated). The pacs.002 webhook (mTLS) and camt.053 statement-channel authenticity rungs are stubs (basis_status: stubbed); the HTTPS and bank-API rungs are simulated because the trace is synthetic. Each status is in a field a verifier reads (catalogue 1.27). A real on-chain anchor lane (EB-004, axes#3) remains open; the interbank pacs.008 leg is outside the capture boundary by design. Hashes, chain, ordering, coverage arithmetic, and artifact linkage are real and re-verifiable under RFC 8785 JCS with integer Amount fields (no JSON floats in hash scope).

This report is produced to AXES, an open, public working-draft standard for autonomous execution evidence, stewarded by Magentix AI. The standard is developed in the open and invites review.

See the standard's origin on GitHub

Other views of the same evidence

The Golden Trace example is published in several role-specific views. Each option below opens the same underlying record, framed for a stated profession. Select a view to read it, or share a link with a colleague whose role differs from yours.

Each view ends with the same review questions. The public requirements register is strengthened when multiple professions contribute.

Review this example

You have read the example report above. The questions below ask what would need to change before you could rely on a report like this in your role. Your answers are added to the public AXES requirements register.

Common questions (every reviewer)
Questions for your role

When a customer says "I did not make that payment", the answer today is often a multi-week reconstruction.

Attribution and contact
E1. May we credit you as a design partner on the standard? * Design partners are acknowledged in the standard's contributor record. This is standards review, not a testimonial.