World Models · Published

Verification / ZK Attestation

Attach a governed predicate, proof or attestation and source-qualified verification result to another model while minimizing disclosure and remaining independent of storage and interface format.

AI YAMLAGENTS.mdResearch evidence
Published. Research assurance: reviewable-draft. The Codex-only synthesis is published under an explicit repository-owner provider waiver. It passed structural validation and a separate no-tools adversarial audit, but remains a reviewable draft until independent second-provider review and the holds below are closed.
Catalogue IDWM-XCT-006
Version0.3.0-research.1
Previous version-
Typemixin
ValidationPassed
Synthesis digestsha256:1fe93b552eb052fc…
10Sources
6Bundles
12Layers
24Findings
72Questions
24Artifacts
Format-independent logical structure

Bundles → Layers → Findings → Questions + Artifacts

attestation-identity-statement-and-requestAttestation identity, statement and request2 layers

Identifies the proof binding and defines exactly what statement a verifier requests.

binding-identity-host-and-statementBinding identity, host and statement2 findings

Stable identity and unambiguous subject matter for the attestation.

attestation-binding-identifier-host-record-purpose-and-version

Attestation binding identifier, host record, purpose and version

Mixin identifier, host record and path, binding purpose, profile, version, predecessor, lifecycle state and authoritative registry.

Questions
  1. What identities, roles, versions, scope and values define attestation binding identifier, host record, purpose and version?identity
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support attestation binding identifier, host record, purpose and version?evidence
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may attestation binding identifier, host record, purpose and version be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?validation
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • Attestation binding identifier, host record, purpose and version recordVersioned evidence-bearing attestation record for attestation binding identifier, host record, purpose and version with statement, suite, event and knowledge time, provenance and disclosure marking.
statement-predicate-relation-public-instance-schema-and-canonical-form

Statement, predicate, relation, public instance, schema and canonical form

Predicate identifier and version, formal relation, public instance, parameterization, schema, canonical bytes or digest and semantic description.

Questions
  1. What identities, roles, versions, scope and values define statement, predicate, relation, public instance, schema and canonical form?definition
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support statement, predicate, relation, public instance, schema and canonical form?authority
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may statement, predicate, relation, public instance, schema and canonical form be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?interoperability
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • Statement, predicate, relation, public instance, schema and canonical form recordVersioned evidence-bearing attestation record for statement, predicate, relation, public instance, schema and canonical form with statement, suite, event and knowledge time, provenance and disclosure marking.
verifier-request-purpose-and-acceptance-boundaryVerifier request, purpose and acceptance boundary2 findings

Captures requested evidence without treating verification as authorization.

verification-request-identifier-verifier-audience-purpose-and-requested-claims

Verification request identifier, verifier, audience, purpose and requested claims

Request identity, external verifier, audience, purpose, requested predicates or disclosures, format choices, expiry and request-object digest.

Questions
  1. What identities, roles, versions, scope and values define verification request identifier, verifier, audience, purpose and requested claims?relationship
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support verification request identifier, verifier, audience, purpose and requested claims?temporal
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may verification request identifier, verifier, audience, purpose and requested claims be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?access
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • Verification request identifier, verifier, audience, purpose and requested claims recordVersioned evidence-bearing attestation record for verification request identifier, verifier, audience, purpose and requested claims with statement, suite, event and knowledge time, provenance and disclosure marking.
acceptance-policy-reference-required-assurance-and-decision-separation

Acceptance policy reference, required assurance and decision separation

External policy identifier and version, required proof and freshness properties, exception path and explicit separation of cryptographic result from relying-party decision.

Questions
  1. What identities, roles, versions, scope and values define acceptance policy reference, required assurance and decision separation?requirement
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support acceptance policy reference, required assurance and decision separation?decision
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may acceptance policy reference, required assurance and decision separation be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?exception
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • Acceptance policy reference, required assurance and decision separation recordVersioned evidence-bearing attestation record for acceptance policy reference, required assurance and decision separation with statement, suite, event and knowledge time, provenance and disclosure marking.
actors-authority-keys-and-trust-materialActors, authority, keys and trust material2 layers

References issuers, holders, provers, verifiers and versioned verification material.

actor-roles-authority-and-bindingActor roles, authority and binding2 findings

Keeps external identity and role-specific authority explicit.

issuer-attester-holder-prover-subject-verifier-and-relying-party-reference

Issuer, attester, holder, prover, subject, verifier and relying-party reference

External actor identifiers, protocol roles, subject relation, holder binding, delegation and role validity intervals.

Questions
  1. What identities, roles, versions, scope and values define issuer, attester, holder, prover, subject, verifier and relying-party reference?ownership
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support issuer, attester, holder, prover, subject, verifier and relying-party reference?provenance
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may issuer, attester, holder, prover, subject, verifier and relying-party reference be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?privacy
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • Issuer, attester, holder, prover, subject, verifier and relying-party reference recordVersioned evidence-bearing attestation record for issuer, attester, holder, prover, subject, verifier and relying-party reference with statement, suite, event and knowledge time, provenance and disclosure marking.
claim-authority-delegation-proof-purpose-and-verification-method-control

Claim authority, delegation, proof purpose and verification-method control

Authority source, delegation scope, proof purpose, controller relation, verification method and authority validity evidence.

Questions
  1. What identities, roles, versions, scope and values define claim authority, delegation, proof purpose and verification-method control?classification
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support claim authority, delegation, proof purpose and verification-method control?quality
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may claim authority, delegation, proof purpose and verification-method control be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?security
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • Claim authority, delegation, proof purpose and verification-method control recordVersioned evidence-bearing attestation record for claim authority, delegation, proof purpose and verification-method control with statement, suite, event and knowledge time, provenance and disclosure marking.
verification-material-status-and-trustVerification material, status and trust2 findings

Pins keys, parameters and status observations without importing key or trust registries.

verification-key-method-identifier-parameters-validity-and-resolution

Verification key, method identifier, parameters, validity and resolution

External key or method identifier, type, controller, public material digest, algorithm parameters, resolver, valid interval and resolution evidence.

Questions
  1. What identities, roles, versions, scope and values define verification key, method identifier, parameters, validity and resolution?composition
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support verification key, method identifier, parameters, validity and resolution?measurement
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may verification key, method identifier, parameters, validity and resolution be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?validation
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • Verification key, method identifier, parameters, validity and resolution recordVersioned evidence-bearing attestation record for verification key, method identifier, parameters, validity and resolution with statement, suite, event and knowledge time, provenance and disclosure marking.
credential-proof-key-and-status-source-revocation-suspension-and-freshness

Credential, proof, key and status source, revocation, suspension and freshness

External credential and status references, status purpose, observed status, source authority, retrieval time, validity, cache age and error state.

Questions
  1. What identities, roles, versions, scope and values define credential, proof, key and status source, revocation, suspension and freshness?state
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support credential, proof, key and status source, revocation, suspension and freshness?lifecycle
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may credential, proof, key and status source, revocation, suspension and freshness be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?retention
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • Credential, proof, key and status source, revocation, suspension and freshness recordVersioned evidence-bearing attestation record for credential, proof, key and status source, revocation, suspension and freshness with statement, suite, event and knowledge time, provenance and disclosure marking.
proof-system-circuit-commitments-and-privacy-propertiesProof system, circuit, commitments and privacy properties2 layers

Pins the cryptographic system, formal relation and privacy claims required to interpret a proof.

public-inputs-commitments-and-witness-boundaryPublic inputs, commitments and witness boundary2 findings

Records what is revealed and binds undisclosed inputs without storing them.

public-input-challenge-commitment-disclosure-digest-and-context

Public input, challenge, commitment, disclosure digest and context

Typed public inputs, commitments, disclosed values or digests, challenge, domain, audience, context and canonical ordering.

Questions
  1. What identities, roles, versions, scope and values define public input, challenge, commitment, disclosure digest and context?identity
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support public input, challenge, commitment, disclosure digest and context?evidence
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may public input, challenge, commitment, disclosure digest and context be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?validation
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • Public input, challenge, commitment, disclosure digest and context recordVersioned evidence-bearing attestation record for public input, challenge, commitment, disclosure digest and context with statement, suite, event and knowledge time, provenance and disclosure marking.
private-input-witness-secret-and-non-retention-boundary

Private input, witness, secret and non-retention boundary

Witness class and relation only, prohibition on stored value, prover-side master reference if allowed, zeroization or non-retention claim and audit evidence.

Questions
  1. What identities, roles, versions, scope and values define private input, witness, secret and non-retention boundary?definition
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support private input, witness, secret and non-retention boundary?authority
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may private input, witness, secret and non-retention boundary be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?interoperability
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • Private input, witness, secret and non-retention boundary recordVersioned evidence-bearing attestation record for private input, witness, secret and non-retention boundary with statement, suite, event and knowledge time, provenance and disclosure marking.
proof-system-suite-circuit-and-setupProof system, suite, circuit and setup2 findings

Pins all inputs needed to interpret security claims and verification.

proof-system-cryptosuite-algorithm-group-curve-and-security-parameter

Proof system, cryptosuite, algorithm, group, curve and security parameter

Named system and version, cryptosuite, algorithm identifiers, group or curve, security parameter, implementation profile and deprecation status.

Questions
  1. What identities, roles, versions, scope and values define proof system, cryptosuite, algorithm, group, curve and security parameter?relationship
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support proof system, cryptosuite, algorithm, group, curve and security parameter?temporal
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may proof system, cryptosuite, algorithm, group, curve and security parameter be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?access
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • Proof system, cryptosuite, algorithm, group, curve and security parameter recordVersioned evidence-bearing attestation record for proof system, cryptosuite, algorithm, group, curve and security parameter with statement, suite, event and knowledge time, provenance and disclosure marking.
circuit-relation-verification-key-srs-setup-ceremony-and-assumptions

Circuit, relation, verification key, SRS, setup ceremony and assumptions

Circuit or relation digest and version, verification key, structured reference string, setup kind and ceremony evidence, assumptions and compatibility constraints.

Questions
  1. What identities, roles, versions, scope and values define circuit, relation, verification key, srs, setup ceremony and assumptions?requirement
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support circuit, relation, verification key, srs, setup ceremony and assumptions?decision
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may circuit, relation, verification key, srs, setup ceremony and assumptions be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?exception
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • Circuit, relation, verification key, SRS, setup ceremony and assumptions recordVersioned evidence-bearing attestation record for circuit, relation, verification key, srs, setup ceremony and assumptions with statement, suite, event and knowledge time, provenance and disclosure marking.
proof-presentation-transcript-and-verificationProof, presentation, transcript and verification2 layers

Binds anti-replay context, proof material and attributable verification outcomes.

challenge-domain-session-and-holder-bindingChallenge, domain, session and holder binding2 findings

Prevents replay and cross-context proof substitution.

nonce-challenge-domain-audience-client-session-and-expiry-binding

Nonce, challenge, domain, audience, client, session and expiry binding

Fresh nonce or challenge, verifier domain, audience, client identifier, session, issue and expiry time, one-time-use state and entropy evidence.

Questions
  1. What identities, roles, versions, scope and values define nonce, challenge, domain, audience, client, session and expiry binding?ownership
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support nonce, challenge, domain, audience, client, session and expiry binding?provenance
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may nonce, challenge, domain, audience, client, session and expiry binding be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?privacy
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • Nonce, challenge, domain, audience, client, session and expiry binding recordVersioned evidence-bearing attestation record for nonce, challenge, domain, audience, client, session and expiry binding with statement, suite, event and knowledge time, provenance and disclosure marking.
holder-binding-key-binding-possession-and-replay-correlation-control

Holder binding, key binding, possession and replay-correlation control

Binding method, key or nonce reference, possession proof, replay cache reference, verifier-specific context, correlation risk and mitigation.

Questions
  1. What identities, roles, versions, scope and values define holder binding, key binding, possession and replay-correlation control?classification
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support holder binding, key binding, possession and replay-correlation control?quality
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may holder binding, key binding, possession and replay-correlation control be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?security
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • Holder binding, key binding, possession and replay-correlation control recordVersioned evidence-bearing attestation record for holder binding, key binding, possession and replay-correlation control with statement, suite, event and knowledge time, provenance and disclosure marking.
proof-artifact-processing-and-resultProof artifact, processing and result2 findings

Preserves inputs, outputs and errors for independent review.

proof-presentation-derived-proof-disclosure-set-format-and-integrity

Proof, presentation, derived proof, disclosure set, format and integrity

Proof value or external artifact, format and media type, derived-proof profile, disclosure manifest, host and request binding, digest and size.

Questions
  1. What identities, roles, versions, scope and values define proof, presentation, derived proof, disclosure set, format and integrity?composition
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support proof, presentation, derived proof, disclosure set, format and integrity?measurement
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may proof, presentation, derived proof, disclosure set, format and integrity be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?validation
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • Proof, presentation, derived proof, disclosure set, format and integrity recordVersioned evidence-bearing attestation record for proof, presentation, derived proof, disclosure set, format and integrity with statement, suite, event and knowledge time, provenance and disclosure marking.
verification-activity-inputs-checks-result-errors-time-and-evidence

Verification activity, inputs, checks, result, errors, time and evidence

Verifier implementation and version, resolved inputs, algorithm checks, status and freshness checks, valid or invalid result, structured errors and provenance.

Questions
  1. What identities, roles, versions, scope and values define verification activity, inputs, checks, result, errors, time and evidence?state
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support verification activity, inputs, checks, result, errors, time and evidence?lifecycle
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may verification activity, inputs, checks, result, errors, time and evidence be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?retention
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • Verification activity, inputs, checks, result, errors, time and evidence recordVersioned evidence-bearing attestation record for verification activity, inputs, checks, result, errors, time and evidence with statement, suite, event and knowledge time, provenance and disclosure marking.
disclosure-privacy-status-and-lifecycleDisclosure, privacy, status and lifecycle2 layers

Makes disclosure and correlation effects visible and preserves time-qualified validity.

disclosure-minimization-linkability-and-leakageDisclosure minimization, linkability and leakage2 findings

Records intended and observed privacy properties.

requested-disclosed-derived-undisclosed-and-inferred-claim-manifest

Requested, disclosed, derived, undisclosed and inferred claim manifest

Claim paths or predicate IDs by category, necessity, derivation, value or commitment visibility, verifier purpose and minimization justification.

Questions
  1. What identities, roles, versions, scope and values define requested, disclosed, derived, undisclosed and inferred claim manifest?identity
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support requested, disclosed, derived, undisclosed and inferred claim manifest?evidence
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may requested, disclosed, derived, undisclosed and inferred claim manifest be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?validation
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • Requested, disclosed, derived, undisclosed and inferred claim manifest recordVersioned evidence-bearing attestation record for requested, disclosed, derived, undisclosed and inferred claim manifest with statement, suite, event and knowledge time, provenance and disclosure marking.
zero-knowledge-selective-disclosure-unlinkability-anonymity-and-leakage-assessment

Zero knowledge, selective disclosure, unlinkability, anonymity and leakage assessment

Property claimed, proof-system basis, threat model, verifier collusion assumptions, linkable fields, status-channel leakage, residual inference and confidence.

Questions
  1. What identities, roles, versions, scope and values define zero knowledge, selective disclosure, unlinkability, anonymity and leakage assessment?definition
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support zero knowledge, selective disclosure, unlinkability, anonymity and leakage assessment?authority
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may zero knowledge, selective disclosure, unlinkability, anonymity and leakage assessment be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?interoperability
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • Zero knowledge, selective disclosure, unlinkability, anonymity and leakage assessment recordVersioned evidence-bearing attestation record for zero knowledge, selective disclosure, unlinkability, anonymity and leakage assessment with statement, suite, event and knowledge time, provenance and disclosure marking.
validity-status-change-and-event-historyValidity, status change and event history2 findings

Separates cryptographic, credential and policy time.

proof-created-presented-received-verified-observed-and-knowledge-time

Proof created, presented, received, verified, observed and knowledge time

Distinct RFC 3339 event times, source clock, accuracy, ordering, observation and ingestion time, and later knowledge correction.

Questions
  1. What identities, roles, versions, scope and values define proof created, presented, received, verified, observed and knowledge time?relationship
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support proof created, presented, received, verified, observed and knowledge time?temporal
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may proof created, presented, received, verified, observed and knowledge time be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?access
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • Proof created, presented, received, verified, observed and knowledge time recordVersioned evidence-bearing attestation record for proof created, presented, received, verified, observed and knowledge time with statement, suite, event and knowledge time, provenance and disclosure marking.
credential-proof-key-policy-and-trust-status-change-effect

Credential, proof, key, policy and trust status change effect

External status event, purpose, source, prior and next state, effective time, reversibility, affected verification and re-evaluation requirement.

Questions
  1. What identities, roles, versions, scope and values define credential, proof, key, policy and trust status change effect?requirement
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support credential, proof, key, policy and trust status change effect?decision
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may credential, proof, key, policy and trust status change effect be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?exception
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • Credential, proof, key, policy and trust status change effect recordVersioned evidence-bearing attestation record for credential, proof, key, policy and trust status change effect with statement, suite, event and knowledge time, provenance and disclosure marking.
interoperability-provenance-access-and-agent-governanceInteroperability, provenance, access and agent governance2 layers

Provides versioned projections, reproducibility and safe autonomous handling.

format-protocol-crosswalk-and-reproducibilityFormat, protocol, crosswalk and reproducibility2 findings

Maps proof families with explicit information loss and environment evidence.

vc-data-integrity-bbs-sd-jwt-openid4vp-and-zkp-crosswalk

VC Data Integrity, BBS, SD-JWT, OpenID4VP and ZKP crosswalk

Source and target versions, field and event mappings, canonicalization, holder binding, disclosure semantics, omissions and round-trip limits.

Questions
  1. What identities, roles, versions, scope and values define vc data integrity, bbs, sd-jwt, openid4vp and zkp crosswalk?ownership
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support vc data integrity, bbs, sd-jwt, openid4vp and zkp crosswalk?provenance
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may vc data integrity, bbs, sd-jwt, openid4vp and zkp crosswalk be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?privacy
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • VC Data Integrity, BBS, SD-JWT, OpenID4VP and ZKP crosswalk recordVersioned evidence-bearing attestation record for vc data integrity, bbs, sd-jwt, openid4vp and zkp crosswalk with statement, suite, event and knowledge time, provenance and disclosure marking.
implementation-build-test-vector-verifier-environment-and-reproducibility

Implementation, build, test vector, verifier environment and reproducibility

Implementation and dependency versions, build digest, platform, test-vector set, conformance result, execution evidence and reproducibility status.

Questions
  1. What identities, roles, versions, scope and values define implementation, build, test vector, verifier environment and reproducibility?classification
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support implementation, build, test vector, verifier environment and reproducibility?quality
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may implementation, build, test vector, verifier environment and reproducibility be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?security
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • Implementation, build, test vector, verifier environment and reproducibility recordVersioned evidence-bearing attestation record for implementation, build, test vector, verifier environment and reproducibility with statement, suite, event and knowledge time, provenance and disclosure marking.
purpose-bound-access-retention-and-safe-operationsPurpose-bound access, retention and safe operations2 findings

Controls sensitive proof metadata and agent changes.

prover-verifier-auditor-regulator-public-and-analytical-view

Prover, verifier, auditor, regulator, public and analytical view

Audience, purpose, authority, permitted fields, witness exclusion, pseudonymization, correlation budget, expiry, disclosure event and re-identification risk.

Questions
  1. What identities, roles, versions, scope and values define prover, verifier, auditor, regulator, public and analytical view?composition
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support prover, verifier, auditor, regulator, public and analytical view?measurement
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may prover, verifier, auditor, regulator, public and analytical view be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?validation
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • Prover, verifier, auditor, regulator, public and analytical view recordVersioned evidence-bearing attestation record for prover, verifier, auditor, regulator, public and analytical view with statement, suite, event and knowledge time, provenance and disclosure marking.
agent-authority-operation-prewrite-postwrite-concurrency-recovery-and-retention

Agent authority, operation, pre-write, post-write, concurrency, recovery and retention

Actor and agent, delegated authority, operation, expected head, validation, idempotency, confirmation class, outcome, rollback, deletion and audit event.

Questions
  1. What identities, roles, versions, scope and values define agent authority, operation, pre-write, post-write, concurrency, recovery and retention?state
    Expected answer
    • identifiers and roles
    • versions and profiles
    • scope and values
    • explicit unknowns
  2. Which statement, authority, cryptographic evidence, event time and knowledge time support agent authority, operation, pre-write, post-write, concurrency, recovery and retention?lifecycle
    Expected answer
    • statement and authority
    • proof or status evidence
    • event and knowledge time
    • assumptions
  3. How may agent authority, operation, pre-write, post-write, concurrency, recovery and retention be validated, contested, corrected, superseded, retained and disclosed without exposing a witness or equating verification with authorization?retention
    Expected answer
    • validation
    • contest and correction
    • successor history
    • witness exclusion
    • decision boundary
Artifacts
  • Agent authority, operation, pre-write, post-write, concurrency, recovery and retention recordVersioned evidence-bearing attestation record for agent authority, operation, pre-write, post-write, concurrency, recovery and retention with statement, suite, event and knowledge time, provenance and disclosure marking.

Publication holds

  • Claude and Grok timed out during their bounded attempts, so independent external review is absent and explicitly waived for this published reviewable draft.
  • No approved relation row establishes the parent-child contract with WM-XCT-034 Digital Signature / Proof.
  • Proof-system-specific algebra, circuit languages, hardware attestation, regulatory profiles and certified security levels require specialist review.
  • BBS remains a Candidate Recommendation Draft and ZKProof Community Reference remains an incomplete 0.x reference; production profiles require explicit maturity gates.
  • Certified VC Data Integrity, BBS, SD-JWT, OpenID4VP and ZKP crosswalks and conformance fixtures remain unverified.
  • Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft.

Deferred research

  • Approve the WM-XCT-006 and WM-XCT-034 division, relation direction, cardinality and inherited responsibilities.
  • Develop proof-system profiles for predicates, circuits, public inputs, setup, verification keys, security assumptions and upgrade paths.
  • Create fixtures for replay, wrong audience, stale status, revoked credential, invalid proof, key rotation, selective disclosure, verifier collusion and re-evaluation.
  • Validate certified cross-format projections with statement, authority, privacy, time, access, information-loss and round-trip tests.