KnitKnot
You are reading the agent-optimized layer of this page: the literal markdown we serve to AI crawlers and assistants, shipped in the page source of every visit. Making sure AI reads the right facts about a company is literally what KnitKnot does.

# Fact Ledger

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

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

Raw mirror of this content: https://knitknot.ai/product/fact-ledger.md. Site-wide summary: /llms.txt · full content: /llms-full.txt

Fact Ledger

Give every Agent Version one approved Fact Ledger.

The Fact Ledger keeps each publishable fact with its receipts, owner, review state, and dependent pages. Demand and journey targets can direct the work without becoming facts.

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
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
Record boundaries

Facts, demand, and targets have different jobs.

The weekly managed cycle can use all three. Only approved facts can support a new claim.

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

Fact detail

Open a fact and inspect the record behind it.

The approved value stays beside its origin, receipts, review date, and managed-page dependencies.

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
Fact contract

A usable fact needs more than a sentence.

The record keeps enough context to review the claim and find every published dependency later.

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.
Published dependencies

Approve once, then publish views of the same record.

Markdown and gated customer-domain interfaces read the approved release. They do not maintain separate claims.

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
Questions

Fact Ledger FAQ

Start with the record

Start with the facts your Agent Versions must get right.

Approve the Fact Ledger, then choose the eligible pages that should use it.

Question → evidence → next evaluation