Kontour Console

Kontour Console

One operating plane for the whole suite. Console surfaces what is true, what is stale, what is blocked, and what comes next — without becoming the authority for any primitive.

Product Boundaries What Console owns, what the primitives own, and how suite-level authority is kept separate from product semantics. Event & Projection Schema The v0.1 event envelope, projection envelope, local JSONL stream convention, replay rules, and cross-product refs. Emitter & Sink Contract Control-plane versus telemetry-plane records, local file output, multi-sink fanout, and inert action descriptors. Hosted Console How a hosted deployment composes the base Console with deployment-owned infrastructure and environment mapping. Flow Agents Integration Local and hosted emission for Flow Agents: sink selection, descriptor location, trusted producer identity, and boundary rules. Telemetry Descriptor Descriptor-driven analytics: facets, flows, record source mappings, and the /api/telemetry query contract.

How Console composes the suite

Console reads product-owned records — Surface claims, Flow runs and gates, Survey review items, Veritas readiness checks, Flow Agents sessions — and presents the integrated operating state without redefining what any of them mean.

The primitives remain portable and useful without Console:

  • Surface owns claim trust state: verified, stale, disputed, fresh.
  • Flow owns process and gate semantics: runs, gates, route-backs, exceptions.
  • Survey owns fact-review records: sources, candidates, review decisions.
  • Veritas owns repo and change governance: standards, requirements, merge readiness.
  • Flow Agents owns agent-facing runtime: modes, skills, adapters, workflow learning.

Console answers the suite-level questions: what is currently true, what is blocked, what proof supports this state, and what is the next action.

Local first

Console v0 runs locally without a hosted service. Producers write JSONL event streams and projection snapshots under .kontour/. The console-inspect CLI reads them and prints a current operating state summary. kontour serve exposes the same state over a loopback SSE hub for the UI.

npx @kontourai/console console-inspect

See the Golden Demo for a full end-to-end example across Flow, Survey, and Surface.

Architecture decisions