One execution. One evidence record. Many professional truths.

Wherever a consequential action runs without a human at every step - a payment, a manufacturing step, a standard operating procedure, a supply-chain hand-off, a customer or HR decision, an infrastructure change - the same question follows: what was done, under whose authority, and can it be proven later. And each profession needs a different cut of that same truth. AXES is the open standard for binding that evidence at the moment of execution, then rendering it as a report a board, an auditor, an operations lead, a disputes team, or a regulator could actually use. The situations it covers are not limited to financial services; the breadth of those use cases is wider than any single industry.

Two worked examples are published on these pages, and they are deliberately built on the identical evidence skeleton. The financial example is an autonomous accounts-payable run committing 14 payment instructions under delegated authority. The industrial example is an autonomous production run releasing 14 machined parts under delegated authority. Same authority model, same pre-commit controls, same commit boundary, same reconciliation, same hash chain. Only the domain and the artefact standards change - ISO 20022 in one, QIF, ISA-95, MTConnect, and EN 10204 in the other. That the same record structure carries both is the point.

How it works

1. Capture once. Execution evidence is bound at the moment of action - authority, artefacts, and outcome - across whatever process the automation ran.
2. Render for the role. Board, audit, forensic, regulator, conformance, and machine-readable views are cuts of the same record, not separate stories.
3. Keep the report portable. Branding slots are intentional: the report is designed to become your organisation's artefact, not a vendor PDF.

That is why a treasury lead, a fraud analyst, a plant operations manager, and a disputes investigator can open different pages and still be looking at the same event.

Why we need your view

Standards fail when they are written only for the people who build them. Your answers enter the public AXES requirements register: what would not survive contact with your desk, and what single gap must close before you could rely on a report like this. That is how the next draft earns the right to be taken seriously - across industries, not inside one.

Choose the view that matches your role. Read it as if it crossed your desk. At the foot of the page, say what would need to change. If another role would read this differently, their view is one tap away after you open yours.

Choose your professional view

Every profession that answers makes the next version harder to dismiss - and more usable on a real desk. Financial or industrial, the review questions are the same, and every answer enters the same public register.