Compliance-Status Legend¶
Shared icon scheme used by every matrix in compliance-standards/. Designed to render correctly in Markdown, DOCX, and PDF outputs, and to be machine-readable when the docs.airwai.com site generator parses these files.
| Icon | Status | Definition | When to use |
|---|---|---|---|
| ✅ | Meets | Capability deployed and delivering the output the standard requires | The standard asks for X; LAIRA produces X with measurement parameters at or above the standard's stated thresholds |
| ✅+ | Exceeds | Measurement resolution or capability surpasses the regulatory threshold, often by an order of magnitude | LAIRA's measurement resolution is meaningfully tighter than the standard's smallest severity threshold (e.g., ±3 mm elevation vs. >⅛ in ≈ 3.2 mm faulting threshold) |
| 🔄 | In Development | Active engineering effort with committed delivery on the near-term roadmap | The capability is being built; expected to flip to ✅ within the planning horizon |
| 🔶 | Partial | Delivers value with documented caveats — screening estimate, calibration dependency, host-platform dependency, or instrument-certification gap | LAIRA can do enough to be useful (screening, triage, advisory) but is not the final compliance instrument the standard envisions (e.g., calibrated-LiDAR retroreflectivity estimate vs. handheld retroreflectometer reading) |
| ℹ️ | Different Paradigm | LAIRA addresses the underlying need differently than the standard envisions | The standard specifies a cadence, sampling regime, or modality that LAIRA replaces with a different (typically continuous-scan) approach. Not a gap; a paradigm note. |
Anti-patterns¶
- Do not use ✅ when the work is partial. If formal validation testing has not been done, the row may still be ✅ when LAIRA's outputs match the standard's requirement in the field, but the matrix narrative should be explicit about what evidence supports the claim.
- Do not use ✅+ for items LAIRA simply covers. Reserve ✅+ for cases where there is a measurable, citable margin between LAIRA's spec and the standard's threshold.
- Do not use 🔄 as a placeholder for items not yet planned. If the capability isn't on the roadmap, omit the row or mark it ℹ️ with an explicit "out of scope" note.
- Do not mix the icon scheme with text labels in the same matrix. Pick the icon scheme; keep textual status labels out of body tables.
Audit posture¶
These icons are not marketing language. Every ✅ and ✅+ in a customer-facing matrix should survive a third-party audit (FAA inspector, AFCEC evaluator, state-DOT QA team, plaintiffs' counsel in a consent-decree forum). When in doubt, downgrade.