# Fact Ledger

> Keep the approved facts, receipts, owners, freshness, and page dependencies behind every managed Agent Version in one record.

- Canonical: https://knitknot.ai/product/fact-ledger/
- Part of: Get Agent Ready

## The fact ledger sets the authoring boundary

Each approved fact states what a managed page may say and points to the evidence that supports it. A fact keeps its origin, receipts, review state, owner, and the managed pages that depend on it.

## 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.