AXES Example (Ind) · Industrial and manufacturing · run MRUN-2026-06-11-A

Your branding here

Automation 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 failure-analysis, root-cause, warranty, and recall 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 - MRUN-2026-06-11-A

1. Verification procedure (vendor-neutral)

  1. Read envelopes.jsonl in sequence order. 2. For each envelope, remove integrity.envelope_hash and integrity.signature; serialise with sorted keys and compact separators; SHA-256; compare to stored hash. 3. Confirm previous_envelope_hash equals the prior envelope’s hash (genesis = 64x’0’). 4. Confirm sequence numbers are contiguous. 5. Compare chain heads at each attestation_recorded event with the anchor receipts in Appendix B of the Conformity Assessment Pack. 6. Re-hash each file in artifacts/ and compare with manifest.json. Steps 1-4 and 6 are fully reproducible from the bundle alone; step 5 is simulated in this golden trace.

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

Seqevent_kindPart#occurred_atenvelope_hash
0001execution_started-2026-06-11T07:00:00.000Z34a24129fcfb�
0002context_retrieved-2026-06-11T07:00:04.000Zc90ced1a9698�
0003plan_created-2026-06-11T07:00:09.000Z045294fe5ab9�
0004policy_check_performed12026-06-11T07:00:12.000Z7a0dc8abbc7d�
0005commit_attempted12026-06-11T07:00:18.000Z3a0af463b1ad�
0006tool_invoked12026-06-11T07:00:19.000Ze0c3d1945807�
0007commit_succeeded12026-06-11T07:00:21.000Z924aaeaf3347�
0008policy_check_performed22026-06-11T07:00:57.000Z224a40453d20�
0009heartbeat_event-2026-06-11T07:01:00.000Z8ed8da57f4e7�
0010commit_attempted22026-06-11T07:01:03.000Z5982f0c991df�
0011tool_invoked22026-06-11T07:01:04.000Zc6b3502a6a2f�
0012commit_succeeded22026-06-11T07:01:06.000Zc5674e144175�
0013policy_check_performed32026-06-11T07:01:42.000Z423b40be6ac3�
0014commit_attempted32026-06-11T07:01:48.000Z50ef7ef3543e�
0015tool_invoked32026-06-11T07:01:49.000Z2caeae8ea0a5�
0016commit_succeeded32026-06-11T07:01:51.000Z191bbbf919d8�
0017heartbeat_event-2026-06-11T07:02:00.000Zfd58e49de6c9�
0018policy_check_performed42026-06-11T07:02:27.000Zbcb85ab98add�
0019commit_attempted42026-06-11T07:02:33.000Zad47f631a32c�
0020tool_invoked42026-06-11T07:02:34.000Z3f2dfeba174f�
0021commit_succeeded42026-06-11T07:02:36.000Z94e82bf0dc7d�
0022heartbeat_event-2026-06-11T07:03:00.000Z58a18aa638b4�
0023policy_check_performed52026-06-11T07:03:12.000Zd33ea75dcc26�
0024commit_attempted52026-06-11T07:03:18.000Zf64b07400c87�

3. Part <-> artifact <-> confirmation linkage

#SerialCritical char (�25 H7 bore)Material lotQIF result hashMES release hashReleased at
01IMP4471-000125.0038 mmHT-88213474aaa15d4�6aae6e47f5�2026-06-11T07:00:21.000Z
02IMP4471-000225.0108 mmHT-88213459157aed0�f88da7ef27�2026-06-11T07:01:06.000Z
03IMP4471-000325.0201 mmHT-88213e3a1b6d646�1fbeed755c�2026-06-11T07:01:51.000Z
04IMP4471-000425.0078 mmHT-882132fb0e9d794�76f59f8d18�2026-06-11T07:02:36.000Z
05IMP4471-000525.0028 mmHT-882132e3f195f40�2f2173c0b9�2026-06-11T07:03:21.000Z
06IMP4471-000625.0131 mmHT-882132963ae2607�46c8bbcd1f�2026-06-11T07:04:06.000Z
07IMP4471-000725.0065 mmHT-88213ec0f8b3026�b629bfe6fa�2026-06-11T07:04:51.000Z
08IMP4471-000825.0016 mmHT-88213f7758184a0�b949347c49�2026-06-11T07:05:36.000Z
09IMP4471-000925.0093 mmHT-88213918aaecd9e�1a62e2d829�2026-06-11T07:06:21.000Z
10IMP4471-001025.0058 mmHT-882139de650fd53�6f6adaa97d�2026-06-11T07:07:06.000Z
11IMP4471-001125.0021 mmHT-882130e1b25391e�6410770987�2026-06-11T07:07:51.000Z
12IMP4471-001225.0068 mmHT-882136c51e7703d�1b2ddd3147�2026-06-11T07:08:36.000Z
13IMP4471-001325.0044 mmHT-8821336a4f54556�ad5c5311c3�2026-06-11T07:09:21.000Z
14IMP4471-001425.0038 mmHT-88213b807115d40�d0e91b5386�2026-06-11T07:10:06.000Z

Released tolerance for the critical characteristic: 25.000 +0.021 / 0 mm (H7). Part 3 at 25.0201 mm sits at 95.6% of the tolerance band - inside tolerance, and the tightest unit in the batch.

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

Nodes: agent mfg-pilot 3.1.0 � orchestrator shopfloor-orch 2.2 � model claude-sonnet-4-6 � gateway toolproxy-2 � connector opcua-gw 1.8.0 � cell cnc-cell-4 � mes ironmark/prod � runtime edge-mes-01. Edges: agent->orchestrator->model (inference); agent->gateway->connector->cell (release path); agent->mes (context and batch record, read/write). No undeclared touchpoints observed (third-party touchpoint set exhaustive for this run; basis: connector egress telemetry) [env:0074 | boundary_assessment.basis].

5. Chronology and silence semantics

Run window 07:00:00-07:10:52Z; heartbeats every 60s (10 beats, 0 silent windows); anchors at 300s cadence (3 receipts); end-of-shift reconciliation 16:10Z. Emission fail-closed => within the declared boundary, absence of an envelope implies absence of a release-boundary action.

6. Known stubs and limitations (golden trace)

Signatures are placeholders; anchor store is simulated; QIF result webhook authenticity (QMS mTLS) is asserted not demonstrated; the subcontracted heat-treatment and plating legs are outside the capture boundary by design. Hashes, chain, ordering, coverage arithmetic, and part-to-artifact linkage are real and re-verifiable.

This report is produced to AXES, an open, public working-draft standard for automation 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 part is returned or a batch is recalled, reconstructing what was made, to which revision, from which material lot, under whose authority, is often a multi-week investigation.

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.