From 6d1d65e77868a8a0516cff0cf9513785e15dd6c9 Mon Sep 17 00:00:00 2001 From: Arkadiy Miteiko Date: Tue, 8 Sep 2026 22:07:03 +0000 Subject: [PATCH] CAT-ALIGN-001: state the VEIP SDK's upstream boundary Add the standard category role block and an explicit upstream-boundary section immediately before the Architecture Model. The SDK's architecture model previously began at "AI System -> Action Proposal -> VEIP Authorization Gate", with no statement of what must already be true upstream. That lets a reader conclude the SDK establishes the authority it enforces. It does not: an authority envelope is an input, and a schema-valid Evidence Pack records a binding rather than proving the upstream institutional authority was legitimate, correctly interpreted, properly admitted or currently applicable. OIC is the reference path for that problem. Documentation only, additive. No implementation names, code, schema, tests or version bindings changed. 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 59d1fba..24c56ac 100644 --- a/README.md +++ b/README.md @@ -4,6 +4,18 @@ MIT Reference Implementation of the Veraxis Execution Integrity Protocol (VEIP) --- +## Role in Open Institutional Computation + +**Category:** Open Institutional Computation +**This component:** Reference implementation of the VEIP execution-integrity boundary — deterministic classification of a proposed action against supplied authority, and emission of a schema-valid Evidence Pack +**Upstream:** Machine-operational authority/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:** Evidence Packs consumed by replay validation, the VEIP Verifier Core, 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 "What This Repository Is Not" and "Early Production-Grade Posture" below for the exact demonstrated scope. + +--- + ## Executive Summary The VEIP SDK is a minimal, production-structured reference implementation of the **Veraxis Execution Integrity Protocol (VEIP)**. @@ -100,6 +112,14 @@ Certification and authoritative validation are governed separately through the V --- +## Upstream Boundary + +The SDK begins at a boundary where machine-operational authority/control inputs have already been supplied. It does not establish whether the original human governing source was interpreted or admitted correctly. The upstream reference path for that problem is OIC. + +An authority envelope supplied to this SDK is an *input*. The SDK binds and classifies against it; it does not originate the institutional authority that envelope represents, and a schema-valid Evidence Pack records that binding rather than proving the upstream authority was legitimate, correctly interpreted, properly admitted, or currently applicable. + +--- + ## Architecture Model The SDK illustrates the VEIP execution control-plane: