Skip to content

CAT-ALIGN-001: align veip-verifier-core 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 3 commits into from
Sep 8, 2026
Merged

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

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6df68f5
CAT-ALIGN-001: bound what a Verifier Core PASS establishes
veraxis-protocol Sep 8, 2026
02eff93
CAT-ALIGN-001B: narrow what a valid Evidence Pack establishes
veraxis-protocol Sep 8, 2026
0019f51
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
19 changes: 19 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,25 @@ This repository defines the verification surface. It does not define certificati

---

## Role in Open Institutional Computation

**Category:** Open Institutional Computation
**This component:** Reference verification engine for the structural and integrity properties of a VEIP Evidence Pack
**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 verifier checks. VEIP does not interpret governing documents, perform institutional admission, or originate institutional authority.
**Upstream:** An Evidence Pack already emitted by a VEIP implementation, itself 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:** Machine-readable PASS/FAIL verification outcomes for local, CI, registry and examination use
**Canonical category thesis:** https://github.com/veraxis-protocol/institutional-continuity/blob/main/THESIS.md

### What a PASS does and does not establish

This verifier verifies the structural/integrity properties of a downstream VEIP Evidence Pack. A PASS does not by itself establish that upstream institutional authority was legitimate, correctly interpreted, properly admitted, or currently applicable unless those properties are themselves covered by the verified inputs/profile.

A cryptographically valid Evidence Pack establishes only the bounded cryptographic and structural integrity properties actually verified under the applicable schema/profile. It does not by itself establish truth, completeness, institutional validity, correct upstream interpretation, consequence occurrence, or observation coverage. It is evidence *about* a binding: not the origin of the institutional authority it records, and not a certificate of its own upstream validity.

Architectural role does not imply production readiness; see "What this repository is not", "Security Model (Minimal Scope)" and "Status" below for the exact demonstrated scope.

---

## Purpose

The Verifier Core provides:
Expand Down
Loading