Skip to content
Merged
Changes from all commits
Commits
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
20 changes: 20 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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)**.
Expand Down Expand Up @@ -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:
Expand Down
Loading