`_uamkt_extensions`
The Lattice catalog namespace through which UAMKT ships Korea-axis IPB primitives. This page is the software-side companion to the doctrine-side `_uamkt_extensions` page in Technology — same entities, here as audit-able JSON.
5 mandatory field rules.
These five rules govern every payload we publish. They are the differences between 200 and 4xx on the Lattice Entity API. If a partner integration is failing, walk these in order.
- 01disposition
FRIENDLY · HOSTILE · UNKNOWN · NEUTRAL — last is the April 2026 official addition for Animal/non-military.
- 02template
TEMPLATE_ASSET/RADAR · TEMPLATE_GEO/CONTROL_AREA · TEMPLATE_TRACK · TEMPLATE_SENSOR_POINT_OF_INTEREST.
- 03environment
ENVIRONMENT_AIR | LAND | SURFACE | SUBSURFACE | SPACE — recommended within milView.
- 04altitude
altitudeAglMeters (low-altitude / ground reference) OR altitudeHaeMeters (HAE / Animal / high-altitude) — pick one.
- 05expiry
Top-level expiryTime as ISO string. NOT nested as expiry.expiryTime — that shape returns 4xx.
Soft-delete.
The Lattice Entity API does not accept HTTP DELETE — it returns 405. We soft-delete by PUTting isLive=false with an epoch expiryTime. This pattern is shared with our partners explicitly so a catalog audit reads cleanly.
// DELETE returns 405 on the Lattice Entity API.
// Soft-delete pattern — PUT with isLive=false + epoch expiryTime:
PUT /api/v1/entities
{
"entityId": "...",
"expiryTime": "1970-01-01T00:00:00Z",
"isLive": false,
"ontology": { "template": "TEMPLATE_TRACK" }
}Try the publish flow.
Pick a reference payload, inspect the JSON, simulate the `PUT /api/v1/entities` call, and watch the response land in the console — same shape as the live sandbox, no auth, no network egress.
Lattice Mockup Demo
- Endpoint
- PUT /api/v1/entities
- Pillar
- Protection
- Description
- AVIX-AI Animal-class entity for a bird detected on approach. NEUTRAL disposition, altitudeHaeMeters for high-altitude migrants.
Simulation only · no live network call · the live sandbox achieved 19/19 HTTP 200 on commit fbcb327 (2026-04-20).
{
"entityId": "track-bird-RKSI-39214",
"expiryTime": "2026-04-26T03:31:00Z",
"isLive": true,
"ontology": {
"platform_type": "Animal",
"template": "TEMPLATE_TRACK"
},
"aliases": { "name": "Bird (Larus crassirostris)" },
"milView": {
"disposition": "NEUTRAL",
"environment": "ENVIRONMENT_AIR"
},
"location": {
"position": {
"latitudeDegrees": 37.4602,
"longitudeDegrees": 126.4407,
"altitudeHaeMeters": 230
}
},
"_uamkt_extensions": {
"doctrine_ref": "ICAO Doc 9332",
"habitat_id": "habitat-RKSI-coastal-mudflat-01"
}
}9 reference payloads.
9 entries- ProtectionPUT /api/v1/entities
Animal · Bird · TEMPLATE_TRACK
AVIX-AI Animal-class entity for a bird detected on approach. NEUTRAL disposition, altitudeHaeMeters for high-altitude migrants.
Read JSON → - DefensePUT /api/v1/entities
CBRN · Chemical hazard · TEMPLATE_GEO/CONTROL_AREA
CBRN-CADS chemical hazard control area, STANAG 2103 categorisation, with first-warning timing.
Read JSON → - IPB AnalysisPUT /api/v1/entities
Pre-indicator · Migration window
Pre-indicator payload — 48 h forward window for a migratory corridor opening. Distinguishes signal-detection time from arrival window.
Read JSON → - ProtectionPUT /api/v1/entities
Animal · soft-delete (PUT isLive=false)
Soft-delete pattern — DELETE returns 405 on Lattice; we PUT isLive=false with epoch expiryTime instead.
Read JSON → - DefensePUT /api/v1/entities
CBRN · Second warning update
Same chemical control area, second-phase warning — refined hazard polygon with downwind plume model applied.
Read JSON → - IPB AnalysisPUT /api/v1/entities
Habitat · profile attachment
Habitat Profile Engine output — LULC + species + microclimate notes per coverage cone. Referenced by `_uamkt_extensions.habitat_id`.
Read JSON → - ProtectionPUT /api/v1/entities
Sensor · solid-state radar
TEMPLATE_ASSET/RADAR registration — declares the sensor surface that produces Animal-class tracks downstream.
Read JSON → - IPB AnalysisPUT /api/v1/entities
Cross-pillar · correlation marker
Marks a known correlation between an AVIX-AI track and a CBRN control area — useful for the duty officer cross-pillar view.
Read JSON → - IPB AnalysisPUT /api/v1/entities
Doctrine-tagged · track payload
Generic track payload illustrating the doctrine_ref tag pattern — every entity we publish carries one of these.
Read JSON →