Skip to content
View meridianverity's full-sized avatar

Block or report meridianverity

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
meridianverity/README.md

Meridian Verity — Before AI acts, prove the exact action.

The acceptance layer between AI proposal and real-world effect.
Meridian Verity binds current authority and evidence to the complete exact action at the last reversible moment—then returns ACCEPT, HOLD, or REFUSE and preserves a replayable receipt.

RUN THE PUBLIC MODEL   ·   VERIFY PUBLIC EVIDENCE   ·   REVIEW THE ARCHITECTURE   ·   ENTERPRISE DILIGENCE

15 SEC 60 SEC 5 MIN 30 MIN
See one changed field stop an effect Verify the declared public state Run a reproducible public artifact Route an enterprise review

One control question

Does current authority still permit this complete exact action—right now?

Identity establishes the actor. Authorization establishes scope. Acceptance resolves whether the exact effect may happen now. Meridian Verity builds the Acceptance Plane™, a dual-gate architecture for consequential AI actions.

Control moment What it decides
G0 · Request gate Whether the actor, request, policy context, and evidence may form a protected action.
A-01 · Complete exact action The actor, target, parameters, destination, consequence, nonce, validity window, and active policy remain bound as one review object.
G1 · Effect gate Whether current authority still matches that exact action at the effect owner’s last reversible boundary.
Receipt + replay The decision, reason, evidence route, outcome, and consumption state remain reviewable.

Protected action classes: Move money · Expose data · Change records · Trigger workflows · Touch infrastructure · Affect people

Public evidence you can challenge

Meridian Verity separates first-party reproducibility from independent validation instead of compressing both into one assurance badge.

500 3 13 0
Digest-sealed OAC vectors First-party reference engines Issued U.S. records Independent organizations currently registered

Run the Open Acceptance Challenge · Inspect the Public Proof Graph · Open the Trust Center

Public reference work

Repository Review surface Fast path Declared public result
acceptance-plane Category architecture, exact-action workflow, schemas, receipts, and bounded public evaluation make qa-full 64 / 64 public-eval cases; 13 / 13 separate recomputation checks
permit-receipt Canonical action binding, policy epoch, freshness, revocation, anti-replay, and fail-closed PermitReceipt evaluation make ietf-preflight 76 / 76 vectors; 323 / 323 strict tests in the current public-evaluation release
haltseal One protected gateway boundary with freshness, continuity, replay, malformed-input, and proof-receipt checks python tools/run_public_eval.py 32 / 32 synthetic public-evaluation cases
acceptance-plane-public-readiness-kit Board → buyer → builder readiness, procurement language, browser demo, and scenario-card tooling make demo 300 public scenarios; no API keys, services, or package install

These are public, synthetic, first-party evaluation surfaces. Each repository states its own version, license, threat boundary, exclusions, and reproduction path.

Standards and public record

Action Acceptance is the public standards program. The current candidate is AAP-1.0.1 / AAP-1-INTEROP-0.2: 24 mandatory PermitReceipt fields, 20 core predicates, Level 0 document-only current-profile evidence, and no independent v0.2 implementation presently reported.

The PermitReceipt work also has a related individual IETF Internet-Draft. It is a work in progress—not an IETF standard or IETF endorsement.

Research & technical record · IP & Patent Record · Public boundary

Built for decisions that cross the room

A consequential action should move from product to architecture, security, counsel, and procurement without losing the exact question, the evidence boundary, or the accountable owner.

EXECUTIVE BRIEF   ·   SECURITY & TRUST   ·   FRAME ONE BOUNDARY   ·   START AN EVALUATION

One action. One owner. One first stop condition.

Public boundary

Public materials support architecture review, reproducibility, standards discussion, procurement, and public record. They do not claim production deployment, certification, external endorsement, compatibility, legal conclusion, implementation authorization, or patent/license rights by publication. Independent evidence remains explicit; production authority, implementation rights, deployment scope, and commercial terms require written agreement.


Meridian Verity Group LLC
Proof before consequence.

Website · Research · Press · Contact

Popular repositories Loading

  1. acceptance-plane acceptance-plane Public

    Public architecture thesis and reference workflow for the Acceptance Plane in agentic AI infrastructure.

    Python

  2. acceptance-plane-public-readiness-kit acceptance-plane-public-readiness-kit Public

    Free public readiness kit for discussing action acceptance before impact, with a 5-minute educational scenario-card linter. Not an implementation, standard, certification kit, or patent license.

    HTML

  3. permit-receipt permit-receipt Public

    Public synthetic reference evaluation for ORPRG PermitReceipt permit-before-commit authorization of AI-agent and workload protected external effects, with canonical request digests, fail-closed neg…

    Python

  4. haltseal haltseal Public

    Public-safe synthetic proof pack for fail-closed permit-before-action runtime control at one AI-agent gateway.

    Python

  5. meridianverity meridianverity Public

    Institutional profile and public verification map for Meridian Verity’s proof-before-consequence infrastructure.