PACP is cryptographic accountability infrastructure for systems where a missed step can create legal, financial, or human harm. It proves what happened, what didn’t happen, and whether the computation was correct.
No reconstruction. No trust required. No sensitive data stored.
When something goes wrong, organizations reconstruct what happened from logs, timestamps, and human memory. But logs only record what occurred. They are structurally silent about what should have occurred and did not.
PACP reduces accountability to three cryptographic primitives, hash-linked into a single tamper-evident chain. Each proves a different kind of truth.
Cryptographic proof that an action was performed, by whom, witnessed by whom, and when. Signed and chain-linked. Something happened.
Cryptographic proof that a required action did not occur within its expected window. The missing step becomes evidence, not silence. Something didn't happen.
Cryptographic proof that a computation was executed and verified at defined precision. The math was right — or provably wasn't.
Every receipt is dual-signed (Ed25519 + ML-DSA-87 FIPS 204), hash-linked to the obligation that created it, and independently verifiable offline.
Before any action window opens, PACP registers a formal obligation: what is expected, who is responsible, who must witness it, under what policy, and by when. That is what makes a NullReceipt possible. You cannot prove what didn't happen unless you first declared what should have.
This is the Protocol of Obligation — the expectation layer that anchors every receipt and every NullReceipt to a specific duty, actor, observer, and deadline.
Google's quantum roadmap targets roughly one million physical qubits by the end of this decade — enough to break RSA and ECDSA. When that happens, every digital signature, every audit trail, and every compliance record built on standard cryptography becomes retroactively unverifiable. Not breached. Forgeable.
Sources: IBM Cost of a Data Breach Report 2025, Ponemon Institute / GlobalSCAPE, Google Quantum AI Roadmap. Quantum timeline estimates reflect published industry roadmaps and remain subject to engineering progress.
PACP wraps existing systems. It does not replace EHRs, trading platforms, or AI pipelines. It adds a cryptographic accountability layer on top.
PACP can fan a query to six AI models simultaneously, receipt every response, detect every failure, and cross-check every numeric claim against verified ground truth. The result: three separate verdicts, not one green check.
Six model adapters (Claude, GPT-4, Grok, Gemini, Llama, Mistral) · BFT consensus at 2f+1 · Parallel fan-out · Circuit breakers · Retry with backoff · SQLite persistence · Every response receipted · Every failure gets a NullReceipt · Every numeric claim gets a NumericReceipt.
If your system has required steps, required approvals, or required computations — and the cost of a missed step is legal, financial, or human — PACP is built for you. It scales from a single workflow to enterprise-wide deployment across any regulated or trust-critical environment.
PACP did not begin as a cryptography project. It began with a simple human problem: in critical environments, the most dangerous failures are the steps that never happened. After 19 years in cardiac catheterization labs, I had seen too many omissions turn into harm. The system could log what happened. It could not prove what didn’t.
I built PACP because accountability should be structural, not retrospective. Because the people who notice what’s missing are the people who care enough to know what should have been there. And because that instinct — to watch over someone, to hold the expectation, to notice the absence — deserves infrastructure as serious as the duty it represents.
— Andrew Hackett, Founder
6 patents filed. 1,860+ tests passing. Three receipt types. Six-model consensus. Ready for enterprise validation.