SEDCPH
Patent pending. U.S. App. No. 19/546,587

Nothing leaves until its integrity is proven again.

SEDCPH is the single exit door for artifacts. On intake it converts data to a canonical form and records a cryptographic hash. Before any export, it re-reads the stored bytes, recomputes the hash, and releases the artifact only if it still matches. If even one byte changed, the artifact is FAILED, and a FAILED artifact can never return to VERIFIED.

Run the live demo See how it works
Patent pendingU.S. Utility Application No. 19/546,587
ArchitectureCanonicalize, hash, re-verify at export, single enforced chokepoint
Veteran-ownedOperated by a Service-Disabled Veteran-Owned Small Business
Research baseFounder is a Florida International University DBA candidate
Based inDoral, Florida (Greater Miami)
The mechanism

One door. Checked on the way in, and again on the way out.

A standardization step removes false alarms from formatting differences; re-verification at export removes silent corruption and tampering.

01
Canonicalize
Convert data to a deterministic standard form (for JSON: sorted keys, no extra whitespace, UTF-8).
02
Hash and store
Record a cryptographic hash of the canonical bytes at intake. State becomes PENDING.
03
Re-verify
Before export, re-read and re-hash. Match becomes VERIFIED; mismatch becomes FAILED, which is irreversible.
04
Gate the exit
Only VERIFIED artifacts can be exported, through one enforced chokepoint with a final re-check.
Why it matters

Proof that what leaves is what was stored.

Single enforced exit

One chokepoint serves artifacts. No alternate endpoint or direct link delivers content around it.

Irreversible failure

FAILED cannot transition back to VERIFIED. A compromised artifact must be re-ingested from source.

Canonical by design

Standardizing bytes first removes false integrity alarms caused by formatting differences alone.

In your browser

Intake an artifact, verify it, then try to sneak a change past the gate.

This demo is real: it canonicalizes your JSON, hashes it with the Web Crypto API (SHA-256), and re-verifies on export. It runs entirely on this page and is not the production service.

Artifact NO ARTIFACT

Event log:
"Reorder keys only" shows canonicalization treating logically identical data as VERIFIED. "Tamper" changes a value and is caught as FAILED.

Illustration only. It omits production controls such as storage-bucket IAM, the canonicalization-profile self-hash, and the deployment bypass scan.

Provenance

What is verifiable today.

Stated without embellishment.

Patent status
U.S. utility application pending. Application No. 19/546,587. A patent has not been granted; "patent pending" denotes a filed application only.
Architecture
Deterministic canonicalization, hash-on-intake, re-verification at export, irreversible FAILED state, single enforced export chokepoint, as described in the application.
Ownership
Intellectual property held by Deterministic Governance LLC; operated under license by FORGE LINK LLC (SDVOSB).
Founder
U.S. Marine Corps veteran; Doctor of Business Administration candidate, Florida International University.
The family

Part of a layered governance stack.

Three standalone patent-pending systems, each enforcing a different boundary, all under Deterministic Governance LLC.

PACDMGSAdmission control: evaluates AI outputs and issues a signed decision token before any action. PM_DECABSMutation boundary: governs every change to authoritative state through bounded, audited epochs. Deterministic GovernanceThe parent company and hub for all three systems.
Contact

Talk to the team.

For technical evaluation, licensing, or pilot inquiries.

ops@deterministicgovernance.com