VEIP Open Protocol
New upload
Records Members Curation policy About

VEIP Open Protocol

The Veraxis Execution Integrity Protocol (VEIP) is an open protocol for representing, binding, transporting, and independently verifying evidence associated with consequential machine execution.

VEIP addresses a recurring architectural boundary in institutional AI: an execution system may correctly authenticate an actor, apply a policy, enforce a decision, and preserve an audit trace while remaining unable to establish the institutional legitimacy of every premise it consumes.

Those premises may concern:

  • normative and policy authority;
  • delegated authority and identity lineage;
  • evidence provenance and sufficiency;
  • jurisdiction and institutional purpose;
  • temporal validity and revocation;
  • action and consequence scope;
  • conditions governing downstream reliance.

VEIP provides a structured means of making those externally grounded conditions computationally cognizable without treating the execution system as the source of their legal, factual, or institutional legitimacy.

Purpose of this community

The VEIP Open Protocol community is the canonical, citable archive for the public development and stewardship record of VEIP.

The community preserves:

  • normative protocol specifications and profiles;
  • schemas, test vectors, and formal invariants;
  • reference implementations and verification tooling;
  • candidate conformance requirements and reports;
  • implementation and interoperability records;
  • reproducible experiments and research foundations;
  • legal-computational analysis;
  • security reviews, criticisms, and counterexamples;
  • protocol governance and stewardship records.

GitHub remains the active engineering environment for source development, issues, pull requests, technical discussion, and change proposals.

Zenodo preserves the versioned and citable record of released protocol artifacts.

GitHub records how VEIP changes. Zenodo records what VEIP officially was.

Protocol status

VEIP is currently published as a Public Working Draft.

A Public Working Draft is available for implementation, evaluation, criticism, and revision. It is not:

  • a formal international standard;
  • a regulatory approval;
  • a security certification;
  • a legal determination;
  • evidence of industry consensus;
  • evidence of adoption or endorsement by any organization unless expressly documented.

Every record accepted into this community must state its own status and relationship to the protocol.

Recognized record statuses include:

  • Canonical Release
  • Candidate Specification
  • Experimental Profile
  • Reference Implementation
  • Implementation Report
  • Candidate Conformance Report
  • Research Foundation
  • Historical or Superseded Record
  • Withdrawn Record

Foundational distinctions

VEIP is developed around several architectural distinctions:

  • computational correctness is not institutional validity;
  • authorization is not runtime admissibility;
  • authentication is not authority;
  • attestation is not institutional grounding;
  • execution is not consequence;
  • consequence is not downstream reliance.

VEIP does not manufacture institutional truth.

It preserves and communicates the provenance, scope, context, temporal validity, and reliance conditions of externally grounded claims when those claims are consumed by computational systems.

The protocol is intended to support the continuity chain:

External grounding → computational representation → runtime binding → execution enforcement → consequence verification → downstream reliance

Stewardship

The Veraxis Research Group (VRG) serves as the founding steward of the VEIP open protocol.

Stewardship means preserving:

  • technical coherence;
  • interoperability;
  • inspectability;
  • accurate versioning;
  • public change records;
  • disciplined attribution;
  • reproducibility;
  • independent implementation;
  • meaningful criticism and correction.

Stewardship does not confer exclusive ownership of Institutional Computation, make VRG the sole source of institutional legitimacy, or prevent compatible, competing, or alternative implementations.

The long-term objective is an ecosystem in which independent implementers, institutions, cloud platforms, researchers, legal scholars, auditors, and standards participants can evaluate, implement, challenge, and extend the shared protocol layer.

As the ecosystem matures, protocol review and conformance governance should become progressively more distributed and independent.

Open participation

The community accepts technically and legally substantive contributions concerning:

  • protocol specification;
  • implementation;
  • verification;
  • interoperability;
  • formal analysis;
  • institutional application;
  • legal classification;
  • security;
  • conformance;
  • criticism;
  • competing models;
  • counterexamples.

Agreement with VRG is not a condition of acceptance.

Acceptance into the community means that a record falls within scope and satisfies the published requirements for attribution, version clarity, inspectability, disclosure, and technical or legal substance.

Acceptance does not constitute certification, endorsement, legal approval, regulatory recognition, or confirmation that every substantive claim in the record is correct.

Canonical engineering sources

GitHub organization:
https://github.com/veraxis-protocol

VEIP specification repository:
https://github.com/veraxis-protocol/veip-spec

Contact

Veraxis Research Group
am@veraxis.io

Subjects