Register source-bound knowledge as a VARVE

What you will build

A knowledge unit whose content, owner, source version and audit identity remain inseparable throughout its lifecycle.

Inputs and ownership

• Approved source material
• Source owner
• Version or effective date

Blueprint

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

{
  "payload_id": "policy.refunds.eu",
  "owner": "policy-operations",
  "source": "refund-policy-v4.pdf",
  "effective_from": "2026-08-01",
  "status": "active"
}

Build it step by step

1. 01

   Identify the authoritative source

   Choose the exact document or dataset that is permitted to shape answers.

2. 02

   Define payload granularity

   Keep the unit narrow enough to update or retire without disturbing unrelated knowledge.

3. 03

   Attach provenance

   Record ownership, version and effective dates in the Audit Anchor.

4. 04

   Validate retrieval

   Confirm that the unit is discoverable only inside its approved scope.

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.