Public claim audit
Aerospace traceability stack (AS9100 · NDT · part marking)
- Scope
- v2 cluster #2 + #13
- Lens version
- v0.4.7
- Claim id
- d58d4775-9310-4a33-80b1-94d27fa33721
Co-presence claim
Aerospace traceability stack (AS9100 · NDT · part marking)
Scope: v2 cluster #2 + #13
Scan date: 2026-08-06
Decomposition — atomic inputs
A1Holds AS9100
agent“iso9001 and as9100 LRQA approval Quality Management System ISO 9001 & AS9100D”
A2NDT methods: mt, pt, ut
agent“In-house Magnetic Particle Inspection (MPI) In-house Dye Penetrant Inspection (DPI) On-site Ultrasonic Testing (UT)”
A3Part marking offered
derivedDerived · R1 AS9100 → part marking — computed from a verified premise, not read off a page.
View premise source ↗Premise — AS9100
iso9001 and as9100 LRQA approval Quality Management System ISO 9001 & AS9100D
Version history
- v1Superseded2026-08-05
Aerospace traceability stack (AS9100 · NDT · part marking)
View this version’s audit page → - v2Supersededthis page2026-08-06
Aerospace traceability stack (AS9100 · NDT · part marking)
- v3Superseded2026-08-07
Aerospace traceability stack (AS9100 · NDT · part marking)
View this version’s audit page → - v4Superseded2026-08-09
Aerospace traceability stack (AS9100 · NDT · part marking)
View this version’s audit page → - v5Superseded2026-08-11
Aerospace traceability stack (AS9100 · NDT · part marking)
View this version’s audit page → - v6Superseded2026-08-13
Aerospace traceability stack (AS9100 · NDT · part marking)
View this version’s audit page → - v7Superseded2026-08-18
Aerospace traceability stack (AS9100 · NDT · part marking)
View this version’s audit page → - v8Superseded2026-08-19
Aerospace traceability stack (AS9100 · NDT · part marking)
View this version’s audit page → - v9Active2026-08-20
Aerospace traceability stack (AS9100 · NDT · part marking)
View this version’s audit page →
Dispute log
No disputes have been filed against this claim.
Disputes are public by design — this log is the publisher’s responsiveness record. Disputer identity is never shown: anonymous disputes are keyed by a one-way fingerprint hash that is not published; verified-owner disputes show only “verified owner”.