Connected Runtime

Connect a trusted external runtime to LumenFlow so sessions, governed tool calls, and evidence receipts stay inside the canonical control plane.

Complete the runtime you already have#

A connected runtime lets teams keep a trusted external agent runtime while adding LumenFlow governance. It is not a second dashboard, a bridge-only ledger, or a public compute marketplace.

The bridge proves the trusted-compute path:

external runtimes identify themselves as canonical connected activity
governed tool calls still pass through LumenFlow Rules, budgets, and approval gates
external-runtime proof lands in the same Evidence and Replay surfaces as first-party Sidekick work

Routes#

A connected runtime uses the same v1 routes as other governed runtime activity:

Action	Route	Why it matters
Register	`POST /api/v1/sessions`	Establishes stable bridge session identity
Dispatch	`POST /api/v1/sidekick/tools/[toolName]`	Sends tool requests through canonical policy, approval, and budget checks
Evidence	`POST /api/v1/evidence`	Stores bridge-attributed receipts in the Evidence Vault

Evidence receipts submitted by a connected runtime are stamped with:

payload.bridge_identity — bridge kind, runtime name/version, external session, capability manifest, and acting principal when provided
payload.bridge_session — LumenFlow session and agent identifiers
payload.governance_context — approval mode, budget scope, workspace role, authority mode, or observed revision when provided

Environment#

export LUMENFLOW_BASE_URL="https://lumenflow.cloud"
export LUMENFLOW_API_KEY="lf_..."