ProofProtocol™
Proof Protocol / PP-SPEC-093-PROOF-OF-STATE

Proof of State

Ownership and Attribution Notice

Proof of State (PP-SPEC-093) is authored by Craig Thomas Ellrod and is published as part of Proof Protocol. Copyright (c) 2026 Craig Thomas Ellrod.

Any use, implementation, derivative, citation, or incorporation of this specification, in whole or in part, MUST attribute Craig Thomas Ellrod and Proof Protocol. This requirement applies to standards bodies, working groups, consortia, and commercial implementations.

Licensed under the Proof Protocol License 1.1 (see LICENSE.md); text CC BY 4.0 under Part A, which grants no patent rights. Original inventor: Craig Thomas Ellrod (ORCID 0009-0004-1058-7666).

Patents. Patent terms are in PATENT-SCHEDULE.md. Claims not listed there are reserved by Craig Thomas Ellrod. Licensing: 1proofprotocol@gmail.com.


Is the control in production the same control that was proven?

A proof of last month's configuration says nothing about today's.

Proof of State is the claim that a deployed control is in the same state as the control a proof was produced against: its DUT Fingerprint (version, configuration, policy, rule and signature sets and, for AI controls, model identifier, system prompt and tool permissions), captured independently of the Provider in production, equals the fingerprint bound to the proof. It is what lets a buyer carry a proof from the test into production.

How it works

  1. Declare first. The claim, its subject, scope and limits are registered and anchored before the evidence they are measured against is produced.
  2. Evidence from the family. The claim is determined only from Conformant, registered Proof Protocol records: - Proven State - Production Captures
  3. Determine mechanically. Exactly one of proven, refuted or insufficient, computed the same way by a person and a machine.
  4. Publish everything. Every Determination is registered, whatever its result.
  5. Expire honestly. A changed control, a revoked basis record, or the end of the declared period ends the claim.

Part of the Proof of X family

Only Proof of Efficacy answers whether a control worked. Proof of State answers one other question a reader needs answered. See SPEC.md Section 11 for the whole family, PP-SPEC-082, PP-SPEC-089 to PP-SPEC-099 and PP-SPEC-101.

Repository

Path Contents
SPEC.md The normative specification, PP-SPEC-093
docs/overview.md Plain-English walkthrough
docs/glossary.md Terms
docs/conformance.md Conformance checklist
schemas/state-claim.schema.json Claim Declaration and Claim Record schemas
schemas/ai-disclosure.schema.json Authorship Disclosure schema (077 21.15)
CHANGELOG.md Version history
CONTRIBUTING.md How to engage
GOVERNANCE.md How this specification is governed
NOTICE.md Attribution requirements
AI_DISCLOSURE.md What was human-authored and what was AI-drafted
FUNDING.md Funding disclosure
REVIEWERS.md Review disclosure
ACKNOWLEDGEMENTS.md Credits
ETHICS.md Proof Economy Code of Ethics
CITATION.cff Citation metadata
SECURITY.md Reporting protocol flaws
PATENT-SCHEDULE.md Patent terms
LICENSE.md License terms
LICENSE-CC-BY-4.0.md CC BY 4.0, specification text
LICENSE-APACHE-2.0.md Apache License 2.0, reference text

Status

Draft, version 0.1.0, 2026-11-04. Maintained by Craig Thomas Ellrod as part of Proof Protocol.

Builds on PP-SPEC-077 (Dead Canary), PP-SPEC-081 (Reproof). Records are registered to a PP-SPEC-004 registry; the public instance is proofregister.com.

Glossary: Proof of State. Specifications: proofprotocol.io.

Archived on Zenodo: pending.

Related: Proof Economy Prior Art Declaration, DOI 10.5281/zenodo.21379780.

Cite

Ellrod, C. (2026). Proof of State (PP-SPEC-093), v0.1.0.
Craig Thomas Ellrod, Proof Protocol. https://github.com/proofprotocol/PP-SPEC-093-PROOF-OF-STATE
View source on GitHub