What belongs in the Fact Ledger?

Approved company facts and the receipts, owners, review state, and page dependencies attached to them. Products, capabilities, deployment options, policies, and proof can all be represented as facts when the evidence supports them.

Are demand signals stored as company facts?

No. Search demand, benchmark questions, content gaps, and journey targets can direct the work, but they are not publishable facts. Search demand is also a proxy for buyer interest, not private AI-chat volume.

What happens when a fact changes?

The record retains its history and shows which managed pages depend on it. Revoked or refuted facts can take a priority strip path through affected Agent Versions.

Do the agent interfaces keep separate copies of each fact?

No. Markdown and gated customer-domain interfaces read published views of the same approved record. Workspace MCP is a separate authenticated service for authorized KnitKnot workspace data.

# Fact Ledger

Check disputed claims against approved facts, receipts, owners, freshness, and page dependencies in one record.

## The fact ledger sets the evidence boundary

Each approved fact points to the evidence that supports it. KnitKnot uses that record to check disputed claims and to bound what a correction or managed page may say. A fact keeps its origin, receipts, review state, owner, and dependent pages.

## Keep facts separate from direction

Demand signals show what buyers appear to care about. Journey targets define the categories and decisions the customer wants to improve. They can direct a managed revision, but neither one becomes a publishable fact. Search demand is a proxy for buyer interest, not private AI-chat telemetry.

## Trace every dependency

Managed Agent Versions, Markdown, customer-domain MCP, WebMCP, and the agent feed read from the approved record. They do not maintain separate claims. Workspace MCP is a different, authenticated service for querying authorized KnitKnot data.

## Review and revoke without losing history

Superseded and refuted facts remain in the record. When an active fact is revoked, KnitKnot can identify the dependent managed pages and take the priority strip path instead of waiting for the next scheduled cycle.

## Use the same record in every cycle

The weekly content review combines the current page, approved facts, demand and benchmark signals, content gaps, and verified activity. If the evidence does not support a material change, the current version stays active.

Fact Ledger

Know which claims your team can prove.

The Fact Ledger keeps each approved fact with its receipts, owner, review state, and dependent pages. KnitKnot uses that record to verify disputed claims and bound every published response.

Product evidence plate

Approved facts: 41; Publishable by any Agent Version

Receipts resolved: 41 of 41; Every value traces to a page you own

Review due: 3; Past the freshness window for their class

Held back: 6; No receipt yet — never published

Approved facts in one Fact Ledger
Capability	Value	Receipt	Owner
Role-scoped access	Supported	basalt.io/security Site page	Security
Private deployment	Customer-managed	basalt.notion.site/deployment Notion	Platform
Audit history	Recorded activity	docs.basalt.io/audit-log GitBook	Security
SOC 2 Type II	Current report	trust.basalt.io Trust center	Compliance

Approved facts

Publishable statements with receipts, owners, review state, and tracked page dependencies.

Sets what managed content may say

Demand signals

Search demand, benchmark questions, source patterns, content gaps, and verified activity.

Helps decide what to review

Journey targets

The categories, comparisons, and buyer decisions the customer wants to improve.

Defines the measurement scope

Company facts / Approved

Approved factRecord

Approved value

Available on Enterprise plans

Publishable

Origin page

/docs/security/sso

Last reviewed

Current cycle

Supporting receipts

Product documentation Plan matrix

Used by managed pages

Enterprise securityPlatform comparison

Value: The specific statement approved for use.
Receipt: The source or record that supports the value.
Review: The owner and current review state.
Dependencies: The managed pages and published versions that use the fact.

Approved fact Active

Security · Access controls

Role-scoped access is available on every plan.

Source: customer.com/security
Receipt: access-controls-008
Review: Customer approved

Markdown

In use

# Security and access
Role-scoped access is available...

/mcp

Built, gated

get_facts
receipt: attached

WebMCP

Experimental

get_verified_facts
read-only declaration

Agent feed

Built, gated

fact.updated
release: 024

One approval updates the next published release. The interfaces do not maintain separate claims.

See the managed content cycle See Agent delivery

Start with the evidence

Start with the claim your team needs to verify.

Open the captured answer, compare the claim with approved evidence, and choose the response the record supports.

Question → claim → source → response