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.

# Agent readiness glossary

Plain-language definitions for benchmarking AI representation, managed agent content, agent interfaces, and cycle-level measurement.


## Agent readiness

The state in which a company has a preserved benchmark of its AI representation, governed content that agents can read, and a measurement record tied to each published cycle.

## Agent-ready content

A factual, traceable page view built from approved facts and the existing human page. It remains attributable, reviewable, and reversible. [Read the guide](/learn/what-is-agent-ready-content/).

## Benchmark

A preserved set of buyer questions, captured AI answers, available sources, claim evaluations, and competitive outcomes. The benchmark provides the before-state for a managed cycle.

## Cycle

The record that connects evidence, a proposed revision, approval or decline, publication, rollback, and a later measurement window.

## Fact ledger

The approved record of facts and receipts that feeds every managed surface. The human page, Markdown agent version, customer-domain MCP, WebMCP, and agent feed are views of this ledger.

## Receipt

The evidence that supports a managed claim. A receipt can point to the customer's page or another approved fact source.

## Approval policy

The customer rule that determines whether a proposed revision requires manual approval or can publish after the relevant gates pass. Rewrites remain manual.

## Immutable version

The stored artifact for one release, including its content identity and evidence snapshot. A later release does not erase it.

## Rollback

The supported path back to an earlier approved version. Every managed revision must remain reversible.

## Insufficient data

A first-class measurement result. When a journey or cycle is below its reporting floor, KnitKnot does not print a delta.

## Measured movement

The association-grade statement used after a content change. KnitKnot shows what moved by journey and cycle while keeping outside changes visible.

## Holdout

A qualifying comparison between treated and untreated page cohorts. Both cohorts must clear the reporting floor and support the specific contrast before a narrower causal statement is permitted.

## Evidence lane

A class of observation that answers one question. Verified crawler fetches, delivery outcomes, tool calls, AI-referred visits, and benchmark results remain separate.

## Agent feed

A machine-readable change log for managed content. It reports publication and version links, not discovery or use. [Read the guide](/learn/agent-feed/).

## WebMCP

An in-browser adapter that registers read-only tools for compatible agents. It is one gated interface over the approved fact ledger. [Read the guide](/learn/webmcp/).

## Workspace MCP

The authenticated KnitKnot server used by customer assistants to query authorized benchmark and workflow data. It is separate from the public, read-only customer-domain interface.

## Playbook

A legacy customer-managed brief linked to a benchmark issue. Playbooks remain readable, but Optimization is the primary managed workflow.

Raw mirror of this content: https://knitknot.ai/learn/ai-presence-glossary.md. Site-wide summary: /llms.txt · full content: /llms-full.txt

← Guides
Published
Reading time
3 minutes

Glossary

Agent readiness glossary

Plain-language definitions for benchmarking AI representation, managed agent content, agent interfaces, and cycle-level measurement.

A source trail linking claim fragments to citations and evidence receipts

Agent readiness

The state in which a company has a preserved benchmark of its AI representation, governed content that agents can read, and a measurement record tied to each published cycle.

Agent-ready content

A factual, traceable page view built from approved facts and the existing human page. It remains attributable, reviewable, and reversible. Read the guide.

Benchmark

A preserved set of buyer questions, captured AI answers, available sources, claim evaluations, and competitive outcomes. The benchmark provides the before-state for a managed cycle.

Cycle

The record that connects evidence, a proposed revision, approval or decline, publication, rollback, and a later measurement window.

Fact ledger

The approved record of facts and receipts that feeds every managed surface. The human page, Markdown agent version, customer-domain MCP, WebMCP, and agent feed are views of this ledger.

Receipt

The evidence that supports a managed claim. A receipt can point to the customer’s page or another approved fact source.

Approval policy

The customer rule that determines whether a proposed revision requires manual approval or can publish after the relevant gates pass. Rewrites remain manual.

Immutable version

The stored artifact for one release, including its content identity and evidence snapshot. A later release does not erase it.

Rollback

The supported path back to an earlier approved version. Every managed revision must remain reversible.

Insufficient data

A first-class measurement result. When a journey or cycle is below its reporting floor, KnitKnot does not print a delta.

Measured movement

The association-grade statement used after a content change. KnitKnot shows what moved by journey and cycle while keeping outside changes visible.

Holdout

A qualifying comparison between treated and untreated page cohorts. Both cohorts must clear the reporting floor and support the specific contrast before a narrower causal statement is permitted.

Evidence lane

A class of observation that answers one question. Verified crawler fetches, delivery outcomes, tool calls, AI-referred visits, and benchmark results remain separate.

Agent feed

A machine-readable change log for managed content. It reports publication and version links, not discovery or use. Read the guide.

WebMCP

An in-browser adapter that registers read-only tools for compatible agents. It is one gated interface over the approved fact ledger. Read the guide.

Workspace MCP

The authenticated KnitKnot server used by customer assistants to query authorized benchmark and workflow data. It is separate from the public, read-only customer-domain interface.

Playbook

A legacy customer-managed brief linked to a benchmark issue. Playbooks remain readable, but Optimization is the primary managed workflow.