Open questions.

Five research tracks where we are looking for the next answer. Open to collaboration with allied IPB analysts, partner operators, and academic groups working on adjacent doctrine.

1. 01

   IPB whitespace catalogue

   “What allied-doctrine primitives are missing from the Anduril Lattice catalog?”

   Iterative survey of operator pain points where the catalog is silent. Phase 1 identified three (animal-class, pre-indicator, doctrine-tagged). Phase 2 is mapping additional gaps in maritime + space.

   Collaborators · Open to allied IPB analysts

   Active
2. 02

   Doctrine-encoding patterns

   “What is the canonical shape for a doctrine-tagged Lattice payload?”

   `_uamkt_extensions:doctrine_ref` is the concrete pattern. Generalising it into a partner-namespace standard so any vendor can adopt the discipline.

   Collaborators · Anduril Developer Zone (informal)

   Pre-publication
3. 03

   Partner namespace adoption

   “How do allied operators audit a partner namespace before subscribing?”

   Sample payloads + replayable evidence + open NDA scope are our three answers. Looking for a second perspective from operators who have audited multiple namespaces.

   Collaborators · Open call · NATO + JP-class operators

   Open call
4. 04

   OODA compression validation

   “How does a 33× compressed OODA loop hold up under independent walkthrough?”

   CBRN-CADS validation pack ready for an independent allied walkthrough. The compression number is fragile until reviewed.

   Collaborators · Allied CBRN cell · NDA available

   Pre-publication
5. 05

   Habitat profile encoding

   “What habitat features are decisive predictors of bird-strike risk?”

   AVIX-AI Habitat Profile Engine produces the contextual layer. Looking at LULC, microclimate, and migration-window correlation across coastal vs inland operators.

   Collaborators · Wildlife biology · partner airports

   Active