Skip to content

Acceptance Plane v1.0.2-public-eval — Verifiable Action Acceptance Before Impact

Choose a tag to compare

View all tags
@meridianverity meridianverity released this 05 Jul 13:21
v1.0.2-public-eval
ba6c1e0
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Acceptance Plane v1.0.2 — Hardened Public Evaluation

This release provides a hardened public evaluation packet for Acceptance Plane: a synthetic, reviewer-facing framework for evaluating whether an AI-agent or workload output should be accepted before it is relied on, acted on, recorded, or allowed to influence a protected external effect.

The packet is intended for public technical review, reproducible evaluation, and standards-style discussion. It focuses on one narrow question:

Before a system relies on an AI-agent or workload output, can it evaluate whether that output is acceptable, bounded, evidenced, and safe to proceed?

What this release demonstrates

This release exercises a public acceptance-control path:

agent or workload output
→ canonical acceptance input
→ evidence and policy evaluation
→ ACCEPT / HOLD / REFUSE decision
→ proof receipt
→ transparency bundle
→ allow reliance or fail closed before impact

The Acceptance Plane is a category-level control layer. It does not replace downstream authorization systems, gateway controls, action records, attestations, compliance reviews, payment systems, identity systems, or production enforcement layers. Instead, it provides a narrow public evaluation surface for the decision boundary between output and reliance.

Included materials

This release includes:

  • Runnable Acceptance Plane public evaluation.
  • Synthetic acceptance scenarios and test vectors.
  • ACCEPT, HOLD, and REFUSE decision examples.
  • Canonical acceptance input examples.
  • Proof receipt verification path.
  • Transparency bundle verification path.
  • Independent recomputation checks.
  • Schema examples and validation checks.
  • Release gate and strict tree release gate checks.
  • Public manifest and release artifact verification.
  • Reviewer-facing documentation and public-safe scope boundaries.
  • Historical v1.0.0 thesis materials preserved as canonical background assets.
  • Hardened v1.0.2 public-eval release metadata, pointer lock, and upload plan.

Quick start

Run the public evaluation:

python tools/run_public_eval.py

Verify the proof receipt:

python tools/verify_proof_receipt.py

Verify the transparency bundle:

python tools/verify_transparency_bundle.py

Run independent recomputation:

python tools/independent_recompute.py

Verify the release artifact:

python tools/verify_release_artifact.py

Run the full QA path:

make qa-full

Expected hardened release results

Manifest verification:          PASS — 104 files
Public evaluation:              PASS — 64 / 64
Transparency bundle:            PASS
Proof receipt:                  PASS
Independent recomputation:      PASS — 13 / 13
Schema examples:                PASS — 3 examples
Pytest:                         PASS — 11 / 11
Release gate:                   PASS
Strict tree release gate:       PASS
Release artifact verification:  PASS
QA full:                        PASS

Review focus

Reviewers are invited to inspect:

  • whether the Acceptance Plane model is understandable and useful;
  • whether the ACCEPT / HOLD / REFUSE decision structure is clear;
  • whether acceptance inputs are represented in a reproducible way;
  • whether proof receipts are verifiable without private production context;
  • whether transparency-bundle verification is useful for public review;
  • whether negative or uncertain cases fail closed before reliance or impact;
  • whether additional vectors should be added for ambiguity, stale evidence, unsupported profiles, replay, or policy mismatch; and
  • whether future Acceptance Plane work should separate requirements, architecture, data model, proof profile, conformance vectors, and implementation guidance.

Public-safety and scope boundaries

This release contains synthetic public evaluation artifacts only.

It does not process live payments, store payment credentials, call live processors, operate production gateways, make production acceptance decisions, or provide production payment, wallet, issuer, PSP, network-token, settlement-rail, identity, authorization, or compliance infrastructure.

It does not include customer data, production deployment material, non-public implementation mapping, claim charts, evidence-of-use materials, valuation materials, field-of-use analysis, commercial-rights analysis, or confidential information.

This release is not a certification, endorsement, production authorization, license grant, commercial commitment, merged protocol, standards adoption claim, legal or commercial position, valuation request, licensing demand, or patent license grant.

Publication of this packet does not grant any license or commercial rights.

Feedback path

Feedback may be submitted through GitHub Issues or public technical review channels.

Useful feedback includes unclear fields, missing negative vectors, canonicalization edge cases, unsupported profile behavior, replay or freshness questions, proof-receipt verification questions, transparency-bundle review issues, and candidate conformance-vector additions for future Acceptance Plane public-evaluation revisions.

Release asset

acceptance-plane-v1_0_2-public-eval-hardened.zip

SHA-256:

7ab09cad359af97aef20d03dc52edfadcf5deb454e8ed1bddb9bf6cf45ec0444
Assets 4
Loading