Skip to main content

Proof

A proof record is a bounded test: a safe artifact, a procedure, an expected observation, and an acceptance criterion the buyer defined or that is objectively testable. It is not a case study, a testimonial, or a demo script.

Every proof carries at least one evidence reference. A proof with no evidence record cannot be created.

The only vertical-scoped record in the chain​

Problems and solutions carry no vertical scope. Proof does, and deliberately: a result was observed at a specific kind of account doing a specific kind of work, and that context decides whether it may be reused elsewhere.

Each vertical declares a proof_transfer_level:

direct      → the proof may be used in other verticals as written
conditional → the proof may be used only with its stated condition attached
prohibited  → the proof may be used only inside its own vertical

The level is recorded explicitly even when transfer is prohibited. A vertical never defaults to direct.

Bounding the claim​

A proof states what was measured, over what period, at what kind of account — and what was not measured. An unbounded proof is not usable, because a rep cannot tell where it stops applying.

A customer outcome is never restated as a general product claim.

Why this folder gates the whole library​

Nothing generates without proof. W11 refuses to render an asset from a chain containing a draft solution or a missing proof, which is why every audience binding here is currently draft and every generated card is blocked from making any proof, outcome, benchmark, reference, or numeric claim.

Naming​

One proof per file, named for its immutable ID: PF_<vertical>_<nnn>.md, for example PF_M1_V2_001.md.

Current records​

None. This folder is empty.

That single fact is what blocks the library end to end:

  • No audience binding can satisfy the W11 call-sheet preconditions.
  • No solution is generation-ready.
  • Both cards in generated/ had to be generated in provisional mode with every proof claim suppressed.

Authoring​

W7 in the authoring workflows. It requires a resolving solution ID and at least one evidence record, so W9 runs first.

W9 currently halts: the owning location for EV_ evidence records is unsettled. That is the first thing to resolve before this folder can hold anything — see the open questions in the workflows document.