What you actually get.

The shared understanding

A conversation on one side. A structured record on the other, filling in as you talk.

The record exists from the first message. Seven typed fields — goal, what it covers, what it explicitly does not, background, the systems it touches, what done means, and what happens if it breaks — each carrying the evidence behind it and a state saying how solid it is. Readiness is computed from those states and shown as vague, actionable or ready.

• Every value carries the evidence it came from
• Claims can be proposed, contested and resolved in the open
• Inference is marked inferred — confirm, never quietly folded in

Collaboration and assurance

Many people and their agents on one intent, live — and a way to say who is answerable.

Three independent layers that combine rather than compete. What you may do (viewer, commenter, contributor). What you are answerable for (reviewer, attestor, approver, evaluator). And where you belong (org admin, workspace admin, member, guest). One person can be a contributor and a reviewer; an outside auditor can attest without ever seeing the workspace.

• Every contributor is equal — there is deliberately no owner role
• Attestation is bound to a named standard, and blocks publish
• Presence, competing proposals and changes arriving without a refresh

Artifacts and the registry

What the understanding produces, versioned and addressable.

A build produces an OKF bundle — vendor-neutral markdown plus a relationship graph, not a proprietary container. Checkpoints give free undo while a draft is moving; versions are immutable published snapshots you can point at. The registry is the catalog across every intent your organisation has worked.

• Checkpoints are one-click undo; versions are permanent
• Every version is addressable and shareable
• The format is open, so the knowledge is not trapped in a schema only we can read

Knowledge and context

Everyone can build a knowledge graph. Few can afford to run one.

Bring your own sources, and every intent contributes its own context back — the claims, the evidence, the decisions and the systems touched. Over time that accumulates into a grounded map of how your organisation actually works, which is what makes each new intent start richer than the last.

• The position is cost: construction, search, refresh and maintenance
• Vocabularies capture your organisation’s own controlled language
• Evaluations define what “good” means for your work, not ours

Control and economics

What makes the rest of it safe to grant.

Token consumption is visible before a run, measured after, and capped by policy at workspace level — so unsupervised work has a floor rather than an open exposure. Every action is attributable and the record is append-only. And the whole thing runs as a managed service or inside your own network, from the same artifact.

• Spend caps at workspace level, set by an admin
• An append-only audit trail; deletion is a state, not an erasure
• SaaS or your own infrastructure, twelve-factor, no SaaS-only dependencies