CAT-ALIGN-001: align institutional-continuity with controlling Veraxis category thesis - #2
Merged
Merged
Conversation
Establish THESIS.md as the owner-authorized controlling category source for Veraxis public surfaces, and add the manual category-perception gate it references. The category is Open Institutional Computation. The central missing computation is institutional authority computation. OIC is the upstream institutional compilation component; VEIP is the downstream execution-integrity boundary; an Evidence Pack / AEP is a downstream artifact, not the category; enforcement runtimes are consumers, not origins of institutional authority; ICI is a reference end-to-end continuity architecture within the field, not a competing parent category. Documentation only. No runtime, schema, benchmark, claim-ceiling or normative specification change. Role statements are architecture statements; repository STATUS, CLAIMS.md, capability matrices and validation scope continue to govern what may be claimed. 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 was referenced Sep 8, 2026
CAT-ALIGN-001: align veip-spec with controlling Veraxis category thesis
veraxis-protocol/veip-spec#1
Merged
Merged
The README badge read "Category: ICI", which positions Institutional Continuity Infrastructure as the parent category. Under the controlling category thesis the field is Open Institutional Computation and ICI is a reference end-to-end continuity architecture within it. Replace the category badge with a field badge and an architecture badge, and add a short placement section stating the hierarchy, the field's central missing computation, where OIC and VEIP sit, and that an Evidence Pack is a downstream artifact rather than a source of authority. ICI's full-chain model, nine-node canonical chain, eight joins, invariants, ICTS methodology and claim ceilings are unchanged and unweakened. No normative specification is modified: spec/CATEGORY-CONSTITUTION.md is still titled "ICI Category Constitution" and reconciling that title is a normative change requiring a successor artifact under spec/CHANGE-CONTROL.md. 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 was referenced Sep 8, 2026
Record the full repository census (14 censused, 10 modified, 4 not modified), the per-repository execution record with base and head SHAs and validation results, and the veraxis.io category patch prepared for later application. The website source could not be identified: no reachable repository contains any site source or Pages deployment workflow, and the live site is unreachable from the executing environment under the network egress policy. Rather than fabricate current copy or modify an unrelated repository, the patch document records exact proposed copy, the required architecture sequence, the claim constraints binding whoever applies it, and leaves current copy explicitly blank. Known remaining inconsistencies are recorded rather than silently fixed, including that spec/CATEGORY-CONSTITUTION.md still titles ICI a category. Changing it is a material normative change requiring a successor artifact under spec/CHANGE-CONTROL.md, so it is left for owner decision. 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
CI on the MAM alignment PR failed with "cannot compile Go 1.22 code". Root cause is on the base branch, not in the change: go.mod declares go 1.22 while the workflow pins go-version 1.20. The alignment diff there is one Markdown file and touches no Go, no go.mod and no workflow. Recorded as a remaining known inconsistency rather than fixed, since a workflow toolchain bump is not category positioning and is outside this work order's bounded documentation scope. 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
THESIS.md - Add "Reference primitive roles" so fixing the category does not silently redefine or erase existing components: OIC, ZTL, VEIP, ICI, AuthContract and Runtime Admissibility each get an architectural role, explicitly not a capability claim. VICCP, RegSpine and CAGE are deliberately left unassigned because no reachable repository defines them. - OAM is named without a role, pending OAM-ROLE-RECONCILIATION.md, and no component README may infer one from the thesis. - Narrow the Evidence Pack claim. A cryptographically valid Evidence Pack now establishes only the bounded cryptographic and structural integrity properties actually verified under the applicable schema/profile, and not truth, completeness, institutional validity, correct upstream interpretation, consequence occurrence or observation coverage. OAM-ROLE-RECONCILIATION.md (new) - Census of every reachable OAM definition. Two published surfaces conflict materially: the ICI README defines OAM as a standing/examination workflow, while the OIC admission contract says OAM may constrain operational authority. Those sit on opposite sides of the authority-planes non-collapse rule. Recorded with a recommendation and open questions for owner decision; not resolved by editorial preference. spec/ICI-ARCHITECTURE-CONSTITUTION-v0.2.md (new) - Normative successor under spec/CHANGE-CONTROL.md carrying all ten required change-record fields. Semantic change is CATEGORY RELATIONSHIP ONLY. - Definition, canonical chain, full-continuity rule, non-collapse rules, falsifiability and implementation neutrality are carried forward byte-identical, verified programmatically against the predecessor blob. - The predecessor is preserved unedited as historical normative evidence. - The filename carries -v0.2 because change control requires predecessor and successor to coexist under distinct paths; the reasoning is recorded in the document. README.md and CONTRIBUTING.md now point at the successor; the predecessor is still named as history. WEBSITE-CATEGORY-PATCH.md - Rewritten against live copy supplied by the owner. The category hero, the "why is this the rule" framing, the OIC card and the evidence-limitation statement are all marked KEEP, and the earlier proposal to insert an authority block is withdrawn as duplicative. - The patch now targets the one demonstrated defect: the VEIP card's "Portable execution evidence" primary label becomes "Execution integrity", with evidence moved downstream in the sequence. - Provenance is explicit: the owner read the site; this session could not, and says so. No runtime, schema, benchmark, claim-ceiling or historical-evidence change. 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
Three independent evaluators, each reading a single Veraxis surface in isolation, reported the abbreviation 'OIC' collapsing two distinct things: Open Institutional Computation (the field) and Open Institutional Compiler (the component). One recorded 'Two senses appear'; another that 'the acronym is also used for the category name'. A reader who cannot tell the field from the component cannot place the component within it, which defeats the purpose of fixing the category. Add an explicit abbreviation rule to the terminology section: the field is always written out and never abbreviated; OIC unqualified always means the Open Institutional Compiler; the component is expanded on first use. 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
Ten surfaces, three independent cold evaluations each. Evaluators received one artifact and the seven gate questions, were told nothing about the expected answers, and were asked separately what they thought the business was. Zero FAIL indicators across all 30. Q1 answered 'Open Institutional Computation' 30/30; no evaluator ever answered yes to Q6 or Q7. Records the two defects rounds 1-2 exposed and round 3 confirmed fixed - the OIC abbreviation collision and VEIP being undefined on veip-registry and veip-verifier-core - with verbatim evaluator quotes on both sides of the fix. Preserves disagreements rather than smoothing them: evaluators split on whether the VEIP surfaces read as a standards-and-certification business or simply as a published spec, and several independently observed that the surfaces disclaim much and demonstrate little. 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
The census recorded a material conflict between two published surfaces: the ICI README defined OAM as a standing/examination workflow, while the OIC admission contract said OAM may constrain operational authority. Those sit on opposite sides of the authority-planes non-collapse rule. The owner adopted the examination-side reading on 2026-09-08. OAM is the examination and audit-authority workflow within Open Institutional Computation: entitled examination of continuity evidence, disposition, replay, correction, and whether an examined result is fit for later institutional reliance. It does not originate institutional authority and does not authorize exact runtime execution. Replace the provisional OAM language in THESIS.md with the canonical role, and record the disposition, the consequent actions and the corrected statement in OAM-ROLE-RECONCILIATION.md. The record keeps the original conflict evidence and the recommendation as put, so the basis of the decision stays legible. Also recorded: OAM-GATE-* identifiers are audit/examination gates, not evidence that OAM owns runtime authorization, and historical identifiers are not renamed. 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.
Problem
Veraxis public surfaces make evidence artifacts substantially easier to recognize than the upstream institutional-authority computation that gives those artifacts meaning. Observed externally: an independent AI-assisted evaluation of VEIP centered on the Authorization Evidence Pack, and an executive discussion opened on authority/permission computation drifted to AEP security and evidence.
There is currently no single controlling source that fixes the category and the component relationships, so each repository's positioning is independently negotiable.
Proposed change
Add
THESIS.md— the owner-authorized controlling category source under work order CAT-ALIGN-001 — and the manual category-perception gate it references.Files changed (2 added, 0 modified, 0 deleted):
THESIS.md(new)governance/CATEGORY-PERCEPTION-GATE.md(new)The hierarchy it fixes:
THESIS.mdcarries a precedence rule: component repositories keep their own implementation scope, status, interfaces and claim ceilings, but do not redefine their architectural role without an owner-authorized successor to this document.Normative impact
No normative specification is modified.
spec/CATEGORY-CONSTITUTION.md,spec/CANONICAL-CHAIN.md,spec/INVARIANTS.md, the ontology, and the benchmark schemas are untouched.THESIS.mdstates explicitly that it does not silently override any normative specification, and that a specification changes only through its own governance process.Compatibility impact
None. No versioned artifact, profile, schema, interface or release is affected. The canonical nine-node chain, the eight joins, the invariants and ICTS are unchanged.
spec/CATEGORY-CONSTITUTION.mdis titled "ICI Category Constitution" and remains so in this PR. Reconciling that title with the Open Institutional Computation field is a normative change underspec/CHANGE-CONTROL.mdand requires a successor artifact; it is recorded as a known remaining inconsistency rather than made by README-adjacent prose.Benchmark impact
None. Eligibility, vectors, expected dispositions, schemas and claim ceilings are unchanged. No implementation gains or loses an ICTS status; every entry remains
NOT_EVALUATED.Claim impact
None. Role statements are architecture statements, not implementation claims.
THESIS.mdexplicitly preserves repository-specificSTATUS,CLAIMS.md, capability matrices, benchmark status, validation scope and research claim ceilings, and forbids any reading under which 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 behavior, schema, test, expected disposition, historical artifact or release was changed. The diff adds two Markdown files and modifies nothing.
Evidence
python3 tools/validate_repo.py549430974b9511261e997f8f67febb7ad99b503a:REPOSITORY VALIDATION: PASS(exit 0)REPOSITORY VALIDATION: PASS(exit 0) — required files, canonical joins J1–J8, exact canonical chain, resolved internal Markdown links, schema invariants, bounded licensing metadataBoth new files carry SPDX headers as the validator requires, and the internal link from
THESIS.mdto the perception gate resolves.549430974b9511261e997f8f67febb7ad99b503ae7295e02bf50ad9fb25b1ea343e42ced5cf41442Controlling thesis
This PR is the controlling thesis PR for CAT-ALIGN-001. Downstream repository PRs in this work order reference it until it merges.
AI assistance
Drafted by Claude under owner work order CAT-ALIGN-001. The category hierarchy, definitions and terminology table are owner-specified in that work order; drafting, repository validation and boundary checking were machine-assisted.
DCO
Signed-off-by:)Historical integrity
Nothing is rewritten; both files are new.
Generated by Claude Code