CAT-ALIGN-001: align veip-sdk with controlling Veraxis category thesis

[veraxis-protocol]

Scope

Documentation only, additive. README.md gains two sections; nothing is removed or reworded.

1. A standard Role in Open Institutional Computation block directly under the title.
2. An Upstream Boundary section placed immediately before the Architecture Model.

Why

The README's architecture model begins at AI System → Action Proposal → VEIP Authorization Gate → Deterministic Classification → Execution → Evidence Pack Emission. Everything in that chain is accurate, but the chain starts at the gate, so nothing on the page says what must already be true upstream. A reader — or an AI summarizing this repository — can reasonably conclude that the SDK establishes the authority it enforces, and that the Evidence Pack is the point of the system.

Neither is true. The added section states the boundary directly:

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.

and makes the envelope's status explicit: an authority envelope is an input; the SDK binds and classifies against it and does not originate the institutional authority it represents. A schema-valid Evidence Pack records that binding rather than proving upstream authority was legitimate, correctly interpreted, properly admitted, or currently applicable.

Files changed

• README.md — 20 insertions, 0 deletions

What is explicitly preserved

• Executive Summary and the "not a certification engine" statement
• The three deterministic design principles, verbatim
• Specification binding, schema SHA-256 pinning and version-matching description
• "What This Repository Is" / "What This Repository Is Not", both untouched
• "Early Production-Grade Posture" and its explicit out-of-scope list
• MIT licensing, trademark position, contribution invariants, disclaimer

No implementation name, class, function, module, schema field or test was renamed or touched. Per the work order, implementation names and tests are changed only where documentation is demonstrably inconsistent with code; no such inconsistency was found.

Claim impact

None. The role block carries its own qualifier pointing at the repository's existing scope sections. No conformance, certification, maturity, adoption or deployment claim is made or broadened. No enterprise adoption is asserted for any party.

No runtime change

No runtime semantics, code, schema, test, expected disposition or version binding was changed. The diff touches one Markdown file.

Validation

• make check (the gate CI actually runs, per .github/workflows/ci.yml) → OK: Python syntax checks passed, exit 0, both before and after the change.

• make ci additionally runs pytest; the test suite could not be executed in this environment because pytest is not installed and the package is not pip-installed here. This is an environment limitation, not a repository failure, and it is disclosed rather than worked around. The change adds no Python, so no test outcome can be affected by it.

• Base SHA: 40bcb5708c8e3aadcb0e31d3190824ddc33f8fce

• Head SHA: 6d1d65e77868a8a0516cff0cf9513785e15dd6c9

Controlling thesis

veraxis-protocol/institutional-continuity#2 — Veraxis Category Thesis v1.0. Canonical location after merge: https://github.com/veraxis-protocol/institutional-continuity/blob/main/THESIS.md

DCO

Commit is signed off.

---

Generated by Claude Code