Oko
Oko/Docs

Command reference

oko index coverage

How far the catalogue covers what Transcript Lake holds: what was read at the detector's current version and what was not, and which Lake sessions with operator messages the catalogue lacks or counts short.

Invocation#

Command
oko index coverage

Inputs and options#

  • None.

Output and state effect#

  • Reads only. `lake` compares Lake with the catalogue: lakeOperatorSessions and lakeOperatorMessages are Lake's own counts (a replayed identical event counted once, as sync counts); missingFromCatalogue and missingSessions are Lake sessions with operator messages and no catalogue row; behindLake and behindSessions ({sessionId, lake, catalogue}) are rows counting fewer operator messages than Lake. Both empty means every operator message Lake holds is in Oko's catalogue; `oko index sync` closes the gap. Oko Desktop shows the same as 'Lake sessions not in Oko' on the Projection screen.

Refusals and safe exits#

  • The --db and shared database refusals of `list`, and the Transcript Lake refusals of `oko lake sources` when Lake cannot be read.

CLI reference#