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.

# Measure movement by journey and cycle

KnitKnot freezes the before-state, keys measurement to each published version, and shows what moved after a managed change.

## Freeze the baseline first

A completed benchmark must be frozen before the first managed revision is published. Without that barrier, the original representation is lost and the later comparison cannot support the program's promise.

## Key the record to the revision

Each published version carries its release identity, base content hash, overlay version, and evidence snapshot. The cycle report connects those records to the next eligible benchmark window.

## Use association language by default

The default statement is changed -> measured movement. KnitKnot shows visibility, head-to-head, and misrepresentation movement per journey and per cycle, with the revision and evidence beside it.

## Treat insufficient data as a result

When a journey or cycle falls below its reporting floor, the report says insufficient data. It does not print a delta from a sample too thin to interpret.

## Holdouts govern causation

A qualifying holdout experiment is the only path to causal language for a specific per-page result. Headline journey and workspace rates remain association-grade.

## Keep traffic in separate lanes

Verified crawler fetches, delivery outcomes, agent tool calls, and AI-referred visits are displayed as distinct facts. They are not added together and they are not the promised outcome.

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

Measurement

Know what moved after every managed cycle.

KnitKnot freezes the representation before managed content, records what published, and measures the next eligible benchmark at the same journey and cycle grain.

Product evidence plate
C12

Cycle measurement report

Journey-level record

Measured

Journey reports

Frozen baseline

Competitor preferred

Frozen benchmark · Cycle 11

Next eligible benchmark

Mixed outcome

Eligible benchmark · Cycle 12

Material misrepresentations

Changed → measured movement. The journey cleared its reporting floor.

Before

4 captured

After

1 captured

R

Publish record

Version 12 · approved fact set 4f8a · manual approval
Cycle epoch

The baseline comes first.

A managed publish cannot be interpreted without the representation that came before it. KnitKnot preserves that record, then waits for a comparable benchmark window.

Cycle 12

The before-state is locked before the first managed change.

Baseline barrier

Publishing waits until the benchmark record is complete.

  1. 01

    Freeze

    Baseline benchmark

    Questions, answer cells, engines, and journey scope are pinned.

  2. 02

    Publish

    Managed version

    The release records its content hash, evidence snapshot, and approval event.

  3. 03

    Wait

    Eligible window

    The next benchmark must use the same measurement grain and clear the reporting floor.

  4. 04

    Read

    Cycle report

    Each journey resolves to measured movement, insufficient data, or no material change.

The cycle epoch is the workspace-wide window between comparable benchmark runs. Page receipts remain attached as evidence.
Reporting states

The report can leave the delta blank.

Thin data and unchanged evidence remain visible. KnitKnot reports the state instead of filling the gap with a favorable number.

State

Measured movement

Comparable windows cleared the floor for this journey.

Shown

Insufficient data

The answer sample is too thin to interpret.

Withheld

No material change

The evidence did not support a useful publish.

Not applicable

Qualifying holdout

Causal language needs an experiment.

Normal cycle reports use the association register: changed → measured movement. A per-page holdout can support a causal statement only when both cohorts clear the reporting floor and the managed group moves more.

Managed cohort

Approved content published

Treated
Frozen baseline Next benchmark

Held cohort

Current version retained

Holdout
Frozen baseline Same benchmark window

Causal language needs a qualifying contrast.

Both cohorts must clear the floor, and the managed cohort must move more than the held cohort. Headline journey rates remain association-grade.

per-page experiment
Illustration of managed and held page cohorts measured against the same frozen baseline and benchmark window.
Evidence lanes

Keep every observation in its own lane.

Benchmark outcomes describe the representation. Delivery, fetch, tool-call, and referral records answer different questions and stay separate.

Benchmark

Journey outcome

Visibility · head-to-head · misrepresentation

Delivery

Response event

Served agent version · origin pass-through

Agent activity

Observed request

Verified fetch · UA-claimed fetch · tool call

AI referrals

Observed visit

Recognized referrer · landing page

These lanes appear beside one another for context. They are never added into one traffic total or treated as the promised outcome.

Audit trail

The result keeps the publish record attached.

Every cycle points back to the active version, base content hash, evidence snapshot, approval event, and benchmark window. Rollback changes the live pointer without erasing the history.

One report answers three questions.

What changed?

Open the immutable managed version.

Why was it allowed?

Inspect the evidence and approval receipt.

What moved later?

Read the next eligible journey benchmark.

Managed version

Release 12 · active

Published

Base content

a48d…91c

Evidence snapshot

4f8a…2b0

Cycle report

Regulated evaluation

Cycle 12
BaselineManaged publishEligible benchmark
Questions

Measurement FAQ

Start with the record

Start with the baseline intact.

Choose the journeys you want KnitKnot to measure across managed cycles.

Question → evidence → next evaluation