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.

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

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

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

Managed agent content

Every benchmark reopens the pages that matter.

KnitKnot reviews search demand, negative-sentiment gaps, co-cited targets, and approved facts after each eligible benchmark. Material changes become checked revisions built from your Fact Ledger and published under your policy.

Product evidence plate
Site / Updates / basalt.io

Managed revision

Correct the access-control claim

Proposal p-084 · base current
basalt.io/enterprise/securityBounded addition · 2 claims
38Enterprise access controls
39−Security controls are available for enterprise teams.
39+Enterprise plans include SAML SSO and role-based access control.
40+Admins can scope permissions by workspace and role.
41See the access-control documentation for configuration details.
Managed cycle

Keep the page, evidence packet, and release on one record.

Diagnosis, writing, review, and publishing stay connected.

  1. 01

    Read signals

    Demand, benchmark gaps, and verified activity set the review scope.

  2. 02

    Assemble

    The page, approved facts, and structured signals form the packet.

  3. 03

    Propose

    KnitKnot authors a bounded revision against the current page hash.

  4. 04

    Check

    Every claim, link, number, and locator must pass.

  5. 05

    Approve

    The workspace policy decides who can release it.

  6. 06

    Publish

    An immutable version becomes the active agent page.

A review can end with no change. KnitKnot keeps the current version active when the evidence is unchanged, too thin, or outside the page's scope.

Weekly inputs

Four signals decide whether a hosted page should move.

They can set the topic, urgency, or evidence target. They cannot introduce an unsupported claim.

Search-demand topics

Current search demand and the active question library show which buyer topics merit review.

Negative sentiment

Repeated objections, inaccuracies, and losing answers identify a representation gap to investigate.

Co-cited targets

Pages repeatedly cited beside the answer reveal the proof environment the revision must address.

Approved facts

Current-page substance and Fact Ledger receipts define the claims the hosted page is allowed to make.

Fact Ledger

The approved Fact Ledger is the authoring boundary.

Choose a fact to see its value, origin, receipts, and the managed pages that use it.

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

A revoked fact can be traced to every dependent revision. A missing receipt blocks the claim before publish.

Open the Fact Ledger
Revision contract

The diff carries its proof with it.

Reviewers see the changed copy beside the records that support it.

proposal p-084 / access-control correction

7 checks passed

Added claim

Enterprise plans include SAML SSO and role-based access control.

F-128 F-131

Base page

hash current

Locator

Matched

Claim support

Passed

Publish history

Rollback changes the pointer, not the record.

Every release keeps its evidence, approval, and status. Choose a version to inspect the record.

Release history

release-0142Active

Access-control correction

Added two approved facts to the enterprise security page.

Evidence
3 receipts
Approval
Customer reviewer
Audit record
Retained

Rollback moves the active pointer.

It does not erase the newer release or rewrite the audit history.
Publishing boundary

Six rules sit between a proposal and your domain.

01

Claims need support

A claim without an approved record fails the compile.

02

Human content stays intact

The agent version adds supported content without withholding the human page.

03

Freshness must be earned

Dates change only when the content changes.

04

Every change is attributable

The release records who changed what, why, and under which policy.

05

Revoked claims take the fast path

Dependent content is stripped without waiting for the scheduled cycle.

06

Automatic publishing is gated

Each eligible revision class must pass its evaluation gate.

Questions

Managed content FAQ

Start with the record

Turn the next benchmark into a better agent-facing page.

Freeze the baseline, choose the first hosted pages, and review an evidence-backed revision with its receipts attached.

Question → evidence → next evaluation