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.

# Customer-managed Content Playbooks

Playbooks turn diagnosed issues into scoped content work for teams that manage their own authoring and publishing.

## What each record keeps

A playbook keeps the issue, supporting evidence, target page, proposed change, ship record, and later measurement together. Customer MCP tools expose the supported playbook fields.

## Choose who owns the page change

Use a playbook when the customer team writes and publishes the change. Eligible page classes can use the managed revision cycle when KnitKnot should propose, check, route for approval, and publish.

## Reconnect the shipped work to measurement

When the work appears on the site, KnitKnot records the page update and measures the next eligible benchmark at the same journey and cycle grain.

## Managed agent content

Managed agent content adds authoring, receipts, machine-enforced checks, approval policy, immutable publishing, and rollback. Read the current workflow at https://knitknot.ai/product/managed-agent-content/.

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

Customer-managed work

Keep evidence attached to content work your team ships.

Each playbook keeps the issue, evidence, target page, recommended change, ship record, and later measurement together. Your team owns authoring and publishing.

Product evidence plate

Correct the RBAC claim AI keeps repeating

High priority

AI tells security buyers that Basalt has no role-based access control, then cites Loupe as support. Revise the enterprise security page with the verified answer and its receipts.

Issues
2
Answers
14
Monthly value at stake
$4.8K
Overview Brief Impact

What to change

Revise · Correction basalt.io/enterprise-security
Basalt supports role-based access control for enterprise deployments. State the verified capability directly, show buyers how access is scoped, and make the supporting product evidence easy for people and AI systems to retrieve.
  1. 01 Open with the verified RBAC answer before any general security positioning.
  2. 02 Show how access control works across users, teams, and self-hosted deployments.
  3. 03 Add the company-fact receipt and link to the product documentation that proves it.
  4. 04 Answer the comparison questions where AI currently repeats the outdated claim.
Playbook record

Keep diagnosis, work, and measurement attached.

The evidence that opened the work remains available after the page ships, so the next benchmark can be read against the original diagnosis.

  1. 01 Query Pull issues, evidence, and supported playbook fields through the customer MCP tools.
  2. 02 Ship Write and publish through your own content workflow, on your own schedule.
  3. 03 Measure KnitKnot detects the page change and reads later benchmark movement against the original diagnosis.
Workflow choice

Choose who owns the page change.

Both paths carry the same evidence and the same measurement. They differ on who writes the page and who presses publish.

Playbooks compared with the managed revision cycle
Playbook Managed revision cycle
Who writes the page Your team KnitKnot proposes a bounded revision
Who publishes Your team, on your own schedule You approve; KnitKnot publishes under your policy
Page eligibility Any page your team owns Eligible managed page classes only
Checks before publish Your own review Deterministic checks, then routed approval
Rollback Your CMS history Publish receipt and rollback kept together
Evidence attached Issue, sources, approved facts Issue, sources, approved facts
Later measurement Next eligible benchmark, same journey grain Next eligible benchmark, same journey grain
Read the managed content workflow
Questions

Playbooks FAQ

Start with the record

Move from diagnosis to a scoped change.

Keep authoring in-house with a playbook, or put eligible pages into the managed revision cycle.

Question → evidence → next evaluation