KnitKnot index
How we measure movement without overstating it.
Every cycle begins with a preserved baseline, keys the record to the published revision, and keeps thin data and outside changes visible.
Measurement unit
Journey, cycle, version.
KnitKnot measures the journeys and categories the customer chose. Each result is tied to the content version and cycle that preceded it.
- Journey
- The buyer questions and category scope the customer chose to track.
- Cycle
- The evidence packet, proposed changes, approvals, publishes, declines, and measurement window in one record.
- Version
- The immutable published artifact, base content hash, overlay identity, and evidence snapshot active for that window.
Baseline barrier
Freeze the before-state first.
A completed benchmark must be frozen before the first managed revision is published for a workspace or newly managed page class. Otherwise the original representation is gone and the comparison is not valid.
Available traffic history is labeled with its source and marked as before KnitKnot. If the deployment mode has no pre-install traffic baseline, the product says so.
Association register
Changed, then measured.
The default statement is changed -> measured movement. The cycle report shows visibility, head-to-head, and misrepresentation movement beside the revision and its receipts.
A later movement can have more than one explanation: other published pages, competitor changes, model updates, retrieval changes, or normal answer variation. KnitKnot keeps those caveats beside the result.
Reporting floor
Insufficient data is a result.
A journey or cycle below its reporting floor is labeled insufficient data. KnitKnot does not print a delta from a sample that is too thin to interpret.
The floor applies before a favorable or unfavorable story can be written. The same rule governs product reports, sales material, and case studies.
Holdout gate
Causal language requires a qualifying experiment.
A holdout comparison must include both cohorts above the floor and support the specific per-page contrast. Headline journey and workspace rates remain association-grade.
The permission is machine-gated for the result it covers. It is not a writing choice that can be applied to the rest of the account.
Separate evidence lanes
Fetches, delivery, tool calls, referrals, and benchmarks answer different questions.
KnitKnot displays each lane separately. They are not added into one total and are not treated as substitutes for journey-level benchmark movement.
Publishing enforcement
The content checks support the measurement claim.
A measured loop is only useful if the published revision is attributable and bounded. KnitKnot enforces the publishing contract before a revision can enter the measurement record.
Every managed claim must trace to the customer's existing page or an approved fact with a receipt. Human content is not withheld, keyword stuffing and fake freshness are blocked, and every revision is reversible.
Revoked or refuted claims take a priority strip path. Automatic publishing only becomes available after the relevant evaluation gates pass, and rewrites remain manual.
Open notebook
The historical experiments remain public.
The measurement lab records scorer repeatability, placebo behavior, selection bias, and variance-reduction work. These historical write-ups explain why the current reporting rules exist.