docs: preserve RESULT-001 adjudicated evidence pointer - #32
Merged
veraxis-protocol merged 1 commit intoAug 18, 2026
Conversation
Two evidence documents and one scoped guard correction. The pointer names RESULT-001's adjudicated claim and the digests behind it. The evidence bytes themselves stay owner-held and outside this repository, so what lands here is enough to tell whether a document someone shows you is the adjudicated record or something derived from it — and nothing more. It carries no local path, no process id, no hostname, no filesystem structure; machine-checked for all of those before commit. The guard correction is the interesting part. `test_no_changed_json_artifact_ asserts_the_measured_claim` prohibited every changed JSON artifact from carrying MEASURED_INTERNAL_END_TO_END_TECHNICAL_DEMONSTRATION outside a disclaimer. That was exactly right when written: no owner adjudication existed, so any artifact naming the ceiling would have been helping itself to it. The owner has since adjudicated the claim ESTABLISHED, and a pointer whose whole function is to report that decision now trips a rule written for a world where the decision did not exist. The successor rule is narrower than "this file is allowed": no changed JSON artifact may ORIGINATE the measured claim; one may REPORT it only while cryptographically bound to the pre-existing owner claim decision and canonical record. Seventeen pointer fields plus four authorization fields plus authorized-path membership must all hold, and the pointer still may not carry the ceiling as a property of itself. Nothing is exempted by filename — a copy of the pointer under another name is judged by identical rules, and an impostor document is refused. Twenty-two mutations are tested one at a time: swapped owner-claim digest, swapped canonical digest, changed decision, each of the three record-class flags, changed representation status, wrong result or claim id, wrong implementation commit, scenario bundle or kernel pin, published or independently-assured or benchmark status, each of the four authorization flags, an unauthorized path, and an emptied path list. Each one closes the reporting exception. A predicate that survived any of them would not be binding the pointer to anything. Preservation and pointer only. No execution, no rerun, no RESULT-002, no claim readjudication, no ceiling expansion, no benchmark release. RESULT-001 remains permanently bound to implementation commit a2ece68; a later documentation commit on this branch is provenance recorded after the result, not the implementation that produced it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
veraxis-protocol
merged commit Aug 18, 2026
ac52dcd
into
ztl/currentness-slice-001-frozen-design
8 checks passed
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.
PRESERVATION / POINTER ONLY — NO EXECUTION — NO CLAIM EXPANSION
What this is
Two evidence documents and one scoped contract-guard correction. Nothing was executed, nothing was rerun, and no claim was re-adjudicated.
RESULT-001 established claim
MEASURED_INTERNAL_END_TO_END_TECHNICAL_DEMONSTRATIONOIC-ZTL-OAM-DEMO-SLICE-001-RESULT-001-MEASURED-CLAIM-001d98f3f5afc17193b21aa684f51af4e902a46b9a98ee75ff2560e670a5dbe8403d14f896c58249394564e8a95b011e2f9f6c843cc29ad9a13f6d62cc0ffb79c5ba2ece68f013c25e6a3874f20a924e95730c175f0sha256:ae72389334d0476421144e7ad42b6ca74b68e65d524ee188cfdbc485e5129bd356e1ff0510c62b04dbd85bbe08b7a6deacbf276bThe claim means: under that exact frozen synthetic scenario, implementation, scenario bytes, owner authorization and pinned kernel, RESULT-001 measured the integrated chain from synthetic source through OIC representation, owner admission, InstitutionalIR, control/runtime binding, live ZTL evaluation, currentness, institutional authority, OAM composition, bounded action disposition, governed propagation, separate consumer revalidation, reliance issuance where authorized, persisted hash-resolvable evidence, and owner claim adjudication. Nothing broader.
Exact repository delta — three files
docs/operations/…RESULT-001-PRESERVATION-AUTHORIZATION-001.jsondocs/operations/…RESULT-001-EVIDENCE-POINTER-001.jsontests/contract/test_demo_slice_contract.pyNo change under
src/,schemas/,.github/,demo/, orSTATUS.md.Evidence bytes are not in this repository
evidence_bytes_committed_to_repository: false·evidence_hosting: OWNER_HELD_EXTERNAL_FREEZENo local filesystem path is disclosed. The pointer was machine-checked before commit for local absolute paths, home directories, temp paths, evidence-store names, process ids, hostnames, and the authorization/consumption filenames — zero occurrences of each, and zero quoted strings beginning with
/.The guard correction
test_no_changed_json_artifact_asserts_the_measured_claimforbade every changed JSON artifact from carrying the measured ceiling outside a disclaimer. Correct when written — no owner adjudication existed then, so naming the ceiling would have meant claiming it. Now a pointer whose only job is to report that adjudication trips a rule written for a world without it.The successor rule is narrower than an allowlist:
Classified
POST_ADJUDICATION_REPRESENTATION_SCOPE_CORRECTION. Explicitly not a filename allowlist carve-out, not a semantic weakening, not a re-adjudication, not a ceiling expansion — each recorded asfalsein the preservation authorization.Seventeen pointer fields, four authorization flags and authorized-path membership must all hold; the pointer still may not carry a
claim_ceilingof its own. Nothing is exempted by filename, so an identical document at another path is refused. 22 single-field mutations are tested and each one closes the exception.RESULT-001 is not a benchmark
benchmark_status: NOT_A_BENCHMARK·representation_status: POINTER_ONLY· research artifact and external technical claim package NOT_CREATED.Unestablished, and stated in the pointer itself
PRODUCTION_READINESS · INSTITUTIONAL_VALIDITY · LEGAL_VALIDITY · NON_BYPASSABLE_PRODUCTION_ENFORCEMENT · INDEPENDENT_TIER1_REPRODUCTION · INDEPENDENT_ASSURANCE · REAL_WORLD_GRANT_AUTHORIZATION · GENERALIZATION_TO_OTHER_INSTITUTIONAL_DOMAINS — all NOT ESTABLISHED. GLOBAL_SEMANTIC_IMPLEMENTATION_GATE CLOSED. PROPOSED_CONTRACT_GLOBALLY_ADMITTED FALSE. RUN-004 remains FALSE.
Historical identity
RESULT-001 stays permanently bound to implementation commit
a2ece68f. If this documentation change merges, the branch moves past that commit — that is provenance recorded after the result, not the implementation that produced it.Owner merge authorization issued under
OIC-ZTL-OAM-DEMO-SLICE-001-RESULT-001-REPOSITORY-POINTER-MERGE-001.
Merge commit only; no execution and no claim expansion.
🤖 Generated with Claude Code