Mine Plan and Engagement Manifest

A Mine Plan is the committed, versioned composition of runs in an Engagement: which PP-SPEC-077 technology profiles and modes, whether PP-SPEC-078 applies, which PP-SPEC-013 measurement windows, and how many of each. The Engagement Manifest is the record, published and anchored before the first commitment, that names who, where, how funded, what Mine Plan, what claims, and the promise to publish everything.

ProofJack Rating: Human 100% · AI 0% (self-estimated; PP-SPEC-079 AI_DISCLOSURE: the phrase 'run the Mine Plan' is the human's)

Also known as: Mine Plan, Engagement Manifest, CMP-1:engagement, incomplete, publication commitment

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

Mine Plan minimums

For each technology profile the control is claimed to serve: at least one Bounded Mode run with White, Gray, Red and Black canaries, and Gold canaries for every applicable Claim Sheet entry.
For a control that is, protects or constrains an agent: at least one Jailed Canary Protocol run with the Escape Test Suite executed.
At least one PP-SPEC-013 measurement window overlapping a Proof Swarm release, so latency, throughput and cost are recorded while the control is doing the work it is credited for. Performance measured on an idle control is not a CMP artifact.
In production or pre-production: a Production Stream commitment of declared minimum duration.
Versioned. Two Engagements compare only on the same composition version.

A run that becomes invalid is published as invalid and the Engagement continues. Fewer valid runs than the minimum produces a Performance Record marked incomplete, which is also published.

Engagement Manifest

Published to the Registry before the first commitment, hashed under the tag CMP-1:engagement and bound to a Time Anchor pulse. It contains:

Engagement identifier, Implementor, Provider, Independent Test Lab, Sponsor, funding tier
Engagement Mode and Environment Class; Parity Declaration hash or Reference Environment
The control: name, version, Control Provenance, Provider, whether Self-Provided, and who captures its fingerprint
The Claim Sheet hash, the Mine Plan and version, the 077 and 078 Interface Manifests
Declared thresholds for every run
The publication commitment: every committed run will be published, including invalid and unfavorable runs
The Registry or Registries and the Holder; the Regulatory Regime set, none stated explicitly
Every extension in use, and the Authorship Disclosure reference of every component

Drift during an Engagement

Every fingerprint is recorded at the start. A change to any of them starts a new segment, must be declared in advance by the party responsible, and is a finding against that party when it is not. The Provider answers for control drift, the Issuer for corpus and profile drift, each seam’s operator for its own harness and pigtail drift, the Implementor or Lab for environment drift. Nobody answers for threat drift; it is measured, not blamed.

Related terms

Sources

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

Updated 2026-10-23