Record erratum 001 correcting the OAM attribution in the admission contract

[veraxis-protocol]

What this corrects

design/admission-boundary-001/ADMISSION-CONTRACT-v0.1.md states:

A later OCE/runtime stage may compute consequences; OAM/ZTL may constrain operational authority; and VEIP may record or verify execution consequences.

Under the owner disposition of 2026-09-08 (CAT-ALIGN-001B), that attribution is no longer canonical as to OAM. The canonical statement is:

ZTL may constrain what is logically warranted for downstream reliance. VEIP/runtime enforcement may constrain whether an exact action may execute. OAM governs examination/audit disposition and may constrain later institutional reliance on examined results; OAM does not authorize exact runtime execution.

Why it matters

Constraining operational authority and constraining later institutional reliance are different acts on different authority planes — causal versus evidentiary. Collapsing them would let an examination workflow read as a runtime control, which is the authority inflation this contract's own admission boundary exists to prevent.

Why an erratum and not an edit

The predecessor is not touched, for three independent reasons:

1. It is preregistered design evidence carrying its own claim ceiling and NOT SELF-ADJUDICATED marker.
2. Its bytes are digest-pinned: docs/capabilities/CAPABILITY_MATRIX.json records sha256 ad4c656831b679a9396b15a8a9ae32448cf63707711916e4f3a8fa5ed34e8cd2 at source_commit 3fcdec63b7e546d9b369e0e8664d5d67be6a3b54. Editing the file would break that pin.
3. VERSIONING.md requires that admitted artifacts are "never mutated in place; supersede with a new version."

The erratum records predecessor path, blob 1128bdbcc42dc47a355551fa230bab6f7420accc, and SHA-256, so the correction is traceable to exactly what it corrects.

Files changed

• design/admission-boundary-001/ADMISSION-CONTRACT-ERRATUM-001.md — new file, 1 added, 0 modified, 0 deleted

Scope

Corrects the OAM attribution only. Explicitly unchanged: every other semantic in the contract including admission states and the minimum successor bundle; the roles attributed in the same sentence to a later OCE/runtime stage, to ZTL and to VEIP; the predecessor's claim ceiling; docs/capabilities/CAPABILITY_MATRIX.json; and every schema, test vector and runtime behavior under design/admission-boundary-001/.

Claim impact

None. The erratum carries independent_validation_claim = FALSE and NOT SELF-ADJUDICATED, and states that nothing here is designed or implemented in this repository. No status, ceiling, exclusion, benchmark figure or capability-matrix entry is modified. No adoption is asserted for any party.

No runtime change

No code, schema, vector, manifest or test was changed. The diff adds one Markdown file.

Validation

Isolated Python 3.12.3 environment from the hash-locked requirements/dev.txt:

Gate	Result
tests/contract/test_claims_discipline.py	51 passed
ruff check .	All checks passed
ruff format --check .	65 files already formatted
mypy	no issues in 52 source files
make verify	PASS; intentional manifest OVERALL: INCOMPLETE preserved at exit 3
make falsify	4/4
Full suite	1743 passed, 1 declared skip, 0 failed

• Base SHA: c3d986229e2d7874a30a318981f5045e3f793236
• Head SHA: 70966810dcd5f48cfd426272b9e81850ea34cf9b

Provenance

Canonical OAM role: veraxis-protocol/institutional-continuity — THESIS.md §8a and OAM-ROLE-RECONCILIATION.md. Conflict discovered by the CAT-ALIGN-001B census; resolved by owner disposition, not by editorial preference.

Separate from the CAT-ALIGN category-alignment PR set by design.

---

Generated by Claude Code