Every clause in a finding cites the exact surface it came from. Each pointer includes the source file, row or record, and SHA-256 computed in this browser. Hashes and file bytes are never transmitted.
A failure is an evidentiary boundary and the next ask. These requests are generated from the gaps in the loaded surfaces: the smallest additions that would let AXM produce a stronger finding.
Operational boundary: this public page is for dummy or de-identified data. For CUI or controlled operational data, download the single-file launcher and run it only inside an authorized environment.
This tool is the intake acceptance harness. It does not mint Genesis shards or sign anything. Surfaces that pass here are candidates for custody, not truth. Promotion into sealing and detached verification happens in the AXM kernel after intake.
A missing field does not kill the analysis. It lowers the evidence tier or becomes a declared gap. Human review routes attention; it does not convert weak evidence into strong evidence.
The browser hashes the supplied bytes, maps familiar field names including Air Force vocabulary such as NIIN, JCN, tail number, AWP/NMCS, and EDD, joins blocked work to the required part, and separates administrative on-hand from serviceable-and-unallocated stock.
Where the recorded state and the physically supportable state diverge, the divergence is the finding.
AXM is the governance layer between recorded state and consequential action: the part that checks whether a premise is physically supportable before planning speed magnifies the error. Accepted surfaces can move into custody, sealing, detached verification, query, and replay without changing the source system.
One static HTML file. No account, backend, database, API key, or automatic network request. The same file can be served from GitHub Pages, emailed as a launcher, copied to removable media, or hosted inside an approved enclave.