Prepare VSTD 1.2.0 and restore the public boundary - #20
Closed
TimeLordRaps wants to merge 39 commits into
Closed
Conversation
Rejects "Zero Identity" as a public label: the construction withholds civil identity while retaining pseudonym, key, trust root, issuer, and revocation coordinates. Adds a non-normative semantic model, threat model, standard-library evaluator, 14 fixtures, and 39 tests that keep UNKNOWN and CONFLICTED intact. Coordinate: no layer, base 598c545, seam experiments/zizk_vstd/zero_identity. Falsification: any record reaching ACCEPTED_BOUNDED with a REFUTED property, or unlinkability reaching SUPPORTED, refutes the model. Compatibility: no wire identifier, schema $id, receipt digest, console alias, lifecycle token, dependency, or conformance behavior changed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Authorization alone cannot tell a first-party claim from a relayed one, so the profile now keeps three questions apart: whether a key was permitted a scope, who is speaking and at what remove, and how the key obtained its authority. Authorship degree covers originator, delegate, relay, and aggregator roles; an absent role stays UNKNOWN rather than defaulting to origination, and a non-originator claiming origination is REFUTED. Credential ancestry records issuance, delegation, and rotation links, mirroring the recorded-lineage discipline of VSTD-Graph-1: a revoked ancestor or a scope-widening delegation is REFUTED, while an unattested link, a chain missing its trust root, and an unattested rotation stay UNKNOWN. Neither property can reach SUPPORTED. Adds seven fixtures (21 total) and eighteen tests (57 total). Records that ancestry enlarges the correlation surface, so authorship provenance and unlinkability are in direct tension, resolved toward provenance with the cost stated. Coordinate: no layer, base 598c545, seam experiments/zizk_vstd/zero_identity. Falsification: authorship_degree or credential_ancestry reaching SUPPORTED, a relayed role read as first-party authorship, or a revoked ancestor evaluating as anything other than a refutation. Compatibility: no wire identifier, schema $id, receipt digest, console alias, lifecycle token, dependency, or conformance behavior changed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Records the round-1 result and tightens the evaluator where review found it inferring more than the evidence carried. Required public coordinates now cover the pseudonym, the key identifier, and the declared trust roots, and a minimization request that removes any of them is REJECTED whether it names the leaf or a parent path. Authentication requires a pseudonym and a key identifier bound to a declared root; authorization requires an issuer that is itself declared. Authorship degree must be a non-negative integer, so a boolean or a negative remove stays UNKNOWN rather than being read as origination. A shared pseudonymous coordinate no longer refutes independence. It refutes independent corroboration from that coordinate, which the record already carries, but actor independence is a claim about people and stays UNKNOWN from a single record. The fixture moves from rejected_ to unknown_ to say so. The round-1 report separates four evidence classes and states a ceiling for each: semantic results, external attestations, declared assumptions, and protocol guarantees. It records the terminology decision, the claims currently justified, the claims still prohibited, and the failed tests, of which there are none. 22 fixtures and 65 tests, all passing; repository suite 255 passed, 3 skipped; presentation gate clean. Coordinate: no layer, base 598c545, seam experiments/zizk_vstd/zero_identity. Falsification: absence of a required coordinate producing a favourable result, a parent-path deletion bypassing a protected leaf, or unlinkability, authorship_degree, or credential_ancestry reaching SUPPORTED. Compatibility: no wire identifier, schema $id, receipt digest, console alias, lifecycle token, dependency, or conformance behavior changed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Merge the bounded identity-disclosure and real zero-knowledge experiments into one experimental tree, then define the actor-blind Tier 0 reverification boundary. Agreement remains non-accumulating, divergence requires a checkable comparable trace, and UNKNOWN and CONFLICTED remain first-class outcomes. Keep rust as an optional object-bound analytical view with no verdict authority, distinguish the two existing STALE enum families, and record the ZK journal trichotomy correction without implementing or reserving a wire profile. Relocate the Round 1 zero-knowledge report beside its experiment. The repository-level ZK containment test remains the sole deliberate file outside experiments/zizk_vstd. Validation: 22 ZI fixtures, 65 ZI tests, 3 ZK containment tests, 258 repository tests passed with 3 pre-existing skips, presentation gate passed, and compileall passed.
# Conflicts: # AGENTS.md # ROADMAP.md # docs/profiles/experimental-workflow.md # docs/reference.html # examples/experimental_workflow/README.md # examples/experimental_workflow/demo.py # experiments/INDEX.md # scripts/build_reference.py # tests/test_experimental_workflow_profile.py
# Conflicts: # docs/ECOSYSTEM.md
Bind generic receipts to a strict profile and package every specification for installed-wheel validation. Record actor independence without inferring it from matching runs, preserve Graph conflicts, and mark supplied-rating levels as non-conformant candidates. Add architecture, schema, packaging, and adversarial coverage.
5 tasks
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
TimeLordRaps
added
specification
State Artifact support as forward causal-provenance flow and Rust as a memetic backtrace over recorded ancestor states without promoting diagnostic reachability into guilt or intervention-level localization. Correct validator and repository-check wording, improve release-note structure, and move the newcomer actions into the first viewport with canonical site metadata. Coordinate: VSTD architecture and v1.2.0 public/release surfaces; no wire-format change. Falsification: any revised surface must not imply that reachability proves responsibility, that generic validation verifies external evidence, or that repository checks establish VSTD conformance. Compatibility: frozen identifiers, schemas, receipt bytes, and runtime behavior are unchanged.
This was referenced Aug 27, 2026
Owner
Author
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
2 participants
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.
Coordinate
TimeLordRaps/verifiercodex/v1.2.0-workflow-profile@039ba96517ebebe733e3f728aa52989233f8b010main@598c545be3833d6d81bb7e252ca5837f3bb2a4491.2.0release candidate; this pull request does not merge, tag, or publish it.F5537E7240663768250B315091A5B5158391B78C.The file-to-seam review matrix and maintainer disposition remain tracked in issue #21; this pull request does not convert passing automation into human approval.
What this pull request changes
Verification semantics and compatibility
layer4_bindingreadable and newly emitted under the frozen profile while classifying it as legacy generic assessment context, not VSTD-4 dispatch or conformance.NOT_ESTABLISHEDwhere no evidence-binding adapter exists; VSTD-5 rejects unearned readiness.Governing artifact-first architecture
examples/zizk_artifact_first/, including the tracked public receipt, public envelope, self-test result, source, exact digests, and verifier command.Public and maintainer surfaces
AGENTS.md,HUMANS.md, andTIME.mdas non-overlapping agent, human, and repository-contradiction controls.conformance-gatejob identifier remains unchanged solely because branch protection requires that exact status context.security-extendedqueries and makes it a protected-gate dependency.UNRELEASEDpending a separate finalization decision.Exact-head evidence
CARGO_NET_OFFLINE=true ./scripts/verify_recorded_proof.shrebuilt the cached verifier path and returnedPASSfor the tracked RISC Zero receipt and public envelope against the pinned image identifier; no private witness or salt was used.repo:artifact digest verify; current manifest digest:sha256:20a9060d8244ed1af59d0ea2e058dc412b08c5b4851c4abcbf7994059e2b093f.HEAD.twine checkpasses; the public-boundary scan checked 446 text members across 3 archives.33036499955passed: Python 3.10–3.13, standard-library smoke, SCITT cryptography, Linux/Windows release integrity, cross-platform reproducibility, installed-wheel smoke, Pages/presentation, CodeQL, and the protected repository-check aggregate.TIME.mdisStatus: CLEAR.Compatibility boundary
PASSremains immutable while current admissibility may change;UNKNOWN,CONFLICTED, andNOT_ESTABLISHEDremain visible.Falsification condition
Request changes if any field name, declaration, digest, repetition, graph multiplicity, actor reputation, runtime placement, SCITT registration, or satisfiable formula can increase assurance without a named mechanism validating the exact proposition and evidence binding; if mechanism separation is presented as evidence-bound actor independence; if recorded reachability is presented as causal localization; if
UNKNOWNorCONFLICTEDbecomes clean; if current candidate/conformance boundaries disappear; or if any exact-head check above cannot be reproduced.Maintainer checklist
TIME.mdisStatus: CLEAR.