veraxis-protocol · veraxis-protocol · Sep 8, 2026 · Sep 8, 2026 · Sep 8, 2026 · Sep 8, 2026
@@ -0,0 +1,101 @@
+<!-- SPDX-FileCopyrightText: 2026 Veraxis Protocol -->
+<!-- SPDX-License-Identifier: CC-BY-4.0 -->
+
+# CAT-ALIGN-001 Execution Report
+
+**Work order:** CAT-ALIGN-001 — Veraxis Category Thesis Freeze and Public-Surface Alignment
+**Owner:** Arkadiy Miteiko
+**Executed:** 2026-09-08
+**Executor session:** `session_01Pkw68qW3iRaeJsiMPBEPvW`
+
+STATUS: **CAT_ALIGN_PR_SET_CREATED**
+
+THESIS PR: https://github.com/veraxis-protocol/institutional-continuity/pull/2
+THESIS BASE SHA: `549430974b9511261e997f8f67febb7ad99b503a`
+THESIS HEAD SHA: see the PR head; the thesis branch carries THESIS.md, the perception gate, the
+README deconfliction, the website patch document, the census and this report.
+
+REPOS CENSUSED: 14
+REPOS MODIFIED: 10
+REPOS NOT MODIFIED: 4
+
+## Per-repository record
+
+| Repository | Base SHA | Branch | Head SHA | Files changed | Tests / checks | PR | Status |
+|---|---|---|---|---|---|---|---|
+| `institutional-continuity` | `549430974b9511261e997f8f67febb7ad99b503a` | `cat-align-001-category-thesis` | see PR | `THESIS.md`, `governance/CATEGORY-PERCEPTION-GATE.md`, `README.md`, `WEBSITE-CATEGORY-PATCH.md`, `CATEGORY-SURFACE-CENSUS.md`, `CAT-ALIGN-001-EXECUTION-REPORT.md` | `tools/validate_repo.py` PASS before and after | [#2](https://github.com/veraxis-protocol/institutional-continuity/pull/2) | PR created |
+| `veip-spec` | `b7bae309cd39b6be2f1669aff75c4feb9cf18668` | `cat-align-001-category-thesis` | `26db2538f1913637a242b0730de6866f5943b408` | `README.md` (+20) | `make schema` PASS; `make check` red on `main` before and after (pre-existing missing `LICENSE.md`) | [#1](https://github.com/veraxis-protocol/veip-spec/pull/1) | PR created |
+| `veip-sdk` | `40bcb5708c8e3aadcb0e31d3190824ddc33f8fce` | `cat-align-001-category-thesis` | `6d1d65e77868a8a0516cff0cf9513785e15dd6c9` | `README.md` (+20) | `make check` PASS (the gate CI runs); pytest unavailable locally | [#1](https://github.com/veraxis-protocol/veip-sdk/pull/1) | PR created |
+| `veip-verifier-core` | `e8b985920b60ba74f2e0e014ee107a5c4937b1fc` | `cat-align-001-category-thesis` | `6df68f5667ea283b59d5e9cad51ae9cd41bc4b12` | `README.md` (+18) | `make check` PASS before and after; pytest unavailable locally | [#1](https://github.com/veraxis-protocol/veip-verifier-core/pull/1) | PR created |
+| `veip-registry` | `a0b70452d14c0b29da500d53714ae215b09bc43e` | `cat-align-001-category-thesis` | `f91b474a2202c1124920cedb1286d6f0c9c7101f` | `README.md` (+16) | `make check` PASS before and after; pytest unavailable locally | [#1](https://github.com/veraxis-protocol/veip-registry/pull/1) | PR created |
+| `Institutional-Compiler` | `c3d986229e2d7874a30a318981f5045e3f793236` | `cat-align-001-category-thesis` | `5a7813b6488f7568f0379afedfe0d73996c85634` | `README.md` (+23) | claims-discipline 51 passed; ruff, format, strict mypy PASS; `make verify` PASS (manifest INCOMPLETE preserved); `make falsify` 4/4; **full suite 1743 passed, 1 declared skip, 0 failed** | [#44](https://github.com/veraxis-protocol/Institutional-Compiler/pull/44) | PR created |
+| `AuthContract` | `6c677aec730bff79dfc60a88d1721564000ad111` | `cat-align-001-category-thesis` | `1dfeef7267d66fb8dc16bc37de6aedd62906c133` | `README.md` (+16) | `make test` **343 passed**; `make falsify` 4/4; `make no-network` PASS | [#16](https://github.com/veraxis-protocol/AuthContract/pull/16) | PR created |
+| `runtime-admissibility-experiment` | `ded0d0d0d831512556ba14c5b692cebb553c7a83` | `cat-align-001-category-thesis` | `de5f0d0a33b4e131e8efa785055519b7e4ce8315` | `README.md` (+14) | `pytest` 10 passed before and after; scenario CLI runs clean | [#1](https://github.com/veraxis-protocol/runtime-admissibility-experiment/pull/1) | PR created |
+| `RAED` | `471f81dcd6a468a5f8b6b6cb95c4b06b4182896a` | `cat-align-001-category-thesis` | `b979a7318e8284f06b218f530ac7979382917e29` | `README.md` (+12) | `gofmt` clean; `go vet ./...` clean; `go test ./...` ok | [#1](https://github.com/veraxis-protocol/RAED/pull/1) | PR created |
+| `Veraxis-Memory-Admissibility-Management-MAM-` | `9f9b8711c7edd811e94c1769f824053553af125f` | `cat-align-001-category-thesis` | `bfc4d1d151a090ab94cc9ff0e77be99d4a5adf30` | `README.md` (+14) | `go build ./...` exit 0; `go test ./...` ok across adversarial, integration and unit suites | [#1](https://github.com/veraxis-protocol/Veraxis-Memory-Admissibility-Management-MAM-/pull/1) | PR created |
+| `Institutional-Compiler-Review-Ledger` | `713381f866798a950e02cf19c3270e145af94369` | — | — | none | — | — | Not modified (Class C, frozen evidence ledger) |
+| `white-papers` | `584a9d3393b3183a2ed985fbb6ca6caf466b84cb` | — | — | none | — | — | Not modified (Class C, released PDF) |
+| `Open-Audit-Mission` | empty repository | — | — | none | — | — | Not modified (Class D, no commits) |
+| `awesome-mcp-servers` | not cloned | — | — | none | — | — | Not modified (Class D, upstream fork) |
+
+## Website
+
+- Exact source repo identified? **NO**
+- Modified? **NO**
+- WEBSITE-CATEGORY-PATCH.md location: [`WEBSITE-CATEGORY-PATCH.md`](WEBSITE-CATEGORY-PATCH.md) in
+  this repository.
+
+All 14 reachable repositories were searched for `index.html`, any `.html`, `CNAME`, `_config.yml`,
+`netlify.toml`, `vercel.json`, `next.config.*`, `astro.config.*` and GitHub Pages deployment
+workflows. Zero matches. A read of `https://veraxis.io` was refused by the network egress policy
+(`EGRESS_BLOCKED`) and was not retried or routed around, so current site copy could not be captured
+and is left explicitly blank in the patch document rather than reconstructed.
+
+No unrelated repository was modified as a substitute.
+
+## Perception surface
+
+**Old failure mode.** Evidence artifacts were the most legible thing about Veraxis. The VEIP family
+foregrounded execution authorization and Evidence Pack emission with no statement of what must be
+established upstream; OIC — the component that addresses that upstream problem — never named the
+field it belongs to; and ICI's badge presented itself as the parent category. An external reader
+given any one of those surfaces would reasonably conclude that Veraxis is an evidence-infrastructure
+company. Two external events showed exactly that: an independent AI-assisted evaluation of VEIP that
+centered on the Authorization Evidence Pack, and an executive discussion that opened on
+authority/permission computation and drifted to AEP security and evidence.
+
+**New intended hierarchy.** Field: Open Institutional Computation. Missing computation: institutional
+authority computation. OIC upstream; VEIP the downstream execution-integrity boundary; enforcement
+runtimes consumers; Evidence Pack / AEP a downstream artifact; ICI the reference end-to-end
+continuity architecture within the field, not a competing parent. THESIS.md is the controlling
+source and every aligned repository links to it.
+
+**Remaining known inconsistencies.** Recorded in
+[CATEGORY-SURFACE-CENSUS.md](CATEGORY-SURFACE-CENSUS.md): the `spec/CATEGORY-CONSTITUTION.md` title
+(requires a normative successor under `spec/CHANGE-CONTROL.md` — owner decision), the unresolved
+veraxis.io source, a pre-existing red CI gate in `veip-spec`, a truncated sentence in the
+`veip-registry` README, the unassessed white-paper PDF, and component names (`VICCP`, `ZTL`,
+`RegSpine`, `CAGE`, `OAM`) with no reachable repository in this account.
+
+## Negative assertions
+
+- runtime semantics changed: **FALSE**
+- schemas changed: **FALSE**
+- benchmark evidence changed: **FALSE**
+- historical releases rewritten: **FALSE**
+- implementation maturity claims broadened: **FALSE**
+
+Additionally: no test expectation was changed to accommodate messaging. Where a test blocked the
+standard placement — `AuthContract`'s developer-language ordering lock — the documentation moved and
+the test stood. No enterprise adoption is asserted for Google Cloud, Backbase, Fujitsu or any other
+party. No normative specification was altered. No branch was merged, and no default branch was
+written to.
+
+## Final verdict
+
+**CAT_ALIGN_PR_SET_CREATED**
+
+Not `CAT_ALIGN_COMPLETE_VERIFIED`: every PR is open and unmerged, which is the work order's default
+disposition. THESIS.md exists, the VEIP family is aligned, ICI no longer claims the parent category,
+and OIC carries its category-role link — but completion depends on merge, and on the owner decision
+recorded for `spec/CATEGORY-CONSTITUTION.md` and the veraxis.io source.
@@ -0,0 +1,80 @@
+<!-- SPDX-FileCopyrightText: 2026 Veraxis Protocol -->
+<!-- SPDX-License-Identifier: CC-BY-4.0 -->
+
+# Category Surface Census — CAT-ALIGN-001
+
+**Controlling source:** [THESIS.md](THESIS.md) — Veraxis Category Thesis v1.0
+**Date:** 2026-09-08
+**Scope:** every repository reachable by the executing account under `veraxis-protocol` (14 total,
+enumerated from the account's repository list; the listing reported no further pages).
+
+## Method
+
+For each repository: the working tree was cloned and inspected — `README.md`, category and
+architecture documents, terminology documents, and public landing documentation — and searched
+case-insensitively across all Markdown and text files for the terms `category`,
+`Institutional Computation`, `Institutional Continuity`, `AI governance`, `governance layer`,
+`authority`, `authorization`, `Evidence Pack`, `AEP`, `VEIP`, `OIC`, `protocol`, and `trust`.
+
+Repositories were then classified:
+
+- **A — CORE:** receives the standard role block now.
+- **B — SUPPORTING:** links to THESIS.md where category positioning appears.
+- **C — HISTORICAL/EXPERIMENTAL:** history preserved; historical claims not rewritten for consistency.
+- **D — IRRELEVANT/FORK:** no action.
+
+No repository was rewritten merely for consistency.
+
+## Census
+
+| Repo | Class | Current positioning before CAT-ALIGN-001 | Conflict found? | Change made? | Reason | PR | Claim-impact assessment |
+|---|---|---|---|---|---|---|---|
+| `institutional-continuity` | A | Badge read `Category: ICI`, positioning ICI as the parent category | **Yes** — competing parent category | Yes — added THESIS.md and the perception gate; replaced the category badge with a field badge plus an architecture badge; added a placement section | Controlling source lives here; ICI must read as an architecture within the field, not as the field | [#2](https://github.com/veraxis-protocol/institutional-continuity/pull/2) | None. Nine-node chain, eight joins, invariants, ICTS and all claim ceilings unchanged; every implementation remains `NOT_EVALUATED` |
+| `veip-spec` | A | Deterministic execution-control standard; execution authorization and evidence packaging foregrounded | Yes — no upstream boundary stated; readable as originating authority | Yes — role block plus an architectural-position subsection | Highest-risk surface for category collapse toward Evidence Packs | [#1](https://github.com/veraxis-protocol/veip-spec/pull/1) | None. Normative spec, scope, licensing, schemas, invariants, versioning untouched; "Evidence Pack" schema terminology preserved |
+| `veip-sdk` | A | Architecture model began at `AI System → Action Proposal → VEIP Authorization Gate` | Yes — chain started at the gate, nothing stated what must be true upstream | Yes — role block plus an Upstream Boundary section before the architecture model | An authority envelope is an input; the SDK does not originate it | [#1](https://github.com/veraxis-protocol/veip-sdk/pull/1) | None. Existing scope sections, invariants and version bindings preserved |
+| `veip-verifier-core` | A | Careful about what it is not, but silent on what a PASS establishes | Yes — a PASS was over-readable as upstream validation | Yes — role block plus "What a PASS does and does not establish" | Verifier output is the easiest artifact in the stack to over-read | [#1](https://github.com/veraxis-protocol/veip-verifier-core/pull/1) | Restrictive only. Existing verifier claim ceiling preserved, not widened |
+| `veip-registry` | A | Already stated it is not a governance authority and not a centralized global registry | Partial — correct boundaries, no upstream reason given | Yes — role block plus the registry authority boundary | Custody of evidence is not legitimacy of authority | [#1](https://github.com/veraxis-protocol/veip-registry/pull/1) | None; restrictive in effect |
+| `Institutional-Compiler` | A | Opened on status, bootstrap date and governing design; field never named | Yes — the upstream component was the least placeable surface | Yes — role section near the top | Inverted dependency: downstream surfaces were easier to recognize than the upstream one | [#44](https://github.com/veraxis-protocol/Institutional-Compiler/pull/44) | None. `BOUNDED_REFERENCE_IMPLEMENTATION`, Gate F/G figures, twelve exclusions, OIC-Bench `TARGET - NOT MEASURED` rows, STATUS/CLAIMS/capability matrix all unchanged |
+| `AuthContract` | A | Developer-workflow framing under an owner-approved language freeze | Partial — receipt behavior over-readable as originating authority | Yes — role block placed **after** `Current status`, below `## Quick start` | `docs/DEVELOPER-LANGUAGE.md` and `tests/test_veip.py` forbid deep ontology vocabulary before Quick start; placement moved rather than changing the test | [#16](https://github.com/veraxis-protocol/AuthContract/pull/16) | None. TRL 4 / experimental status and the full "does not currently claim" list preserved verbatim |
+| `runtime-admissibility-experiment` | A | Static authorization vs runtime admissibility, formally stated | Partial — `RA(x,t)` over-readable as defining institutional authority | Yes — role block stating `A_t` is an input | Research into the runtime currentness/admissibility boundary inside the field | [#1](https://github.com/veraxis-protocol/runtime-admissibility-experiment/pull/1) | None. No equation, predicate, scenario or result altered |
+| `RAED` | B | Semantic memory substrate; core invariant is a field-level non-collapse rule | No conflict | Yes — role block plus thesis link | Category positioning appears ("It is the layer that…"), so the link applies | [#1](https://github.com/veraxis-protocol/RAED/pull/1) | None. CLAIMS, LIMITATIONS, CONFORMANCE, benchmarks, design targets untouched |
+| `Veraxis-Memory-Admissibility-Management-MAM-` | B | "Memory is part of the authority path"; AEP appears in the custody chain | Partial — authority-path sentence over-readable as memory creating authority | Yes — role block bounding the authority-path claim and placing AEP downstream | AEP terminology and authority positioning appear here | [#1](https://github.com/veraxis-protocol/Veraxis-Memory-Admissibility-Management-MAM-/pull/1) | None. Production invariants, benchmark envelope and release notes unchanged |
+| `Institutional-Compiler-Review-Ledger` | C | Adjudication and diagnostic evidence records; zero category-term hits | No | **No** | Frozen evidence ledger. Rewriting historical records for messaging consistency is forbidden by this work order | — | None; untouched |
+| `white-papers` | C | Single released PDF (`Veraxis White Paper v1.2.pdf`); no editable Markdown surface | Not assessable — binary released artifact | **No** | Released artifact; not rewritten. Any category correction belongs in a successor paper version | — | None; untouched |
+| `Open-Audit-Mission` | D | Repository is empty (clone reported no commits) | No | **No** | No surface to patch | — | None |
+| `awesome-mcp-servers` | D | Upstream fork, not Veraxis positioning | No | **No** | Fork of third-party content | — | None |
+
+**Totals:** 14 censused, 10 modified, 4 not modified.
+
+## Remaining known inconsistencies
+
+These are recorded rather than fixed, each for a stated reason.
+
+1. **`spec/CATEGORY-CONSTITUTION.md` is titled "ICI Category Constitution".** With the README now
+   presenting ICI as an architecture within Open Institutional Computation, the normative spec still
+   uses "category" for ICI. Reconciling it is a **material normative change** under
+   [spec/CHANGE-CONTROL.md](spec/CHANGE-CONTROL.md) and requires a successor artifact with a full
+   change record. It was deliberately not changed by README-adjacent prose, per the work order's
+   guardrail against altering released specs by prose alone. **Owner decision required.**
+2. **veraxis.io source is unresolved.** Not present in any reachable repository, and the live site
+   is unreachable from this environment. See [WEBSITE-CATEGORY-PATCH.md](WEBSITE-CATEGORY-PATCH.md).
+3. **`veip-spec` CI is red on `main`, pre-existing.** `make check` requires both `LICENSE` and
+   `LICENSE.md`; only `LICENSE` exists. Unrelated to category positioning and outside this work
+   order's bounded documentation scope, so not fixed. Expect the veip-spec PR to inherit that
+   failure.
+4. **`Veraxis-Memory-Admissibility-Management-MAM-` CI is red on `main`, pre-existing.** A
+   toolchain mismatch: `go.mod` declares `go 1.22` while `.github/workflows/go.yml` pins
+   `go-version: '1.20'`, so the `build` job fails with `cannot compile Go 1.22 code` on every push
+   and pull request regardless of content. Locally, with Go 1.24.7, `go build ./...` and
+   `go test ./...` both pass. The fix is a one-line workflow bump, which is a CI/toolchain change
+   rather than category positioning and therefore outside this work order's scope. Not fixed here.
+
+5. **`veip-registry` README ends mid-sentence.** The "Relationship to veip-spec" section reads
+   "The canonical Evidence Pack schema originates in:" with nothing following. Pre-existing and
+   unrelated to category positioning; not fixed.
+6. **`white-papers` v1.2 PDF has not been assessed against the thesis.** Binary released artifact;
+   assessing and, if needed, correcting it belongs to a successor paper version, not to this work
+   order.
+7. **Component names `VICCP`, `ZTL`, `RegSpine`, `CAGE` and `OAM`** appear in the ICI README's
+   reference-primitive table but have no reachable repository in this account. Their public
+   surfaces, if any exist elsewhere, were not censused.
@@ -19,7 +19,8 @@ A good contribution makes the system:
 
 Read:
 
-1. `spec/CATEGORY-CONSTITUTION.md`
+1. `spec/ICI-ARCHITECTURE-CONSTITUTION-v0.2.md` (current; supersedes
+   `spec/CATEGORY-CONSTITUTION.md`, which is preserved as historical normative evidence)
 2. `CLAIMS.md`
 3. `GOVERNANCE.md`
 4. `spec/CHANGE-CONTROL.md`