Skip to content

CAT-ALIGN-001: align veip-registry with controlling Veraxis category thesis #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
veraxis-protocol merged 2 commits into from
Sep 8, 2026
+17 −0
Merged

CAT-ALIGN-001: align veip-registry with controlling Veraxis category thesis #1

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f91b474
CAT-ALIGN-001: state that a registry does not originate authority
veraxis-protocol Sep 8, 2026
3eead89
CAT-ALIGN-001B: define VEIP on this surface
veraxis-protocol Sep 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,23 @@ 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
**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

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.
Expand Down
Loading