kbpd.ai — home Talk to us
← Proof Studio

Surface trace · Qualitative proof

The page built from its own source

A buyer wants to see whether KBPD can make a product surface trace back to structured source material instead of a hand-built page.

surface trace ready to inspect public sanitized 3 evidence rows 7 evidence values
Inspect evidence Evidence JSON

process trace

Source-to-surface trace

Sanitized projection
The demonstration is drawn as a trace: structured source enters, page sections and public checks leave.

HERMES case-study frame

Read the case before the evidence room.

A reviewer should be able to answer seven things before opening the JSON export: what decision is in front of them, what changed against a cold start, which row carries the claim, where the value appears, what source trail exists, what purchase decision it informs, and what the case does not prove.

  1. 01 · Buyer question

    What is being decided?

    A buyer wants to see whether KBPD can make a product surface trace back to structured source material instead of a hand-built page.

  2. 02 · Cold start

    Ordinary page brief

    A conventional page brief describes the message but does not bind sections, checks, or implementation decisions.

  3. 03 · KBPD-backed

    Structured surface source

    The route source names the audience, primary action, components, checks, and proof boundaries.

  4. 04 · Boundary

    Qualitative proof

    It demonstrates traceability rather than measuring outcome lift.

Best public row route-built-as-public-page Publicly inspectable

Proof row

The source-backed route is published

The demonstration exists as an inspectable public route and is included in the static site build.

Supports the claim that this is a rendered surface trace, not only an internal planning artifact.
Evidence value
Run date: Launch build Date label attached to this public proof case.
Source trail
Route source structured route record · Public projection
Buyer decision
Open the demonstration The output does not just say KBPD is traceable. It shows traceability with the same page the visitor is reading.
Limit
Qualitative proof It demonstrates traceability rather than measuring outcome lift.

Evidence room

Inspect the evidence, values, and limits.

This is the public review surface for the case. Each row names the observation, the evidence values it stands on, the source trail, the boundary, and the matching structured entry in the evidence export.

Evidence JSON
Review order Question -> evidence -> value -> source -> limit Start with the case question, then inspect what the claim is allowed to stand on.
Evidence export /proof/how-it-works-dogfood/evidence.json The same evidence rows are emitted as JSON for independent review.
Claim boundary Qualitative proof The page cannot claim more than this status supports.
Source availability

A source trail is not always a raw public artifact. Public projection means the source has been redrawn or summarized; retained source means it is named for audit but withheld until redaction clears.

Public projection
3
Retained source
0
Pending run
0
Evidence rows
3
Reviewed public observations
Evidence values
7
Metric and run values exposed for review
Source trail
3
Artifacts named for review
Claim status
Qualitative proof
Claim boundary for publication

Claim under review

The demonstration page is itself a rendered proof: its sections, route intent, checks, and implementation plan were specified before code.

The output does not just say KBPD is traceable. It shows traceability with the same page the visitor is reading.

Date
Launch build
Sample
One production route
Provenance
Sanitized route-source projection
Reproducibility
The public page includes the rendered trace; source excerpts are summarized.
01 Four source families are bound to the route Public projection evidence_facts[0]
Observed
The page is backed by route, process, narrative, and code-emission records rather than a standalone marketing brief.
Evidence
Run metadata and source artifacts name the structured route record, narrative record, code plan, and process trace.
Supports
Supports the claim that the public route traces back to structured source material.
Evidence values used
Source trail
Limit that constrains this row

This is one route, not the whole product.

Evidence id four-source-families-bound Review URL #fact-four-source-families-bound
02 The source-backed route is published Publicly inspectable evidence_facts[1]
Observed
The demonstration exists as an inspectable public route and is included in the static site build.
Evidence
The proof case links to `/how-it-works`; build output includes `/how-it-works/index.html`.
Supports
Supports the claim that this is a rendered surface trace, not only an internal planning artifact.
Evidence values used
Source trail
Limit that constrains this row

It demonstrates traceability rather than measuring outcome lift.

Evidence id route-built-as-public-page Review URL #fact-route-built-as-public-page
03 Numeric lift is held back Publicly inspectable evidence_facts[2]
Observed
The page avoids a numeric improvement claim until the controlled comparison clears its gates.
Evidence
The proof case metric identifies claim discipline as the primary gate.
Supports
Supports the limitation boundary around what this case proves.
Evidence values used
Source trail
Limit that constrains this row

This is one route, not the whole product.

Value links

data-02-primary-gate

Evidence id numeric-claim-held-back Review URL #fact-numeric-claim-held-back

Evidence values

The values this proof is allowed to stand on

Field Value Meaning
Source families Value handle: data-01-source-families 4 Route, process, narrative, and code-emission records inform the page.
Primary gate Value handle: data-02-primary-gate claim discipline The page explicitly avoids a numeric improvement claim until the benchmark runs.
Run date Value handle: data-03-run-date Launch build Date label attached to this public proof case.
Sample Value handle: data-04-sample One production route Sample size or unit under review.
Provenance Value handle: data-05-provenance Sanitized route-source projection Where the public projection says the evidence came from.
Reproducibility Value handle: data-06-reproducibility The public page includes the rendered trace; source excerpts are summarized. What a reviewer can repeat or inspect publicly.
Claim status Value handle: data-07-claim-status qualitative proof The maximum strength of the public claim.

Source trail

Where the public proof can point

  • source-01-route-source Route source structured route record · public projection
  • source-02-narrative-source Narrative source structured narrative record · public projection
  • source-03-code-plan Code plan implementation record · public projection

Evidence status mix

What kind of support is each row?

Public projection
1
Publicly inspectable
2

Metrics

Signals carried by the case

  • 4 Source families Route, process, narrative, and code-emission records inform the page.
  • claim discipline Primary gate The page explicitly avoids a numeric improvement claim until the benchmark runs.

Source artifacts

Where the evidence comes from

  • Route source structured route record · public projection
  • Narrative source structured narrative record · public projection
  • Code plan implementation record · public projection

Case quality review

This case has a cold-review quality score.

This is a cold-review rubric, not a sales claim. It checks whether the case can be understood, inspected, bounded, and acted on.

Overall 5.0 Launch-readable

Cold-audience clarity

5.0

A reviewer gets the situation, contrast, and buyer decision without reading the JSON.

Evidence visibility

5.0

The case exposes proof rows, values, source handles, and excerpts before the JSON export.

Limitation clarity

5.0

The page names what the case proves and what it does not prove.

Visual hierarchy

5.0

The route uses visuals, storyboards, or surface frames to break the proof into inspectable layers.

Purchase motivation

5.0

The proof sends the buyer to an evidence room, artifact link, pricing path, or local run.

Next depth gate

Cold-audience clarity: Tighten the opening latch or before/after language when the case still needs explanation.

Open case evidence

Evidence docket

Review the evidence rows behind the case.

Evidence JSON
Evidence rows
3
Public projection
1
Publicly inspectable
2
  1. 01 Public projection

    Four source families are bound to the route

    Observed
    The page is backed by route, process, narrative, and code-emission records rather than a standalone marketing brief.
    Evidence
    Run metadata and source artifacts name the structured route record, narrative record, code plan, and process trace.
    Supports
    Supports the claim that the public route traces back to structured source material.
  2. 02 Publicly inspectable

    The source-backed route is published

    Observed
    The demonstration exists as an inspectable public route and is included in the static site build.
    Evidence
    The proof case links to `/how-it-works`; build output includes `/how-it-works/index.html`.
    Supports
    Supports the claim that this is a rendered surface trace, not only an internal planning artifact.
  3. 03 Publicly inspectable

    Numeric lift is held back

    Observed
    The page avoids a numeric improvement claim until the controlled comparison clears its gates.
    Evidence
    The proof case metric identifies claim discipline as the primary gate.
    Supports
    Supports the limitation boundary around what this case proves.

Evidence Flow

Read the proof as a chain, not a claim.

Each case has to survive the same path: starting condition, system-backed change, visible result, retained evidence, stated limitation, and a next action.

Source families 4
Primary gate claim discipline

Claim

The demonstration page is itself a rendered proof: its sections, route intent, checks, and implementation plan were specified before code.

The output does not just say KBPD is traceable. It shows traceability with the same page the visitor is reading.

Before / after

Same use case. Different starting conditions.

Before · loose narrative

Ordinary page brief

A conventional page brief describes the message but does not bind sections, checks, or implementation decisions.

Explain the pipeline. Add a demo. Make it convincing. Link to pricing.

After · route and narrative specification

Structured surface source

The route source names the audience, primary action, components, checks, and proof boundaries.

Route intent, scroll trace, rendered specimen, and no numeric claim until the controlled comparison runs.

Evidence

What this case actually carries.

Run metadata

Date
Launch build
Sample
One production route
Provenance
Sanitized route-source projection
Reproducibility
The public page includes the rendered trace; source excerpts are summarized.

Metrics

  • 4 Source families Route, process, narrative, and code-emission records inform the page.
  • claim discipline Primary gate The page explicitly avoids a numeric improvement claim until the benchmark runs.

Source artifacts

  • Route source structured route record · public projection
  • Narrative source structured narrative record · public projection
  • Code plan implementation record · public projection

Limitations

What this case does not prove.

Next

Follow this proof into the product.

Open the demonstration Talk to us