feat(platform): complete the Gelios external data loop
This commit is contained in:
@@ -0,0 +1,20 @@
|
||||
# Gelios provider package v5
|
||||
|
||||
Version 5 preserves the Ontology-exact monitoring logic from provider package
|
||||
v4 and publishes it through the immutable `fleet.positions.current.v4@4.0.0`
|
||||
contract.
|
||||
|
||||
The Data Product now declares a machine-enforced contract for every published
|
||||
field. In particular:
|
||||
|
||||
- `signal_state` is required and accepts only `active` or `inactive`;
|
||||
- `movement_state` is required and accepts only `moving` or `stopped`;
|
||||
- identity/presentation attributes are typed and required where the mapping
|
||||
must always produce them;
|
||||
- optional telemetry is type-checked and bounded where the physical domain has
|
||||
a stable lower or upper limit;
|
||||
- geometry remains optional, but when present it must be a valid GeoJSON Point.
|
||||
|
||||
The provider mapping is checked against the same contract before it can be
|
||||
packaged, and External Data Plane checks every publish at runtime. Existing
|
||||
v1-v3 products remain immutable and backward compatible.
|
||||
Reference in New Issue
Block a user