Build your first governed knowledge flow

What you will build

A bounded flow that answers from one approved source set and returns intentional silence outside that evidence.

Inputs and ownership

• One narrow business question
• An approved source owner
• A defined user or application role

Blueprint

This illustrates the governed fields to define during onboarding; it is not a public production API contract.

{
  "knowledge_unit": "support-policy",
  "source_version": "2026-08",
  "allowed_scope": ["support-agent"],
  "insufficient_evidence": "abstain",
  "audit": { "retain_claim_basis": true }
}

Build it step by step

1. 01

   Choose the bounded use case

   Write the question, the permitted user and the decision that the answer may influence.

2. 02

   Register the source identity

   Assign an owner, version, effective date and retirement rule before the material enters inference.

3. 03

   Create the VARVE boundary

   Separate payload, scope policy and audit anchor so content and control do not collapse into one object.

4. 04

   Set intentional silence

   Define what counts as insufficient evidence and the exact behavior expected when that condition is met.

5. 05

   Verify the trail

   Run supported and unsupported prompts, then inspect the basis retained for every material claim.

Prove the governed path

• The permitted path produces an answer from approved evidence.
• An unsupported request returns an explicit governed outcome.
• Every material claim resolves to a known knowledge unit.
• The decision can be rerun after a source version changes.