PACDMGS
Patent pending · U.S. App. No. 19/544,983

Make AI prove a decision met policy, before it acts.

PACDMGS is an admission-control layer for automated decisions. When an AI system reaches a consequential decision, PACDMGS either issues a cryptographically signed decision token attesting the decision met an explicit policy and sufficiency threshold, or it escalates to a human. No token, no action.

Patent pendingU.S. Utility Application No. 19/544,983
Tested260 automated tests · PostgreSQL 16 · ECDSA P-256
Veteran-ownedOperated by a Service-Disabled Veteran-Owned Small Business (SDVOSB)
Research baseFounder is a Florida International University DBA candidate
Based inDoral, Florida (Greater Miami)
The mechanism

A decision is admitted only if it can be proven.

PACDMGS sits between a model's output and any action taken on it. It evaluates the decision against a named policy and a sufficiency threshold, then produces a verifiable, tamper-evident record. It is decision-domain neutral: it governs whether a decision met policy, independent of what the decision is about.

01
Evaluate
Score the decision against a named policy and sufficiency threshold.
02
Admit or escalate
Meets threshold → admit. Below threshold, or escalation-only → route to a human.
03
Sign
On admit, issue a signed decision token binding the decision to its policy, model, and output.
04
Verify
Any party can verify the signature. Altering any bound field invalidates the token.
Why it matters

Accountability that travels with the decision.

Tamper-evident by construction

The token binds the decision's key fields under one signature. Change a field, and verification fails, demonstrated in the demo below.

Fails closed

If the sufficiency threshold is not met, no token is issued and the decision is escalated rather than acted upon.

Human override is explicit

An escalation-only condition forces a human decision path; the system cannot self-authorize past it.

Where it applies

Any decision that must be provably within policy before it acts.

The pattern is the same across industries: an automated or AI-driven system reaches a consequential, hard-to-reverse decision, and someone later has to prove it was authorized. PACDMGS sits at that boundary. Before the action executes it either issues a signed authorization or escalates to a human, and every authorization stays independently verifiable and tamper-evident for as long as the record is kept.

Financial services

Authorizing a disbursement, trade, or credit decision, or gating an AML or KYC step, before money moves. The authorization travels with the transaction for audit.

Healthcare and insurance

Gating an automated coverage, claims, or clinical-support decision before an order or payment executes, with a verifiable record for each one.

Regulated AI and compliance

Proving an AI system's action met an explicit policy before it takes effect, so auditors and regulators can check the decision rather than trust it.

Government and public sector

Enforcing authorization boundaries where an automated action must be provably within policy, with attestations a reviewer can verify independently.

Critical infrastructure and operations

Admitting a state change or control action only when it carries a valid, signed policy attestation, and escalating to a person otherwise.

Agentic software workflows

Wherever software agents chain actions, PACDMGS is the checkpoint that decides whether the next consequential step is admitted, escalated, or refused.

Illustrative applications, not customer claims. PACDMGS governs the decision boundary itself, so it carries across any domain where an action must be authorized before it happens.

Live, in your browser

Issue a token. Then try to forge one.

This runs entirely in your browser using the Web Crypto API (ECDSA P-256). A fresh key pair is generated on this page; nothing is sent anywhere. It mirrors the system's signed-token behavior and its tamper checks.

1 · Decision inputs

Try score below threshold, or tick escalation-only, to see it refuse to issue a token.

2 · Decision token & verification

No token yet. Evaluate a decision that meets policy.

Demonstration only. It illustrates the signing and verification behavior; it is not the production service and omits server-side controls such as nonce/replay handling and the audit store.

Provenance

What is verifiable today.

These are facts a reviewer can check, stated without embellishment.

Patent status
U.S. utility application pending. Application No. 19/544,983. A patent has not been granted; "patent pending" denotes a filed application only.
Testing
260 automated tests pass against PostgreSQL 16, including signed-token integrity and tamper-rejection across every signed field and the signature itself; each single-field mutation is rejected. An independent verifier reproduces the result outside the issuing service.
Cryptography
ECDSA over NIST P-256; a fixed-field signed decision token.
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.
Contact

Talk to the team.

For technical evaluation, partnership, or pilot inquiries.

ops@deterministicgovernance.com