Object
An Object is anything with identity that the force needs to track in the battlespace. Examples include platforms, units, facilities, equipment, personnel, events, control measures, signals, and other operationally relevant things.
The Object schema is intentionally flexible. Producers populate the fields they know and omit fields that are unknown or irrelevant for that object. Different object types naturally use different subsets: a vessel may include maritime identity, position, motion, dimensions, and assessment, while a facility may include location, dimensions, and assessment without motion.
Core Shape
| Area | Purpose |
|---|---|
Identity |
|
Position and movement |
|
Tactical context |
|
Domain-specific data |
|
Trust and handling |
|
Required Discipline
Every publish should include provenance.updated_at.
An Object may include an id; if it does not, the service can generate one.
Populate strongly typed fields before using details.
Avoid default or placeholder values for data you do not actually have, because downstream consumers may treat those values as confirmed facts.
Lifecycle
Object lifecycle is carried by ObjectStatus.
| Status | Meaning |
|---|---|
|
The Object is part of the active operational picture. |
|
The Object is retained for historical or reference use but is not actively tracked. |
|
The Object has been removed from the active picture. |