There are two ways to add a primitive to an allied catalog. You can fork — maintain a private extension in your own namespace, hope your partners can read it. Or you can publish into a partner namespace that the catalog owner has agreed to carry.
We chose the second path. April 2026 made the choice precedential.
What the fork path costs
Forks are easier to ship. You do not have to negotiate; you just write. The cost shows up at the alliance boundary: every coalition partner who needs your data has to either (a) install your private extension, (b) translate at runtime, or (c) pretend the data is not there.
(a) is logistically expensive in a 50-theater coalition. (b) creates schema-translation bugs that surface during incidents — exactly when auditing is impossible. (c) is the path most operators actually take, which is the same as not having the data.
The partner-namespace pattern
_uamkt_extensions is not Anduril's catalog. It is a named extension
slot inside Anduril's catalog, agreed in advance, documented openly.
When AVIX-AI publishes _uamkt_extensions:bird to a partner Lattice
instance, the partner's catalog understands what the slot is.
The pattern works because:
- The slot has a single owner (us) responsible for schema definition
- The catalog owner has agreed to carry the slot
- Allied operators inheriting the catalog inherit the slot too
- Audits run against published documentation, not against private vendor materials
The April 2026 catalog release shipped platform_type: Animal and
aliases.name: Bird (Species) natively — primitives we had submitted
in March 2026. That release made the partner-namespace pattern a
precedent for the next vendor that wants to extend the catalog
responsibly.
What 19/19 HTTP 200 actually validates
Every allied operator is reasonably suspicious of catalog
extensions. The 19/19 HTTP 200 entity-API validation we ran during the
Incheon Technopark demonstration (commit fbcb327, 2026-04-20) is the
narrowest possible answer to that suspicion.
It does not validate that our schema is good. It validates that our schema deserialises against the catalog's parser, every time, across the test corpus. That is the entry condition; everything else is follow-on review.
A namespace is a contract, not a brand
_uamkt_extensions does not mean "UAMKT's stuff." It means
"primitives UAMKT has committed to maintain, documented openly, audited
against doctrine references, replayable from source frames + model
versions."
The contract is the asset. The brand is downstream of the contract.
—
Inquiries: ceo@uamkt.com
Primary reference: Anduril Industries (2026). Lattice Catalog Reference v3.