Audit-friendly by design.
Allied doctrine references, IP filings, and partner audit obligations — listed in one place so a procurement office can verify our claims before they spend an hour on an NDA.
Doctrine references.
- NATOSTANAG 2103
Reporting nuclear detonations, biological and chemical attacks
CBRN-CADS · BLIS-D · /technology/uamkt-extensions
- NATOATP-2.1.1
Allied Tactical Publication for Intelligence Procedures
IPB Framework · 3-Axis Architecture · `_uamkt_extensions`
- JPJP 2-01.3
Joint Intelligence Preparation of the Operational Environment
IPB Framework · Doctrine reference layer
- ICAODoc 9332
Manual on the ICAO Bird Strike Information System (IBIS)
AVIX-AI BirdThreat · Protection pillar · /insights articles
Where we file.
- KIPRIS (KR)
Bleed-air-based airborne CBRN platform · own-IP filing in progress
- USPTO (US)
Pending review — schema submission via Anduril Developer Zone serves as precedent reference
- CNIPA (CN)
Tracked but not pursued in Phase 1
Partner audit obligations.
- 01
Doctrine-tagged outputs
Every entity carries `_uamkt_extensions:doctrine_ref`. Allied operators audit the assumption tree before promoting the entity to operational decision surfaces.
- 02
Replayable evidence
Every published entity is reproducible from its source frames + model version. The 19/19 reference run (commit fbcb327) is the canonical replay target.
- 03
Open sample payloads
9 reference Lattice payloads are documented at /software/lattice-extensions/sample-payloads — partner BD teams can audit before signing anything.
- 04
NDA scope is narrow
Only Korean-theater specific telemetry mappings + customer-specific scenario packs require NDA. The schema, the doctrine, and the validation methodology are public.
Continue
Document ID · UAMKT-COMPANY-COMPLIANCE-V1 · Phase 2 · Updated annually