AS9100 Audit Evidence That Assembles Itself

AS9100 audit evidence does not need to be assembled by hand: when every document review, cross reference and disposition is sealed into a tamper evident record at the moment it happens, the evidence pack for a certification audit becomes a query against that record rather than weeks of manual collation. That is the difference between asserting compliance and proving it on demand.

The AS9100 family, published by SAE International and administered under the International Aerospace Quality Group (IAQG) scheme, is the backbone of aerospace quality certification. AS9100 revision D, published in 2016 and aligned with ISO 9001:2015, covers design and manufacturing organisations. AS9110 covers maintenance and repair organisations, and AS9120 covers distributors and stockists. Certification is not a one off event. Accredited certification bodies audit against the standard, certified organisations are listed on the IAQG OASIS database, and regular surveillance audits keep the certificate live. Every one of those audits runs on evidence, and today most of that evidence is still pulled together by hand.

Why does AS9100 audit preparation consume so much quality team time?

Because the evidence lives in many places and the audit needs it in one. Ahead of a certification or surveillance audit, quality teams pull calibration records, training matrices, nonconformance and findings logs, supplier certifications and corrective action files from the systems and cabinets where they accumulated, then reconcile them into a pack an auditor can walk through. None of that work makes an aircraft part better. It is retrieval and reconciliation done under deadline. The standard does not demand that the pack be built by hand. It demands that the evidence exists, is controlled and can be produced. The hand assembly is a limitation of the tooling, not a requirement of AS9100.

What does it mean for audit evidence to assemble itself?

It means evidence is captured as a side effect of doing the work, never reconstructed afterwards. On our platform, every review and every consequential action is sealed to the Open Audit Record before it runs: what was reviewed, what it was checked against, what the outcome was, and who cleared it. The record is cryptographically signed, built to a post quantum standard, tamper evident, and verifiable offline. When the audit arrives, the pack is not a collation project. It is a query: every calibration certificate reviewed this period, every nonconformance disposition and its signatory, every supplier certificate cross referenced at receiving.

• Calibration records, matched to the instruments and the dates they cover
• Training and competence matrices, tied to the procedures each person is authorised to perform
• Nonconformance and findings logs, each carrying its disposition and the signature behind it
• Supplier certifications and material certificates, cross referenced at receiving against the records behind them
• Corrective actions from root cause to closure, every step time stamped and sealed

How does a sovereign review system actually handle the documents?

It reads them the way a careful engineer would, and it does not get tired. Our document review capability reads incoming packages, cross references certificates against the records behind them, drafts the routine paperwork, and holds anything anomalous for a person to judge. A material certificate that does not match its purchase order, a calibration record with a gap in its history, a training entry that does not cover the procedure performed: these are held, not hidden. The machine does the patient first pass across everything. People keep judgement, disposition and sign-off, and consequential actions wait for a person's clearance. Every step, including the holding of an anomaly and the human decision that resolved it, is sealed to the record as it happens.

“An audit should be a conversation about your quality system, not a scramble to reconstruct what it did. When every review is sealed the moment it happens, the evidence is simply there, and it is provable.”

Why does this need to run on our own hardware?

Because aerospace quality records are not neutral data. Supplier certificates, nonconformance records and engineering paperwork routinely sit close to export controlled technical data, commercially sensitive supplier terms and customer designs. Routing that material through a third party cloud service raises questions an export control officer or a customer contract may not let you answer. Mickai is a Sovereign Intelligence Operating System that runs entirely on hardware you own, on premise and air gapped where you require it. Nothing leaves the building: not the documents, not the prompts, not the audit trail. An auditor can verify the record offline, on site, without your organisation depending on any external service to prove its own compliance.

Does this replace our quality management system?

No, and we would be wary of anyone who claimed it should. AS9100 certifies your organisation's quality management system: its processes, its people and its discipline. What we address is the layer underneath, the reviewing, cross referencing and evidencing that consumes quality engineers' hours without using their judgement. Your procedures still govern. Your people still sign. What changes is that the proof accumulates continuously instead of quarterly, and that it is tamper evident rather than merely filed. We say this plainly because overclaiming is the fastest way to lose a quality director's trust.

Aerospace quality is moving in one direction: more traceability, more scrutiny of supplier evidence, and less tolerance for paperwork that cannot be proven. The organisations that will find the next decade of audits straightforward are the ones whose evidence accumulates, sealed and verifiable, as a by-product of daily work. We are building for that world, on your hardware, under your control, with your people in charge of every disposition. The audit pack that assembles itself is not a convenience feature. It is what provable compliance looks like.

Frequently asked questions

What evidence does an AS9100 audit typically require?

Certification and surveillance audits look for objective evidence that the quality management system operates as documented. That typically includes calibration records, training and competence records, nonconformance and corrective action files, supplier evaluation and receiving records, and internal audit findings, all controlled and retrievable on request.

Can evidence from an AI assisted review be trusted by an auditor?

Only if it is attributable and tamper evident. Our approach seals every review to the Open Audit Record before the action runs, in a cryptographically signed form that can be verified offline. People, not the machine, make dispositions, and the record shows exactly who cleared what and when.

Does automated evidence collection change our AS9100 certification?

No. Certification is still issued by an accredited certification body against your quality management system under the IAQG scheme. Sealed evidence changes how easily you can demonstrate conformity, not who certifies it or what the standard requires.

Can this run in an air gapped facility?

Yes. Mickai runs fully offline on hardware the customer owns, and the Open Audit Record is verifiable offline. That suits facilities handling export controlled technical data or material that cannot leave the estate under any circumstances.

Who decides what happens when the system finds an anomaly?

A person does, every time. The system holds the anomaly, presents what it found and what it was checked against, and waits. The disposition, the signature and the clearance belong to your engineer, and all of it is sealed to the record.

What is MICKAI?

MICKAI is a Sovereign Intelligence Operating System (a SIOS) that runs entirely on the customer's own hardware, on premise and air gapped. Every consequential action is sealed to the Open Audit Record, a cryptographically signed, tamper evident record that is verifiable offline and sealed before the action runs. The system comprises 87 studios, with ten production ready at launch and 77 in development. Our intellectual property position includes 104 filed UK patent applications across 2,340 claims, filed rather than granted, held by Mickai LTD.