Provider-Run Mode (forbidden)

Provider-Run Mode is any test in which the Provider of a control, or anyone under its direction, generates canaries, holds labels, operates the Proof Witness or the Warden, captures fingerprints, adjudicates or controls publication. It is not a Coal Mine Protocol Engagement, whatever it is called internally, and its results are verification, not proof.

ProofJack Rating: Human 67.5% · AI 32.5% (self-estimated; No per-term record; PP-SPEC-079 AI_DISCLOSURE shares (conception 80/20, naming 55/45))

Also known as: Provider-Run, vendor-run test, proof of concept

Mynted 2026-10-23 · Updated 2026-10-23

First used: PP-SPEC-079, Proof of Performance Engagement: The Coal Mine Protocol, 13 October 2026, by Craig Thomas Ellrod

What it means

A test operated by whoever built or runs the control is the control grading itself. It does not matter whether the operator is a vendor’s field team or the customer’s own engineers who built the control. The result is verification evidence, which has its place as a baseline, and it may not be called proof.

The rules

Results of a Provider-Run test must not be published as a Performance Record, must not carry the words “Proof of Performance”, and must not be submitted to a Registry as a CMP artifact.
A Provider may run its own Dead Canary or Jailed Canary runs for internal purposes. Those are its own business and outside the specification.
An Engagement with no external party at any seam and no demonstrable internal separation is Provider-Run, whatever it is called internally. See Self-Provided Engagement.
The Provider-Run prohibition is one of the rules that can never be extended. Anything that relaxes it is a fork.

This is the Self-Attestation Oxymoron stated as a rule of engagement.

Related terms

Sources

Proof of Performance Engagement: The Coal Mine Protocol (PP-SPEC-079)

Updated 2026-10-23