From 26db2538f1913637a242b0730de6866f5943b408 Mon Sep 17 00:00:00 2001 From: Arkadiy Miteiko Date: Tue, 8 Sep 2026 22:05:59 +0000 Subject: [PATCH] CAT-ALIGN-001: position VEIP within Open Institutional Computation Add the standard category role block and an explicit architectural-position statement so the specification cannot be read as originating institutional authority or as being defined by its Evidence Pack artifact. VEIP consumes machine-operational authority or control state established upstream and binds it to an exact action, runtime classification, execution transition and verifiable evidence. It does not interpret governing documents as institutional truth, perform institutional admission, or originate institutional authority. OIC is the Veraxis reference path for that upstream problem. An Evidence Pack / AEP is a downstream artifact, not VEIP itself. Documentation only, additive. Normative specification, scope, licensing, schemas, invariants and versioning are unchanged. Existing "Evidence Pack" schema terminology is preserved. Signed-off-by: Arkadiy Miteiko Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01Pkw68qW3iRaeJsiMPBEPvW --- README.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/README.md b/README.md index 0c0d194..ed72e5c 100644 --- a/README.md +++ b/README.md @@ -10,6 +10,16 @@ # Veraxis Execution Integrity Protocol (VEIP) Specification +## Role in Open Institutional Computation + +**Category:** Open Institutional Computation +**This component:** Normative execution-integrity protocol specification — the runtime boundary at which established machine-operational authority/control state is bound to an exact action and to verifiable evidence +**Upstream:** Machine-operational authority or control state, already established through authorized institutional interpretation and admission (the Veraxis reference path for that upstream problem is [OIC — Open Institutional Compiler](https://github.com/veraxis-protocol/Institutional-Compiler)) +**Downstream:** Conformant implementations, supervisory verification, and Evidence Packs consumed by verifiers, registries, and enforcement runtimes +**Canonical category thesis:** https://github.com/veraxis-protocol/institutional-continuity/blob/main/THESIS.md + +Architectural role does not imply production readiness; see this repository's status, versioning, and conformance documentation for the exact demonstrated scope. + ## Overview The Veraxis Execution Integrity Protocol (VEIP) defines a deterministic execution-control standard for AI and automated systems. @@ -26,6 +36,16 @@ VEIP is an open specification. This repository contains the normative standard documents and JSON schemas that define VEIP behavior. +### VEIP's position in the architecture + +VEIP is the execution-integrity protocol within Open Institutional Computation. It consumes machine-operational authority or control state established upstream and binds/preserves that state across the boundary to an exact proposed action, runtime classification, execution transition, and verifiable evidence. + +VEIP does not determine the institutional meaning of governing documents, perform institutional admission, or originate institutional authority. + +OIC provides the Veraxis reference path for the upstream institutional compilation problem. + +An Evidence Pack / Authorization Evidence Pack is a downstream evidence artifact used by the architecture. It is not VEIP itself and does not create the authority it records. + ## Foundational Invariants 1. Execution Authorization Precedes Action.