developer map products compose by evidence, gates, and ownership

Kontour for developers

which product owns what, and how the pieces fit

Kontour is a product line for making AI-assisted and human-operated work inspectable. Surface owns trust records. Flow owns process semantics. Veritas owns repo readiness. Flow Agents brings those disciplines into local agent workflows. Console makes the resulting state operable without taking over the products it observes.

Start with ownership → Open repositories
Flow Agents agent workflow coordination
Builder Kit build path, verification, release readiness
Veritas repo readiness and evidence findings
Flow process gates and route-backs
Surface claims, evidence, status, trust reports

Ownership boundaries

Each product owns one layer of the work.

Composition is intentionally one-way: product layers can consume trust and process evidence, but the evidence substrate does not depend on a specific agent, workflow, or application.

Tools and workflows
Flow Agents runs local agent workflows, skills, sidecars, and kits
Builder Kit consumes Flow, Veritas, and Surface signals for build work
Governance and process
Veritas owns repo standards, readiness, evidence findings, and exceptions
Flow owns paths, transitions, gates, route-backs, and next action
Trust substrate
Surface owns portable claims, evidence, policies, status, Trust Reports, and transparency gaps
Operating view
Console aggregates product-owned projections and routes attention back to the owner

Evidence lifecycle

A change moves by gates, evidence, and state handoffs.

This is the intended composition model. The exact integration depends on which products a team adopts, but ownership stays stable.

01 Work item idea, issue, customer promise, or operational change
02 Flow path required states, gates, evidence, and route-backs
03 Agent work Builder Kit or local workflow executes with sidecar state
04 Readiness evidence Veritas checks repo standards and change evidence
05 Trust projection Surface packages claims, evidence, status, and gaps
06 Decision view Console or a gate shows what is ready, blocked, stale, or missing

Composition contracts

Surface

Owns: portable claims, evidence, policies, status, Trust Reports, and trust vocabulary.

Composes by: makes product facts inspectable for Console, Flow gates, Veritas reports, and downstream operators.

Product page GitHub

Flow

Owns: process paths, transitions, gates, route-backs, exceptions, and next-action semantics.

Composes by: uses Surface or Veritas evidence as gate input without owning claim truth or repo policy.

Product page GitHub

Veritas

Owns: repo standards, readiness checks, evidence findings, exceptions, and code-change governance.

Composes by: projects code-change readiness into evidence other products can inspect.

Product page GitHub

Flow Agents

Owns: agent workflows, skills, kits, local sidecars, verification loops, and handoff discipline.

Composes by: coordinates Builder Kit work and can consume Flow, Veritas, and Surface signals.

Product page GitHub

Use-case families

Useful anywhere claims, process, readiness, and evidence need to stay connected.

Sales / RevOps

Keep account, pipeline, renewal, and enablement claims tied to sources, freshness, approvals, and next actions.

Software delivery

Make code-change readiness, release gates, browser checks, and missing evidence visible before merge.

Public data and records

Track claim provenance, review status, staleness, and disputed facts for directories or public datasets.

Regulated advisory review

Separate authored recommendations from evidence, reviewer authority, exception handling, and final status.

Support and customer operations

Route unresolved promises, stale facts, policy exceptions, and follow-up work back to the owning system.

Research and knowledge operations

Preserve where assertions came from, what changed, which gaps remain, and who can rely on the output.

Maturity framing

Current state, near-term direction, and future possibilities are separate.

The public map should help developers decide what to inspect next, not imply a single finished control plane. Adopt one product, or compose several when the workflow needs it.

Current state

Product pages, open repositories, local workflow artifacts, Surface trust reports, Veritas readiness evidence, Flow Agents workflows, and early Console projections are all inspectable now.

Near-term direction

Tighter cross-product handoffs, more published examples, clearer resource-shaped contracts, and richer Console projections are being wired in product by product.

Future possibilities

Kubernetes-style operators, hosted coordination, and broader runtime adapters are possible future integrations. They are not current requirements for using the products.

inspect the product line

$ open /developers


✓ Surface trust records and reports

✓ Flow paths, gates, route-backs

✓ Veritas repo readiness evidence

✓ Flow Agents local workflow coordination

→ Console operating view, not authority

Where to go next

Inspect Surface trust records Inspect Flow gates Inspect Veritas readiness Inspect Flow Agents workflows Inspect Console framing