Entities
Choose a Track, Geo, Asset, or Template value and preserve its identity, relationships, and quantity semantics.
Use the Entity primitive for observed objects, geographic features, managed resources, and reusable templates. An independent application can use these values without Mission enrollment.
Relationships do not grant access to either object.
Choose the value model
An Entity has a UUIDv7 EntityId, a name, lifecycle, type-specific data, and optional shared metadata. Equality follows identity, not matching field values.
| Variant | Use for | Type-specific content |
|---|---|---|
| Track | An observed or detected object | Classification, confidence, and source |
| Geo | A geographic feature | Geometry, feature type, and elevation |
| Asset | A managed resource | Category, tracking mode, serial details, or quantity unit |
| Template | A reusable blueprint | Shared entity fields, with no type-specific payload |
These four variants form a closed type system. Use category fields and bounded ontology metadata to describe application meaning, not invented Entity variants. Position and motion apply to Track and Asset values. Lifecycle distinguishes Active from Archived.
Preserve relationships and derived quantities
An entity stores typed Relation values, each combining a RelationKind with a PrimitiveRef. The model permits at most 32 relationships. Your application resolves targets and verifies authority independently. A relationship is not a copy of its target or an access grant.
For a quantity-tracked Asset, current quantity equals initial_quantity plus the sum of quantity_adjustments. Retain the initial value and deltas rather than treating a displayed total as the complete history. Individual-tracked Assets return no quantity. Quantity and relationships are members of Entity, not separate primitives.
Entity ontology can contain OntologyValue::BlobRef. That support does not imply that document fields accept the same value type.
Keep records and Mission services distinct
The record API's EntityRef contains an application-owned kind and id. A Record combines that reference, a SchemaRef, and an application payload. Neither type supplies the richer Entity model described here.
Constructing an Entity validates a value. It does not commit a record, replicate state, authenticate its metadata, or admit it to Mission. Your application owns the payload encoding, identity mapping, schema, and authorization policy when storing Entity values in records.
Mission adds organization ownership, team placement, and domain rules through its entity services. A Platform Track value alone is not a Mission Track publication.
Use the Entity reference for exact builders, fields, and limits. Continue with schemas and records, storage and replication, or the Platform language references.