CAT-ALIGN-001: align Institutional-Compiler with controlling Veraxis category thesis - #44
Open
veraxis-protocol wants to merge 1 commit into
Open
CAT-ALIGN-001: align Institutional-Compiler with controlling Veraxis category thesis#44veraxis-protocol wants to merge 1 commit into
veraxis-protocol wants to merge 1 commit into
Conversation
Add a category role section near the top of the README naming the field, the upstream institutional-compilation problem OIC addresses, and the boundary that institutional authority remains externally constituted: machine extraction may propose meaning, and authorized institutional admission is required before meaning is admitted. OIC operates upstream of VEIP and runtime enforcement. The section states an architectural role, not a capability. It says so explicitly and defers to README status text, STATUS.md, CLAIMS.md and the capability matrix for the exact demonstrated scope. No status, ceiling, exclusion, benchmark figure, validation history or measured evidence is modified. Documentation only, additive. Signed-off-by: Arkadiy Miteiko <am@veraxis.io> Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Pkw68qW3iRaeJsiMPBEPvW
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope
Documentation only, additive. One section added to
README.mdimmediately below the DOI badge. Nothing is removed, reworded, or reordered.Files changed (1 modified):
README.md— 23 insertions, 0 deletionsWhy
OIC is the upstream component in the Veraxis architecture, but the README opens on status, bootstrap date and governing design and never names the field OIC sits in. Downstream surfaces — the VEIP family in particular — are much easier for an external reader to place, which inverts the actual dependency: readers recognize the evidence artifacts and miss the institutional-authority computation that gives those artifacts meaning.
The added section names the category and states the boundary that matters most for this repository:
Claim impact — none
This is the sensitive part of this PR, so it is stated precisely.
The section is explicitly marked as an architectural role rather than a capability claim, and it defers by name to the README's own status text,
STATUS.md,CLAIMS.mdanddocs/capabilities/CAPABILITY_MATRIX.jsonfor the exact demonstrated scope.Unchanged and unweakened:
BOUNDED_REFERENCE_IMPLEMENTATIONstatus line and its independent-review scopingTARGET - NOT MEASURED; comparative target:PROVISIONAL TARGET - NOT MEASURED - NOT CALIBRATEDSTATUS.md,CLAIMS.md,LIMITATIONS.md, capability matrix, benchmark evidence, validation history — all untouchedNothing asserts that OIC currently performs production institutional compilation or runtime authorization. No enterprise adoption is asserted for any party. No implementation maturity claim is broadened.
No runtime change
No runtime semantics, code, schema, test, expected behavior, manifest, benchmark, historical artifact or release was changed.
git statusshows exactly one modified file.Validation
Full canonical Linux run in an isolated Python 3.12.3 environment installed from the hash-locked
requirements/dev.txt, with import provenance bound to this checkout:tests/contract/test_claims_discipline.pyruff check .ruff format --check .mypymake verifyOVERALL: INCOMPLETEpreserved at exit 3make falsifyThe declared skip is
tests/contract/test_canada_acquisition_preflight.py:574(gitignored local receipts intentionally unavailable in CI), matching the established baseline.The claims-discipline contract is the control that would catch an unscoped or widened claim in this file. It passes unchanged at 51.
c3d986229e2d7874a30a318981f5045e3f7932365a7813b6488f7568f0379afedfe0d73996c85634Controlling 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
Per that thesis, this repository keeps its own implementation scope, status, interfaces and claim ceilings; only its architectural role is inherited.
Attribution
Executed under owner work order CAT-ALIGN-001. Not an independent review.
Generated by Claude Code