KnitKnot

# Issues and playbooks

Turn benchmark losses and damaging claims into issues and customer-managed response plans.

Issues and playbooks keep the diagnosis, evidence, response plan, ship record, and later measurement together when the customer team owns the work.

Managed content is another response option: an evidence packet, proposed Agent version revision, approval decision, published version, and later measurement window. If **Content → Updates** is available in your workspace, follow [Review a proposed Agent version update](/docs/review-managed-updates/) for the approval steps. Customers who write and publish the content themselves can use the issue and playbook records below.

## Issues

Material gaps can become **issues** : persistent records with evidence attached. The main kinds include:

  • - **Factual errors** : AI states something that conflicts with available company facts and supporting receipts.
  • - **Outdated claims** : a statement conflicts with dated evidence or a newer canonical fact.
  • - **Missed capabilities** : a capability you have that AI says you lack, often while crediting a competitor with it.
  • - **Losing comparisons** : head-to-heads where AI consistently picks a competitor, with the cited reasons.
  • - **Visibility gaps** : categories where competitors surface organically and you don't.

Issues are prioritized using evidence such as reach, severity, demand, concentration, and source ownership. Each issue resolves to the right evidence grain: a claim and quote, captured answer, cited or owned page, coverage record, or site check.

Issues keep their identity and history across qualifying full benchmarks. Reach can fall to zero, and an issue can become dormant after repeated zero observations, without erasing the record. If the same signature returns, KnitKnot redetects the existing issue instead of creating a disconnected alert.

## Playbooks

A **playbook** turns one or more issues into a concrete create, revise, or repair action. Page-touching playbooks provide a ready-to-edit brief with relevant evidence, buyer vocabulary, structure, and verified proof points where available. Technical playbooks provide a remediation plan instead of article copy.

For the current screens and exact steps, see [Work an issue and ship a playbook](/docs/work-an-issue-and-playbook/).

The source view can provide the bridge: an issue describes *what* is happening, reliable citation and content evidence show which pages are involved, and the playbook describes *what to ship*. A claim without a reliable citation signal remains unattributed.

## Measurement after shipping

When you mark a playbook shipped, KnitKnot records the before-state when a completed full benchmark is available. After a later full benchmark completes, the impact view compares observed score, answer, citation, and linked-issue changes. Direct citation pickup is shown when it exists; other movement remains descriptive rather than being presented as proof of causality.

The customer-managed loop keeps the before-state and later comparison visible. The managed workflow adds the governed publishing and cycle record between those points.

Docs navigation
Docs › Core concepts

Issues and playbooks

Turn benchmark losses and damaging claims into issues and customer-managed response plans.

Updated

Issues and playbooks keep the diagnosis, evidence, response plan, ship record, and later measurement together when the customer team owns the work.

Managed content is another response option: an evidence packet, proposed Agent version revision, approval decision, published version, and later measurement window. If Content → Updates is available in your workspace, follow Review a proposed Agent version update for the approval steps. Customers who write and publish the content themselves can use the issue and playbook records below.

Issues

Material gaps can become issues : persistent records with evidence attached. The main kinds include:

  • Factual errors : AI states something that conflicts with available company facts and supporting receipts.
  • Outdated claims : a statement conflicts with dated evidence or a newer canonical fact.
  • Missed capabilities : a capability you have that AI says you lack, often while crediting a competitor with it.
  • Losing comparisons : head-to-heads where AI consistently picks a competitor, with the cited reasons.
  • Visibility gaps : categories where competitors surface organically and you don’t.

Issues are prioritized using evidence such as reach, severity, demand, concentration, and source ownership. Each issue resolves to the right evidence grain: a claim and quote, captured answer, cited or owned page, coverage record, or site check.

Issues keep their identity and history across qualifying full benchmarks. Reach can fall to zero, and an issue can become dormant after repeated zero observations, without erasing the record. If the same signature returns, KnitKnot redetects the existing issue instead of creating a disconnected alert.

Playbooks

A playbook turns one or more issues into a concrete create, revise, or repair action. Page-touching playbooks provide a ready-to-edit brief with relevant evidence, buyer vocabulary, structure, and verified proof points where available. Technical playbooks provide a remediation plan instead of article copy.

For the current screens and exact steps, see Work an issue and ship a playbook.

The source view can provide the bridge: an issue describes what is happening, reliable citation and content evidence show which pages are involved, and the playbook describes what to ship. A claim without a reliable citation signal remains unattributed.

Measurement after shipping

When you mark a playbook shipped, KnitKnot records the before-state when a completed full benchmark is available. After a later full benchmark completes, the impact view compares observed score, answer, citation, and linked-issue changes. Direct citation pickup is shown when it exists; other movement remains descriptive rather than being presented as proof of causality.

The customer-managed loop keeps the before-state and later comparison visible. The managed workflow adds the governed publishing and cycle record between those points.