# Gelios capability catalog

`capability-catalog-v1.mjs` is the immutable baseline classified inventory for the
current `UnitModelOutput` surface and the adjacent object APIs that NODE.DC may
consume. Its authority is the official Gelios OpenAPI, checked on 2026-07-22.

`capability-catalog-v2.mjs` preserves that inventory and records the first cold
profile implementation: stable unit type, hardware classification and trip
settings in `fleet.units.profile.current.v1`. Sensor definitions, fuel,
storage and maintenance remain explicitly planned rather than being implied by
the new product.

The catalog is deliberately separate from an active L2 package. `implemented`
means a capability already has a governed collection and Data Product path;
`catalogued` means NODE.DC understands the surface but has not activated it;
`disabled` is mandatory for control and destructive operations.

The catalog accounts for every top-level Unit field and all twelve official
`/api/v1/units` include flags. It also records the separate read surfaces for
sensor metadata, latest sensor values, maintenance, filling, schedules and
command audit. Raw messages, decrypt material and command execution never
enter an operational UI projection.

Cadence is a product boundary:

- `hot`: current position, state, counters and classified latest readings;
- `warm`: slowly changing operational records such as maintenance plans;
- `cold`: unit, equipment and calculation profiles;
- `on_demand`: restricted or historical details that need explicit policy;
- `never`: secret, raw or command material outside the telemetry plane.

Provider packages may implement catalogued families incrementally, but they
must not move fields between classifications or cadences implicitly. A new
Data Product and its Foundry subject aspect must be explicit and versioned.