# Gelios provider package v4

Version 4 is the first provider package whose monitoring states are derived
strictly from the Gelios Ontology `v1.1.0` value contracts.

The collection uses two official safe-read capabilities with the same native
rotating Gelios credential:

- `GET /api/v1/users/me/monitoring-config` supplies the account/user
  `signalActiveDuration` and `signalSomewhatInactiveDuration` values used by
  the official monitoring client;
- `GET /api/v1/units?incltrip=true` supplies the complete credential-visible
  unit set, last-message time, speed and position facts.

The immutable provider-neutral output is
`fleet.positions.current.v3@3.0.0`. Its only monitoring-state fields are:

- `signal_state`: `active` or `inactive`;
- `movement_state`: `moving` or `stopped`.

The realtime collection profile resolves the signal threshold in one explicit
order: a positive `signalSomewhatInactiveDuration`, then a positive
`signalActiveDuration`, then the Robot2B profile fallback of `120` seconds.
The fallback is profile metadata with observable provenance; it is never a
silent mapper default. If no live threshold and no positive profile fallback
exist, publication fails closed instead of manufacturing `inactive` facts.

There is no unknown, freshness, GPS-quality, position-quality, parked,
no-position or aggregate operational-status state. Missing geometry remains an
absent geometry fact and never becomes a status. Labels, counters, colours and
layout remain Foundry presentation metadata, but Foundry may only use the exact
values declared by Ontology.