From f91b474a2202c1124920cedb1286d6f0c9c7101f Mon Sep 17 00:00:00 2001 From: Arkadiy Miteiko Date: Tue, 8 Sep 2026 22:08:50 +0000 Subject: [PATCH 1/2] CAT-ALIGN-001: state that a registry does not originate authority Add the standard category role block and the registry's authority boundary. A registry stores and serves evidence state. It does not originate the institutional authority represented by that state. A registry that accepted, stored and served a pack perfectly has established custody of evidence, not the legitimacy of the authority that evidence describes. The repository's existing statements that it is not a governance authority and not a centralized global registry are preserved and now have an explicit upstream reason. Documentation only, additive. API surface, ingestion semantics, storage, schema and tests are unchanged. Signed-off-by: Arkadiy Miteiko Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01Pkw68qW3iRaeJsiMPBEPvW --- README.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/README.md b/README.md index 076aebe..718f9be 100644 --- a/README.md +++ b/README.md @@ -8,6 +8,22 @@ It is intentionally compact and transparent. --- +## Role in Open Institutional Computation + +**Category:** Open Institutional Computation +**This component:** Reference intake and retrieval surface for VEIP Evidence Packs — storage and service of evidence state +**Upstream:** Evidence Packs emitted by VEIP implementations, themselves downstream of machine-operational authority/control state 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:** Retrieval by verifiers, examiners and reconciliation processes +**Canonical category thesis:** https://github.com/veraxis-protocol/institutional-continuity/blob/main/THESIS.md + +A registry stores/serves evidence state. It does not originate the institutional authority represented by that state. + +This is why the boundaries stated below matter: a registry that accepted, stored and served a pack perfectly has established custody of evidence, not the legitimacy of the authority that evidence describes. + +Architectural role does not imply production readiness; see "What This Repository Is Not" below for the exact demonstrated scope. + +--- + ## Purpose The VEIP Registry defines the **external intake and retrieval surface** for Evidence Packs. From 3eead890aa1bc81b0736953611f305cb304e457f Mon Sep 17 00:00:00 2001 From: Arkadiy Miteiko Date: Tue, 8 Sep 2026 22:57:50 +0000 Subject: [PATCH 2/2] CAT-ALIGN-001B: define VEIP on this surface Independent evaluators reading this README in isolation reported that VEIP is never expanded or defined here, and that whether VEIP originates institutional authority is therefore 'unstated'. A downstream component that cannot say what the protocol above it does leaves a required category answer unobtainable from the artifact alone. Expand the acronym and state VEIP's role and its three explicit non-roles in the role block. Documentation only, additive. API surface, ingestion semantics, storage and schema unchanged. Signed-off-by: Arkadiy Miteiko Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01Pkw68qW3iRaeJsiMPBEPvW --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 718f9be..2e247eb 100644 --- a/README.md +++ b/README.md @@ -12,6 +12,7 @@ It is intentionally compact and transparent. **Category:** Open Institutional Computation **This component:** Reference intake and retrieval surface for VEIP Evidence Packs — storage and service of evidence state +**VEIP — Veraxis Execution Integrity Protocol:** the execution-integrity and interoperability boundary that binds already-established machine-operational authority/control state to an exact action and runtime disposition, and emits the Evidence Packs this registry stores. VEIP does not interpret governing documents, perform institutional admission, or originate institutional authority. **Upstream:** Evidence Packs emitted by VEIP implementations, themselves downstream of machine-operational authority/control state 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:** Retrieval by verifiers, examiners and reconciliation processes **Canonical category thesis:** https://github.com/veraxis-protocol/institutional-continuity/blob/main/THESIS.md