CAT-ALIGN-001: align veip-registry with controlling Veraxis category thesis - #1
Merged
Merged
Conversation
Add the standard category role block and the registry's authority boundary. A registry stores and serves evidence state. It does not originate the institutional authority represented by that state. A registry that accepted, stored and served a pack perfectly has established custody of evidence, not the legitimacy of the authority that evidence describes. The repository's existing statements that it is not a governance authority and not a centralized global registry are preserved and now have an explicit upstream reason. Documentation only, additive. API surface, ingestion semantics, storage, schema and tests are unchanged. 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
Independent evaluators reading this README in isolation reported that VEIP is never expanded or defined here, and that whether VEIP originates institutional authority is therefore 'unstated'. A downstream component that cannot say what the protocol above it does leaves a required category answer unobtainable from the artifact alone. Expand the acronym and state VEIP's role and its three explicit non-roles in the role block. Documentation only, additive. API surface, ingestion semantics, storage and schema unchanged. 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.
README.mdgains a role block near the top. Nothing is removed or reworded.Why
This README is already the most disciplined of the VEIP family about what it is not — explicitly not a certification authority, not a supervisory endorsement system, not a centralized "global registry," and "a reference surface, not a governance authority." Those statements are preserved exactly.
What was missing is the upstream reason they hold. The added text supplies it:
and makes the consequence explicit: a registry that accepted, stored and served a pack perfectly has established custody of evidence, not the legitimacy of the authority that evidence describes.
Files changed
README.md— 16 insertions, 0 deletionsWhat is explicitly preserved
POST /v1/evidence,GET /v1/evidence/{evidence_id})veip-specand canonical schema originClaim impact
None, and restrictive in effect. No conformance, certification, maturity, adoption or deployment claim is made or broadened. No enterprise adoption is asserted for any party.
No runtime change
No API behavior, ingestion logic, storage, schema, test or fixture was changed. The diff touches one Markdown file.
Validation
make check— the structural + schema gate:a0b70452d14c0b29da500d53714ae215b09bc43e:OK: schema JSON parses/OK: checks passed, exit 0OK: schema JSON parses/OK: checks passed, exit 0make test(pytest) could not be run in this environment —pytestis not installed here and the package is not pip-installed. Disclosed rather than worked around; the change adds no Python, so no test outcome can be affected by it.a0b70452d14c0b29da500d53714ae215b09bc43ef91b474a2202c1124920cedb1286d6f0c9c7101fObserved, not fixed here
README.mdends mid-sentence: the final "Relationship to veip-spec" section reads "The canonical Evidence Pack schema originates in:" with nothing following it. This is pre-existing onmain, is unrelated to category positioning, and is left untouched under this work order's bounded documentation scope. It is recorded in the CAT-ALIGN-001 census for separate disposition.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