Skip to main content

Module harness_service

Module harness_service 

Source
Expand description

Versioned, language-neutral service over persisted harness sessions.

The service is transport-agnostic: HarnessSessionService::handle accepts one JSON-RPC value and HarnessSessionService::poll produces subscription notifications. The CLI exposes those primitives as NDJSON over stdio.

Structs§

GatewayHealth
ORCH-17: gateway on a harness.v1.harnesses.list row.
HarnessSessionService
Stateful persisted-session service. Each instance owns its follow subscriptions; discovery and loading remain read-only.

Enums§

GatewayState
Receipt-backed evidence that a harness has a RUNNING instance right now, distinct from being merely installed (UNI-7). Detection is passive and default-on: a gateway liveness connect for daemon harnesses, a fresh SQLite WAL stamp for store-writer harnesses (precedent: the opencode follower’s -wal/-shm freshness). Control stays behind per-connection grants — this reports observations only. ORCH-17: the gateway-health noun on an inventory row. Derived from the UNI-7 running-instance probe (Hermes: state.db-wal freshness; OpenClaw: a TCP connect to the gateway endpoint resolved from its OWN config) plus the executable version — never by starting anything.

Constants§

HARNESS_SERVICE_METHODS
Every JSON-RPC method the harness service dispatches (harness.v1.capabilities reports it; ORCH-4 registry tiers must cite entries of it).
HARNESS_SERVICE_VERSION
Protocol namespace implemented by this service.
RUNTIME_EVENT_METHOD
Notification method emitted for live runtime events.
SESSION_ACTIVITY_EVENT_METHOD
Notification method emitted for normalized session-activity transitions.
SESSION_EVENT_METHOD
Notification method emitted for followed-session changes.
SESSION_INDEX_EVENT_METHOD
Notification method emitted for revisioned session-list changes.