Machine-readable subset (human-rendered)

The blocks below are simplified renderings of what a QMS, MES, or customer acceptance system would consume programmatically before accepting an autonomous release disposition. They are not the raw JSON stream; they show the fields that matter for a pre-acceptance evidence check.

Latency expectation: a check that cannot return within your production or incoming-inspection window becomes friction, not assurance. The review questions ask what your latency budget is and what the check would need to return.

Lane boundary: AXES evidences execution; whether you block release on missing evidence is your quality policy, outside the standard.

Pre-release quality gate (part 3)

Pre-release quality gates evaluated before part 3 (SN IMP4471-0003) was dispositioned conforming.

event_kind: policy_check_performed
occurred_at: 2026-06-11T07:01:42.000Z
trace_id: 7c1de4a90b6f42e8b3a5c0d9e1f28a44
authority_context_id: MD-5120
delegation_receipt_id: delrec:MD-5120/2026-04-15
policy_version: 5.1
agent_id: agent:ironmark/mfg-pilot
emission_fail_posture: fail_closed
control_evaluation_phase: pre_commit

Part release committed (part 3)

Part release committed under delegated authority MD-5120 with quality-system confirmation.

event_kind: commit_succeeded
occurred_at: 2026-06-11T07:01:51.000Z
trace_id: 7c1de4a90b6f42e8b3a5c0d9e1f28a44
authority_context_id: MD-5120
delegation_receipt_id: delrec:MD-5120/2026-04-15
policy_version: 5.1
agent_id: agent:ironmark/mfg-pilot
emission_fail_posture: fail_closed

Batch reconciliation (run close)

End-of-run batch reconciliation against independently defined production order (14 of 14, 0 scrap).

event_kind: source_system_reconciliation
occurred_at: 2026-06-11T16:10:52.000Z
trace_id: 7c1de4a90b6f42e8b3a5c0d9e1f28a44
authority_context_id: MD-5120
delegation_receipt_id: delrec:MD-5120/2026-04-15
policy_version: 5.1
agent_id: agent:ironmark/mfg-pilot
emission_fail_posture: fail_closed
evidence_coverage_ratio: 1

This is what the machine consumes. The full stream contains 76 hash-chained envelopes for run MRUN-2026-06-11-A. See the standard origin on GitHub for the complete bundle structure.

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.

Open the board summary →
plant, operations, and manufacturing leadership
Open the quality and control view →
quality assurance, quality engineering, and inspection leads
Open the conformity assessment pack →
notified bodies, auditors, and airworthiness roles
Open the forensic pack →
failure analysis, root-cause, warranty, and recall teams
Open the conformance view →
product-liability and warranty underwriting

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) C1. Which view did you read? * C2. What in this report would not survive contact with your world? * The thing that would break, be queried, or be quietly distrusted the moment a colleague in your role saw it. C3. What single field or gap is missing that you would need before you could rely on this? * One thing - the one that matters most in your role. C4. Today, without a record like this, how do you answer the question your role actually faces?

Questions for your role

An incoming-acceptance evidence check is only usable if it returns inside your goods-inwards window without holding the dock.

What would a pre-acceptance evidence check need to return before you would accept an autonomously released part? * What is your acceptance-window budget before the check becomes friction? Where is the lane boundary - evidence only, or an accept/quarantine recommendation? AXES evidences conformance; the decision to accept is your policy, outside the standard.

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. Credit by name and role Role only Anonymous

E2. Name E3. Role and organisation type Organisation type is enough ("a UK clearing bank", "a mid-tier audit firm"); a specific employer name is not needed. E4. Email, if you are open to one clarifying question from the steward Used only to ask about your submission; not a mailing list. Not published in the public register. E5. Would you review a later draft?