<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Micky Irons</title>
    <description>The latest articles on DEV Community by Micky Irons (@mickai).</description>
    <link>https://dev.to/mickai</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3909620%2F836c63c8-56bd-4f81-b44c-5d3968713336.jpeg</url>
      <title>DEV Community: Micky Irons</title>
      <link>https://dev.to/mickai</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mickai"/>
    <language>en</language>
    <item>
      <title>Sealed before it runs beats logged after it happened</title>
      <dc:creator>Micky Irons</dc:creator>
      <pubDate>Fri, 31 Jul 2026 18:32:29 +0000</pubDate>
      <link>https://dev.to/mickai/sealed-before-it-runs-beats-logged-after-it-happened-2849</link>
      <guid>https://dev.to/mickai/sealed-before-it-runs-beats-logged-after-it-happened-2849</guid>
      <description>&lt;p&gt;&lt;em&gt;An audit record sealed before an action runs cannot be shaped by the outcome, which makes it evidence rather than recollection.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Conventional systems write audit logs after actions execute, and forensics teams routinely find those logs incomplete or editable. Our Open Audit Record seals every consequential action before it runs, cryptographically signed, post quantum and verifiable offline.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://mickai.co.uk/articles/sealed-before-it-runs-vs-logging-after" rel="noopener noreferrer"&gt;mickai.co.uk&lt;/a&gt;. This is a cross-post; the canonical version, with the full body, footnotes and references, lives on the mickai.co.uk article page.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffboqna5fvi9h78lxeq6t.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffboqna5fvi9h78lxeq6t.png" alt="cover" width="800" height="420"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>sovereignai</category>
      <category>openauditrecord</category>
      <category>tamperevidentaudit</category>
      <category>aigovernance</category>
    </item>
    <item>
      <title>Document fraud is a supply chain attack and deserves the same defence</title>
      <dc:creator>Micky Irons</dc:creator>
      <pubDate>Fri, 31 Jul 2026 18:32:14 +0000</pubDate>
      <link>https://dev.to/mickai/document-fraud-is-a-supply-chain-attack-and-deserves-the-same-defence-4h2f</link>
      <guid>https://dev.to/mickai/document-fraud-is-a-supply-chain-attack-and-deserves-the-same-defence-4h2f</guid>
      <description>&lt;p&gt;&lt;em&gt;Forged certificates enter supply chains through the trusted receiving desk, so the defence is depth of review at the point of entry, on your own hardware, with every decision sealed.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Document fraud behaves like a supply chain attack: it enters through the trusted receiving desk and propagates downstream. The defence is depth of review at the point of entry, every certificate cross checked on your own hardware, anomalies held for a person, every disposition sealed.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://mickai.co.uk/articles/counterfeit-certificates-supply-chains-document-fraud" rel="noopener noreferrer"&gt;mickai.co.uk&lt;/a&gt;. This is a cross-post; the canonical version, with the full body, footnotes and references, lives on the mickai.co.uk article page.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F88gz0t2n6ikb8ue0360o.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F88gz0t2n6ikb8ue0360o.png" alt="cover" width="800" height="420"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>supplychaindocumentfraud</category>
      <category>sovereigndocumentreview</category>
      <category>counterfeitparts</category>
      <category>certificateverification</category>
    </item>
    <item>
      <title>UK Export Controls and Cloud AI: The Intangible Transfer Wall</title>
      <dc:creator>Micky Irons</dc:creator>
      <pubDate>Fri, 31 Jul 2026 18:31:59 +0000</pubDate>
      <link>https://dev.to/mickai/uk-export-controls-and-cloud-ai-the-intangible-transfer-wall-1b7h</link>
      <guid>https://dev.to/mickai/uk-export-controls-and-cloud-ai-the-intangible-transfer-wall-1b7h</guid>
      <description>&lt;p&gt;&lt;em&gt;Uploading controlled technical data to a cloud AI raises a licensable intangible transfer question under UK export control law, and sovereign on premise review removes it.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;UK strategic export controls restrict intangible transfers of controlled technology by electronic means, which puts cloud AI squarely in licensing territory. We explain why on premise, air gapped review is the defensible route for British defence and dual use manufacturers.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://mickai.co.uk/articles/uk-strategic-export-controls-beyond-itar" rel="noopener noreferrer"&gt;mickai.co.uk&lt;/a&gt;. This is a cross-post; the canonical version, with the full body, footnotes and references, lives on the mickai.co.uk article page.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7t9xk7piz1iqr3n94qqa.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7t9xk7piz1iqr3n94qqa.png" alt="cover" width="800" height="420"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>sovereignai</category>
      <category>ukexportcontrols</category>
      <category>intangibletechnologytrans</category>
      <category>defencemanufacturing</category>
    </item>
    <item>
      <title>Audit working papers, client confidentiality and AI</title>
      <dc:creator>Micky Irons</dc:creator>
      <pubDate>Fri, 31 Jul 2026 18:31:43 +0000</pubDate>
      <link>https://dev.to/mickai/audit-working-papers-client-confidentiality-and-ai-2am3</link>
      <guid>https://dev.to/mickai/audit-working-papers-client-confidentiality-and-ai-2am3</guid>
      <description>&lt;p&gt;&lt;em&gt;Audit firms can use AI on client working papers without breaching confidentiality, but only when the review runs on hardware the firm owns, with nothing leaving the building and a sealed record of every action.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Audit firms can use AI on working papers without breaching client confidentiality, but only on hardware the firm owns and controls. We set out why the cloud delivery model fails the profession's duties, and what sovereign, sealed working paper review looks like instead.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://mickai.co.uk/articles/audit-working-papers-confidentiality-ai" rel="noopener noreferrer"&gt;mickai.co.uk&lt;/a&gt;. This is a cross-post; the canonical version, with the full body, footnotes and references, lives on the mickai.co.uk article page.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1476rwey6ev2vxinc2cz.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1476rwey6ev2vxinc2cz.png" alt="cover" width="800" height="420"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>sovereignai</category>
      <category>auditworkingpapers</category>
      <category>clientconfidentiality</category>
      <category>documentreview</category>
    </item>
    <item>
      <title>OFFICIAL SENSITIVE and AI: the question UK departments must answer</title>
      <dc:creator>Micky Irons</dc:creator>
      <pubDate>Fri, 31 Jul 2026 18:31:29 +0000</pubDate>
      <link>https://dev.to/mickai/official-sensitive-and-ai-the-question-uk-departments-must-answer-33ea</link>
      <guid>https://dev.to/mickai/official-sensitive-and-ai-the-question-uk-departments-must-answer-33ea</guid>
      <description>&lt;p&gt;&lt;em&gt;The defensible way for a UK department to apply AI to OFFICIAL SENSITIVE material is to run it inside its own estate, air gapped, with every action sealed and a person in charge.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;OFFICIAL SENSITIVE material cannot defensibly go through uncontrolled third party AI services, so the AI has to come to the data. We explain how sovereign, on premise review with a sealed audit record lets departments use modern AI on casework, procurement and policy documents.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://mickai.co.uk/articles/official-sensitive-documents-uk-public-sector-ai" rel="noopener noreferrer"&gt;mickai.co.uk&lt;/a&gt;. This is a cross-post; the canonical version, with the full body, footnotes and references, lives on the mickai.co.uk article page.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F2avssap6c9mrj6pnssko.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F2avssap6c9mrj6pnssko.png" alt="cover" width="800" height="420"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>sovereignai</category>
      <category>officialsensitive</category>
      <category>ukpublicsector</category>
      <category>governmentsecurityclassif</category>
    </item>
    <item>
      <title>Supplier certificates: manufacturing's quiet counterfeit problem</title>
      <dc:creator>Micky Irons</dc:creator>
      <pubDate>Fri, 31 Jul 2026 18:31:10 +0000</pubDate>
      <link>https://dev.to/mickai/supplier-certificates-manufacturings-quiet-counterfeit-problem-2if0</link>
      <guid>https://dev.to/mickai/supplier-certificates-manufacturings-quiet-counterfeit-problem-2if0</guid>
      <description>&lt;p&gt;&lt;em&gt;Counterfeit parts enter factories through paperwork, and deep cross referencing of every supplier certificate at receiving, on your own hardware, is the defence that works.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Counterfeit and non conforming parts enter manufacturing through the receiving desk. Deep, sovereign review of every supplier certificate against the records behind it catches the one that does not add up.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://mickai.co.uk/articles/supplier-certificates-manufacturing-counterfeit-risk" rel="noopener noreferrer"&gt;mickai.co.uk&lt;/a&gt;. This is a cross-post; the canonical version, with the full body, footnotes and references, lives on the mickai.co.uk article page.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fb5hdj5gssi5o6yv201yk.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fb5hdj5gssi5o6yv201yk.png" alt="cover" width="800" height="420"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>suppliercertificates</category>
      <category>counterfeitparts</category>
      <category>iatf16949</category>
      <category>as9120</category>
    </item>
    <item>
      <title>NIS2 and the documentation burden on critical infrastructure</title>
      <dc:creator>Micky Irons</dc:creator>
      <pubDate>Fri, 31 Jul 2026 18:30:55 +0000</pubDate>
      <link>https://dev.to/mickai/nis2-and-the-documentation-burden-on-critical-infrastructure-490</link>
      <guid>https://dev.to/mickai/nis2-and-the-documentation-burden-on-critical-infrastructure-490</guid>
      <description>&lt;p&gt;&lt;em&gt;NIS2 obliges essential and important entities to document cyber risk management, supply chain security and incident handling, and to prove it on demand, with management personally accountable.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;NIS2 turns cyber security into an evidence discipline for critical infrastructure, with documented risk management, supply chain oversight and incident records that regulators can inspect. We explain the duties and the sovereign, on premise way to meet them.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://mickai.co.uk/articles/nis2-critical-infrastructure-documentation" rel="noopener noreferrer"&gt;mickai.co.uk&lt;/a&gt;. This is a cross-post; the canonical version, with the full body, footnotes and references, lives on the mickai.co.uk article page.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fedf33d8c2i7c5w4uwh8a.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fedf33d8c2i7c5w4uwh8a.png" alt="cover" width="800" height="420"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>nis2</category>
      <category>criticalinfrastructure</category>
      <category>sovereignai</category>
      <category>cyberriskmanagement</category>
    </item>
    <item>
      <title>Pharma batch records: Part 11 wants exactly this audit trail</title>
      <dc:creator>Micky Irons</dc:creator>
      <pubDate>Fri, 31 Jul 2026 18:30:39 +0000</pubDate>
      <link>https://dev.to/mickai/pharma-batch-records-part-11-wants-exactly-this-audit-trail-3gmd</link>
      <guid>https://dev.to/mickai/pharma-batch-records-part-11-wants-exactly-this-audit-trail-3gmd</guid>
      <description>&lt;p&gt;&lt;em&gt;Part 11 requires secure, computer generated, time stamped audit trails independent of the operator, and a sovereign on premise review system with a sealed, tamper evident record is the cleanest way to meet it while using AI on batch records.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;FDA's 21 CFR Part 11 demands audit trails that are computer generated, time stamped and independent of the operator. We explain why batch record review on your own hardware, sealed before every action runs, is the architecture the regulation describes.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://mickai.co.uk/articles/pharma-batch-records-21-cfr-part-11" rel="noopener noreferrer"&gt;mickai.co.uk&lt;/a&gt;. This is a cross-post; the canonical version, with the full body, footnotes and references, lives on the mickai.co.uk article page.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzonmtncya44115omfbap.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzonmtncya44115omfbap.png" alt="cover" width="800" height="420"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>21cfrpart11</category>
      <category>pharmabatchrecords</category>
      <category>audittrail</category>
      <category>dataintegrity</category>
    </item>
    <item>
      <title>DORA and the document trail your firm must be able to prove</title>
      <dc:creator>Micky Irons</dc:creator>
      <pubDate>Fri, 31 Jul 2026 18:30:21 +0000</pubDate>
      <link>https://dev.to/mickai/dora-and-the-document-trail-your-firm-must-be-able-to-prove-2hn6</link>
      <guid>https://dev.to/mickai/dora-and-the-document-trail-your-firm-must-be-able-to-prove-2hn6</guid>
      <description>&lt;p&gt;&lt;em&gt;DORA turns operational resilience into a documentary obligation, and the firms that can produce a provable trail of registers, contracts and incident records on demand are the ones that will face inspection calmly.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;DORA requires financial firms to evidence their operational resilience, not merely assert it, through registers, contracts, incident logs and test results a regulator can inspect. We explain why that document trail is now the compliance programme, and why building it on your own hardware is the defensible route.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://mickai.co.uk/articles/dora-document-trail-financial-services" rel="noopener noreferrer"&gt;mickai.co.uk&lt;/a&gt;. This is a cross-post; the canonical version, with the full body, footnotes and references, lives on the mickai.co.uk article page.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Flz84buwy1xvx1ufra56c.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Flz84buwy1xvx1ufra56c.png" alt="cover" width="800" height="420"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>doracompliance</category>
      <category>financialservices</category>
      <category>sovereignai</category>
      <category>operationalresilience</category>
    </item>
    <item>
      <title>Due diligence data rooms and AI: privilege is the constraint</title>
      <dc:creator>Micky Irons</dc:creator>
      <pubDate>Fri, 31 Jul 2026 18:29:51 +0000</pubDate>
      <link>https://dev.to/mickai/due-diligence-data-rooms-and-ai-privilege-is-the-constraint-1jip</link>
      <guid>https://dev.to/mickai/due-diligence-data-rooms-and-ai-privilege-is-the-constraint-1jip</guid>
      <description>&lt;p&gt;&lt;em&gt;Law firms can use modern AI on a due diligence data room without endangering privilege only when the review runs on their own hardware, air gapped, with every action sealed to a verifiable record.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Privilege rests on confidentiality, and confidentiality ends where third party infrastructure begins. We explain why sovereign, on premise review is the defensible way for deal teams to put AI to work on a data room.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://mickai.co.uk/articles/legal-due-diligence-data-rooms-on-premise-ai" rel="noopener noreferrer"&gt;mickai.co.uk&lt;/a&gt;. This is a cross-post; the canonical version, with the full body, footnotes and references, lives on the mickai.co.uk article page.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhxcocccwxn3xfkhu6dnw.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhxcocccwxn3xfkhu6dnw.png" alt="cover" width="800" height="420"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>legalduediligence</category>
      <category>sovereignlegalai</category>
      <category>legalprofessionalprivileg</category>
      <category>onpremiseai</category>
    </item>
    <item>
      <title>Half of MRO engineering time goes on paperwork. It does not have to.</title>
      <dc:creator>Micky Irons</dc:creator>
      <pubDate>Fri, 31 Jul 2026 18:29:36 +0000</pubDate>
      <link>https://dev.to/mickai/half-of-mro-engineering-time-goes-on-paperwork-it-does-not-have-to-312n</link>
      <guid>https://dev.to/mickai/half-of-mro-engineering-time-goes-on-paperwork-it-does-not-have-to-312n</guid>
      <description>&lt;p&gt;&lt;em&gt;Industry commentary puts half of MRO engineering time on paperwork, and the fix is a sovereign first pass on your own hardware with engineers keeping sign off.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Industry commentary puts close to half of MRO engineers' time on paperwork rather than aircraft. We explain how a sovereign first pass on your own hardware returns those hours while engineers keep disposition and sign off.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://mickai.co.uk/articles/mro-engineering-time-paperwork-problem" rel="noopener noreferrer"&gt;mickai.co.uk&lt;/a&gt;. This is a cross-post; the canonical version, with the full body, footnotes and references, lives on the mickai.co.uk article page.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5v4azsab5bbflc0g4szg.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5v4azsab5bbflc0g4szg.png" alt="cover" width="800" height="420"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>mropaperwork</category>
      <category>aviationmaintenance</category>
      <category>taskcards</category>
      <category>sovereignai</category>
    </item>
    <item>
      <title>AS9100 Audit Evidence That Assembles Itself</title>
      <dc:creator>Micky Irons</dc:creator>
      <pubDate>Fri, 31 Jul 2026 18:29:20 +0000</pubDate>
      <link>https://dev.to/mickai/as9100-audit-evidence-that-assembles-itself-27i</link>
      <guid>https://dev.to/mickai/as9100-audit-evidence-that-assembles-itself-27i</guid>
      <description>&lt;p&gt;&lt;em&gt;When every review and disposition is sealed as it happens, the AS9100 audit pack becomes a query against a tamper evident record, not a quarter of manual collation.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;AS9100 evidence packs do not have to be assembled by hand. When every review and disposition is sealed the moment it happens, the audit pack becomes a query against a tamper evident record that an auditor can verify offline.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://mickai.co.uk/articles/as9100-audit-evidence-that-assembles-itself" rel="noopener noreferrer"&gt;mickai.co.uk&lt;/a&gt;. This is a cross-post; the canonical version, with the full body, footnotes and references, lives on the mickai.co.uk article page.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbgn1pwtvpck5lduip3ji.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbgn1pwtvpck5lduip3ji.png" alt="cover" width="800" height="420"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>as9100</category>
      <category>aerospacequality</category>
      <category>auditevidence</category>
      <category>sovereignai</category>
    </item>
  </channel>
</rss>
