kbpd.ai — home Talk to us
← Proof Studio

Measured pilot · Measured pilot

One review frame for many demos

A team has many experiments and needs a shared way to compare them without turning the site into a folder of disconnected artifacts.

case study pilot evidence public sanitized 3 evidence rows 7 evidence values
Inspect evidence Evidence JSON

registry map

Shared proof registry

Rendered evidence
The accumulated demos become comparable because every case enters the same evidence frame.

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 team has many experiments and needs a shared way to compare them without turning the site into a folder of disconnected artifacts.

  2. 02 · Cold start

    Loose demo pile

    Each demo has its own layout, vocabulary, maturity level, and proof standard.

  3. 03 · KBPD-backed

    Proof case frame

    Every demo becomes a proof case with the same claim, use case, evidence, limitation, and CTA shape.

  4. 04 · Boundary

    Measured pilot

    The first registry is curated, not automatically generated.

Best public row registry-is-curated Publicly inspectable

Proof row

Registry is curated, not automatic

The current registry is intentionally curated and raw experiment assets still require redaction before publication.

Supports the boundary between launch proof organization and future automated ingestion.
Evidence value
Run date: Launch build Date label attached to this public proof case.
Source trail
Demo registry public projection · Public projection
Buyer decision
Browse the studio The value is accumulation. New tests become comparable because they enter the same frame.
Limit
Measured pilot The first registry is curated, not automatically generated.

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/battery-review-console/evidence.json The same evidence rows are emitted as JSON for independent review.
Claim boundary Measured pilot 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
2
Retained source
0
Pending run
0
Evidence rows
3
Reviewed public observations
Evidence values
7
Metric and run values exposed for review
Source trail
2
Artifacts named for review
Claim status
Measured pilot
Claim boundary for publication

Claim under review

A consistent review frame makes accumulated tests legible: every demo carries the same claim, evidence, limitation, and next-action fields.

The value is accumulation. New tests become comparable because they enter the same frame.

Date
Launch build
Sample
Eight proof families
Provenance
Sanitized public registry
Reproducibility
The registry is validated at build time.
01 Eight proof families are registered Validated by build evidence_facts[0]
Observed
The public registry currently contains eight proof cases spanning comparisons, demos, a case study, a surface trace, and a benchmark placeholder.
Evidence
Proof Studio index renders eight cards; validator output reports eight proof cases passed validation and leak scan.
Supports
Supports the claim that accumulated demos now enter one shared review frame.
Evidence values used
Source trail
Limit that constrains this row

The first registry is curated, not automatically generated.

Evidence id eight-proof-families-registered Review URL #fact-eight-proof-families-registered
02 Every public case has status and limits Validated by build evidence_facts[1]
Observed
The proof-case validator rejects entries without claim status, limitations, visuals, metrics, source artifacts, and evidence facts.
Evidence
`web/scripts/validate-proof-cases.ts` is part of the web prebuild and exits nonzero on missing required fields.
Supports
Supports the claim that public proof cases share comparable evidence standards.
Evidence values used
Source trail
Limit that constrains this row

Raw experiment assets require redaction before publication.

Evidence id required-status-and-limit-fields Review URL #fact-required-status-and-limit-fields
03 Registry is curated, not automatic Publicly inspectable evidence_facts[2]
Observed
The current registry is intentionally curated and raw experiment assets still require redaction before publication.
Evidence
Limitations section states the first registry is curated and raw experiment assets require redaction.
Supports
Supports the boundary between launch proof organization and future automated ingestion.
Evidence values used
Source trail
Limit that constrains this row

The first registry is curated, not automatically generated.

Evidence id registry-is-curated Review URL #fact-registry-is-curated

Evidence values

The values this proof is allowed to stand on

Field Value Meaning
Proof families Value handle: data-01-proof-families 8 The launch registry covers comparisons, local demos, surface traces, cases, and benchmark placeholders.
Required labels Value handle: data-02-required-labels 100% Every public case has a claim status and limitation list.
Run date Value handle: data-03-run-date Launch build Date label attached to this public proof case.
Sample Value handle: data-04-sample Eight proof families Sample size or unit under review.
Provenance Value handle: data-05-provenance Sanitized public registry Where the public projection says the evidence came from.
Reproducibility Value handle: data-06-reproducibility The registry is validated at build time. What a reviewer can repeat or inspect publicly.
Claim status Value handle: data-07-claim-status measured pilot The maximum strength of the public claim.

Source trail

Where the public proof can point

  • source-01-demo-registry Demo registry public projection · public projection
  • source-02-validation-script Validation script build gate · public projection

Evidence status mix

What kind of support is each row?

Validated by build
2
Publicly inspectable
1

Metrics

Signals carried by the case

  • 8 Proof families The launch registry covers comparisons, local demos, surface traces, cases, and benchmark placeholders.
  • 100% Required labels Every public case has a claim status and limitation list.

Source artifacts

Where the evidence comes from

  • Demo registry public projection · public projection
  • Validation script build gate · 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 4.4 Inspectable with caveats

Cold-audience clarity

4.0

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

Evidence visibility

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

4.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
Validated by build
2
Publicly inspectable
1
  1. 01 Validated by build

    Eight proof families are registered

    Observed
    The public registry currently contains eight proof cases spanning comparisons, demos, a case study, a surface trace, and a benchmark placeholder.
    Evidence
    Proof Studio index renders eight cards; validator output reports eight proof cases passed validation and leak scan.
    Supports
    Supports the claim that accumulated demos now enter one shared review frame.
  2. 02 Validated by build

    Every public case has status and limits

    Observed
    The proof-case validator rejects entries without claim status, limitations, visuals, metrics, source artifacts, and evidence facts.
    Evidence
    `web/scripts/validate-proof-cases.ts` is part of the web prebuild and exits nonzero on missing required fields.
    Supports
    Supports the claim that public proof cases share comparable evidence standards.
  3. 03 Publicly inspectable

    Registry is curated, not automatic

    Observed
    The current registry is intentionally curated and raw experiment assets still require redaction before publication.
    Evidence
    Limitations section states the first registry is curated and raw experiment assets require redaction.
    Supports
    Supports the boundary between launch proof organization and future automated ingestion.

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.

Proof families 8
Required labels 100%

Claim

A consistent review frame makes accumulated tests legible: every demo carries the same claim, evidence, limitation, and next-action fields.

The value is accumulation. New tests become comparable because they enter the same frame.

Before / after

Same use case. Different starting conditions.

Before · artifact collection

Loose demo pile

Each demo has its own layout, vocabulary, maturity level, and proof standard.

Interesting work exists, but visitors cannot tell what is proven and what is just promising.

After · shared app surface

Proof case frame

Every demo becomes a proof case with the same claim, use case, evidence, limitation, and CTA shape.

The studio turns accumulated experiments into a browsable product proof system.

Evidence

What this case actually carries.

Run metadata

Date
Launch build
Sample
Eight proof families
Provenance
Sanitized public registry
Reproducibility
The registry is validated at build time.

Metrics

  • 8 Proof families The launch registry covers comparisons, local demos, surface traces, cases, and benchmark placeholders.
  • 100% Required labels Every public case has a claim status and limitation list.

Source artifacts

  • Demo registry public projection · public projection
  • Validation script build gate · public projection

Limitations

What this case does not prove.

Next

Follow this proof into the product.

Browse the studio Talk to us