# Managed agent content

> KnitKnot keeps eligible Agent Versions current through a weekly review of demand, benchmark evidence, content gaps, verified activity, and the approved Fact Ledger.

- Canonical: https://knitknot.ai/product/managed-agent-content/
- Part of: Get Agent Ready

## The Fact Ledger sets the boundary

Managed content can draw from the customer's existing page, approved company facts with receipts, and structured signals produced by KnitKnot. Raw third-party page text is excluded from the authoring context.

## The weekly cycle

KnitKnot reads current demand, benchmark, content-gap, source, and verified activity signals before it selects a page. It proposes bounded changes, attaches a receipt to each claim, and runs machine-enforced checks before approval. A weekly review can end with no change.

## Approval stays under policy

Customers choose manual approval or automatic approval by workspace and page class. Automatic publishing requires a passing evaluation gate, a recorded change, and one-click rollback. In-place rewrites always require manual review.

## Publishing is reversible

Every published revision is immutable. A small active pointer selects the current version, so rollback changes the pointer without erasing history. A revoked or refuted claim takes a priority strip path instead of waiting for the next weekly cycle.

## The publishing contract

KnitKnot enforces six rules: claims need support, human content is never withheld, keyword stuffing and fake freshness are blocked, every change is attributable and reversible, revoked claims take the fast removal path, and each revision class must pass its evaluation gate before automatic publishing is permitted.