GlossaryOriginSpecs

Glossary

Provider and Control Provenance

In Proof Protocol the Provider is whoever built, maintains, sells or operates the control under test: a commercial vendor, an open source project, a managed service, a cloud platform or an internal team. Control Provenance records which of those it is, commercial, open_source, custom, managed_service, platform_native or configuration, and is never a factor in how the control is tested or compared.

ProofJack Rating: Human 25% · AI 75% (self-estimated; PP-SPEC-079 AI_DISCLOSURE: Provider and Control Provenance terms proposed by Claude)

Also known as: Provider, Control Provenance, vendor, commercial, open_source, custom, managed_service, platform_native, configuration

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

The Provider

The term is deliberately wide. Every rule that constrains the Provider applies to all of them equally: a vendor’s field team and the customer’s own engineers who built a control are both the Provider of that control.

The Provider:

In jail mode the same role is the Agent Provider.

Control Provenance

Value Meaning
commercial A vendor’s product
open_source An open source project
custom Built in house
managed_service Operated by a service provider
platform_native A cloud or platform feature
configuration A configuration of something else

Recorded in every Engagement. Never part of the Comparability Class. A commercial, an open source and a custom control under the same Mine Plan are placed side by side; the provenance is shown so a reader can weight it, and the record does not.

Related terms

Sources

Updated 2026-10-23