Kontour Flow · process transparency

Proof, not promises.

AI agents skip steps, accept weak evidence, and summarize work as complete. Flow records the required path, the evidence each gate expected, and why the work was allowed to advance — in plain local files that survive context loss.

$ flow status dev-1847

flow run: agent-dev-flow / feature-search-filters
current step: implement

PASS  plan gate: Acceptance criteria are ready for implementation. satisfied
WAIT  implementation gate: implementation gate waiting
WAIT  verify gate: verify gate waiting

next action: attach evidence for implementation gate
continuation: resume from implement, not chat memory

Why teams adopt Flow

Evidence-gated transitions

A step is not complete because an agent says so. Gates declare typed expectations, and runs advance only when evidence satisfies them — or a human accepts an explicit, attributable exception.

Survives context loss

Every run lives in plain files under .flow/runs/. A new agent session, a teammate, or a CI job can flow resume and continue from recorded state, not chat memory.

Deterministic route-back

Failed evidence routes work back to the right step with attempt budgets derived from persisted state, so agents cannot loop silently forever.

Audit-ready reports

Every run regenerates a human-readable report.md and machine-readable report.json explaining what passed, what blocked, what was excepted, and what happens next.

Local-first, zero lock-in

A file-backed CLI and typed TypeScript library. No hosted service, no account, no telemetry. Your evidence stays in your repo.

Built to compose

Veritas can supply repo-readiness evidence, Flow Agents can enforce gates from agent harnesses — and Flow stands alone without either.

Watch the gate hold

Four commands: scaffold a demo run, check status, watch flow evaluate --exit-code refuse to pass without evidence, and resume from recorded state.

Terminal recording of flow init --demo, status, a blocked evaluate, and resume

Inspect any run, locally

The bundled loopback-only console renders a run from its local files: process graph, transition timeline, gate outcomes, evidence, and the next action.

Flow Console showing a run blocked at the verify step with gate details and evidence

Sixty seconds to a gated run

npm install -D @kontourai/flow

npx flow init
npx flow start .flow/definitions/agent-dev-flow.json \
  --run-id dev-1847 --params subject=feature-search-filters
npx flow attach-evidence dev-1847 --gate plan-gate \
  --file ./acceptance-claim.json --trust-artifact
npx flow evaluate dev-1847
npx flow resume dev-1847

Walk through it step by step