{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-xct-006","code":"wm-xct-006-verification-zk-attestation","url":"https://ver.cy/models/wm-xct-006-verification-zk-attestation/","name":"Verification / ZK Attestation","alternateNames":["S6"],"kind":"world-model","status":"published","version":"0.3.0-research.1","language":"en","classifiers":{"family":"World Models","category":"Cross-cutting context","entryKind":"mixin","plane":"","domain":["XCT.PRF"],"industry":["Cross-industry"],"navPath":"NAV.XCT.PRF","tags":["verification","zk","attestation","xct.prf"],"facets":{}},"whatItIs":"Owns the host proof-binding identity, statement and predicate, verifier request, public inputs and commitments, proof-system and cryptosuite profile, challenge and audience binding, proof or presentation reference, disclosure manifest, verification activity and result, privacy-property assessment, status observations and lifecycle. Credentials, actors, subjects, keys, trust registries, policies, decisions, source datasets and audit logs remain external.","purpose":"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.","scope":{"in":["Host binding, statement, predicate schema and canonical form, request, purpose, audience, public inputs, commitments and witness non-retention boundary","Actor roles and authority references, proof system, cryptosuite, circuit, verification key, setup, challenge, holder binding, proof, presentation and verification result","Disclosure minimization, zero-knowledge and unlinkability claims, status and freshness, time, interoperability, access, retention and safe operations"],"out":["Credential, person, organization, subject, key, trust registry, authorization policy, relying-party decision, source dataset or audit-log master lifecycle","Persisting witnesses, private inputs, holder secrets or undisclosed claims and implementing cryptographic prover or verifier algorithms","Universal identity truth, authorization or legal-effect decisions, guaranteed zero knowledge, unsupported algorithm fallback or certified cross-format equivalence"],"boundaries":[{"neighbor":"Credential / Claim","distinction":"A credential or claim owns asserted content and issuer authority; this mixin binds a selected statement and proof or verification evidence to a host."},{"neighbor":"Digital Signature / Proof","distinction":"WM-XCT-034 can provide a generic signature or proof artifact mixin; this model adds verifier request, formal predicate, privacy properties, challenge, status and verification-result semantics for attestation use."},{"neighbor":"Key / Verification Method / Trust Registry","distinction":"Keys, controllers, trust anchors and status sources remain external masters; the attestation pins their identifiers, versions and observations."},{"neighbor":"Authorization / Eligibility / Decision","distinction":"Cryptographic verification is evidence for an external policy decision and never establishes authorization, eligibility or business acceptance by itself."},{"neighbor":"Audit Log / Evidence Record","distinction":"This mixin owns proof-specific provenance and result evidence but delegates generic append-only audit persistence and organization-wide retention."}]},"distinguishingFeatures":["Models the verifier-side binding of a statement, proof and result, not the credential or key it relies on.","Records only the class of private inputs and never stores the witness itself.","Keeps cryptographic validity, issuer trust, status and business acceptance as separate outcomes.","Qualifies privacy properties by named proof system, version and threat model."],"structure":{"bundles":[{"id":"attestation-identity-statement-and-request","name":"Attestation identity, statement and request","description":"Identifies the proof binding and defines exactly what statement a verifier requests.","layers":[{"id":"binding-identity-host-and-statement","name":"Binding identity, host and statement","description":"Stable identity and unambiguous subject matter for the attestation.","findings":[{"id":"attestation-binding-identifier-host-record-purpose-and-version","name":"Attestation binding identifier, host record, purpose and version","description":"Mixin identifier, host record and path, binding purpose, profile, version, predecessor, lifecycle state and authoritative registry.","questions":[{"text":"What identities, roles, versions, scope and values define attestation binding identifier, host record, purpose and version?","id":"attestation-binding-identifier-host-record-purpose-and-version-q01","kind":"identity"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support attestation binding identifier, host record, purpose and version?","id":"attestation-binding-identifier-host-record-purpose-and-version-q02","kind":"evidence"},{"text":"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?","id":"attestation-binding-identifier-host-record-purpose-and-version-q03","kind":"validation"}]},{"id":"statement-predicate-relation-public-instance-schema-and-canonical-form","name":"Statement, predicate, relation, public instance, schema and canonical form","description":"Predicate identifier and version, formal relation, public instance, parameterization, schema, canonical bytes or digest and semantic description.","questions":[{"text":"What identities, roles, versions, scope and values define statement, predicate, relation, public instance, schema and canonical form?","id":"statement-predicate-relation-public-instance-schema-and-canonical-form-q01","kind":"definition"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support statement, predicate, relation, public instance, schema and canonical form?","id":"statement-predicate-relation-public-instance-schema-and-canonical-form-q02","kind":"authority"},{"text":"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?","id":"statement-predicate-relation-public-instance-schema-and-canonical-form-q03","kind":"interoperability"}]}]},{"id":"verifier-request-purpose-and-acceptance-boundary","name":"Verifier request, purpose and acceptance boundary","description":"Captures requested evidence without treating verification as authorization.","findings":[{"id":"verification-request-identifier-verifier-audience-purpose-and-requested-claims","name":"Verification request identifier, verifier, audience, purpose and requested claims","description":"Request identity, external verifier, audience, purpose, requested predicates or disclosures, format choices, expiry and request-object digest.","questions":[{"text":"What identities, roles, versions, scope and values define verification request identifier, verifier, audience, purpose and requested claims?","id":"verification-request-identifier-verifier-audience-purpose-and-requested-claims-q01","kind":"relationship"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support verification request identifier, verifier, audience, purpose and requested claims?","id":"verification-request-identifier-verifier-audience-purpose-and-requested-claims-q02","kind":"temporal"},{"text":"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?","id":"verification-request-identifier-verifier-audience-purpose-and-requested-claims-q03","kind":"access"}]},{"id":"acceptance-policy-reference-required-assurance-and-decision-separation","name":"Acceptance policy reference, required assurance and decision separation","description":"External policy identifier and version, required proof and freshness properties, exception path and explicit separation of cryptographic result from relying-party decision.","questions":[{"text":"What identities, roles, versions, scope and values define acceptance policy reference, required assurance and decision separation?","id":"acceptance-policy-reference-required-assurance-and-decision-separation-q01","kind":"requirement"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support acceptance policy reference, required assurance and decision separation?","id":"acceptance-policy-reference-required-assurance-and-decision-separation-q02","kind":"decision"},{"text":"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?","id":"acceptance-policy-reference-required-assurance-and-decision-separation-q03","kind":"exception"}]}]}]},{"id":"actors-authority-keys-and-trust-material","name":"Actors, authority, keys and trust material","description":"References issuers, holders, provers, verifiers and versioned verification material.","layers":[{"id":"actor-roles-authority-and-binding","name":"Actor roles, authority and binding","description":"Keeps external identity and role-specific authority explicit.","findings":[{"id":"issuer-attester-holder-prover-subject-verifier-and-relying-party-reference","name":"Issuer, attester, holder, prover, subject, verifier and relying-party reference","description":"External actor identifiers, protocol roles, subject relation, holder binding, delegation and role validity intervals.","questions":[{"text":"What identities, roles, versions, scope and values define issuer, attester, holder, prover, subject, verifier and relying-party reference?","id":"issuer-attester-holder-prover-subject-verifier-and-relying-party-reference-q01","kind":"ownership"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support issuer, attester, holder, prover, subject, verifier and relying-party reference?","id":"issuer-attester-holder-prover-subject-verifier-and-relying-party-reference-q02","kind":"provenance"},{"text":"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?","id":"issuer-attester-holder-prover-subject-verifier-and-relying-party-reference-q03","kind":"privacy"}]},{"id":"claim-authority-delegation-proof-purpose-and-verification-method-control","name":"Claim authority, delegation, proof purpose and verification-method control","description":"Authority source, delegation scope, proof purpose, controller relation, verification method and authority validity evidence.","questions":[{"text":"What identities, roles, versions, scope and values define claim authority, delegation, proof purpose and verification-method control?","id":"claim-authority-delegation-proof-purpose-and-verification-method-control-q01","kind":"classification"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support claim authority, delegation, proof purpose and verification-method control?","id":"claim-authority-delegation-proof-purpose-and-verification-method-control-q02","kind":"quality"},{"text":"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?","id":"claim-authority-delegation-proof-purpose-and-verification-method-control-q03","kind":"security"}]}]},{"id":"verification-material-status-and-trust","name":"Verification material, status and trust","description":"Pins keys, parameters and status observations without importing key or trust registries.","findings":[{"id":"verification-key-method-identifier-parameters-validity-and-resolution","name":"Verification key, method identifier, parameters, validity and resolution","description":"External key or method identifier, type, controller, public material digest, algorithm parameters, resolver, valid interval and resolution evidence.","questions":[{"text":"What identities, roles, versions, scope and values define verification key, method identifier, parameters, validity and resolution?","id":"verification-key-method-identifier-parameters-validity-and-resolution-q01","kind":"composition"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support verification key, method identifier, parameters, validity and resolution?","id":"verification-key-method-identifier-parameters-validity-and-resolution-q02","kind":"measurement"},{"text":"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?","id":"verification-key-method-identifier-parameters-validity-and-resolution-q03","kind":"validation"}]},{"id":"credential-proof-key-and-status-source-revocation-suspension-and-freshness","name":"Credential, proof, key and status source, revocation, suspension and freshness","description":"External credential and status references, status purpose, observed status, source authority, retrieval time, validity, cache age and error state.","questions":[{"text":"What identities, roles, versions, scope and values define credential, proof, key and status source, revocation, suspension and freshness?","id":"credential-proof-key-and-status-source-revocation-suspension-and-freshness-q01","kind":"state"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support credential, proof, key and status source, revocation, suspension and freshness?","id":"credential-proof-key-and-status-source-revocation-suspension-and-freshness-q02","kind":"lifecycle"},{"text":"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?","id":"credential-proof-key-and-status-source-revocation-suspension-and-freshness-q03","kind":"retention"}]}]}]},{"id":"proof-system-circuit-commitments-and-privacy-properties","name":"Proof system, circuit, commitments and privacy properties","description":"Pins the cryptographic system, formal relation and privacy claims required to interpret a proof.","layers":[{"id":"public-inputs-commitments-and-witness-boundary","name":"Public inputs, commitments and witness boundary","description":"Records what is revealed and binds undisclosed inputs without storing them.","findings":[{"id":"public-input-challenge-commitment-disclosure-digest-and-context","name":"Public input, challenge, commitment, disclosure digest and context","description":"Typed public inputs, commitments, disclosed values or digests, challenge, domain, audience, context and canonical ordering.","questions":[{"text":"What identities, roles, versions, scope and values define public input, challenge, commitment, disclosure digest and context?","id":"public-input-challenge-commitment-disclosure-digest-and-context-q01","kind":"identity"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support public input, challenge, commitment, disclosure digest and context?","id":"public-input-challenge-commitment-disclosure-digest-and-context-q02","kind":"evidence"},{"text":"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?","id":"public-input-challenge-commitment-disclosure-digest-and-context-q03","kind":"validation"}]},{"id":"private-input-witness-secret-and-non-retention-boundary","name":"Private input, witness, secret and non-retention boundary","description":"Witness class and relation only, prohibition on stored value, prover-side master reference if allowed, zeroization or non-retention claim and audit evidence.","questions":[{"text":"What identities, roles, versions, scope and values define private input, witness, secret and non-retention boundary?","id":"private-input-witness-secret-and-non-retention-boundary-q01","kind":"definition"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support private input, witness, secret and non-retention boundary?","id":"private-input-witness-secret-and-non-retention-boundary-q02","kind":"authority"},{"text":"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?","id":"private-input-witness-secret-and-non-retention-boundary-q03","kind":"interoperability"}]}]},{"id":"proof-system-suite-circuit-and-setup","name":"Proof system, suite, circuit and setup","description":"Pins all inputs needed to interpret security claims and verification.","findings":[{"id":"proof-system-cryptosuite-algorithm-group-curve-and-security-parameter","name":"Proof system, cryptosuite, algorithm, group, curve and security parameter","description":"Named system and version, cryptosuite, algorithm identifiers, group or curve, security parameter, implementation profile and deprecation status.","questions":[{"text":"What identities, roles, versions, scope and values define proof system, cryptosuite, algorithm, group, curve and security parameter?","id":"proof-system-cryptosuite-algorithm-group-curve-and-security-parameter-q01","kind":"relationship"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support proof system, cryptosuite, algorithm, group, curve and security parameter?","id":"proof-system-cryptosuite-algorithm-group-curve-and-security-parameter-q02","kind":"temporal"},{"text":"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?","id":"proof-system-cryptosuite-algorithm-group-curve-and-security-parameter-q03","kind":"access"}]},{"id":"circuit-relation-verification-key-srs-setup-ceremony-and-assumptions","name":"Circuit, relation, verification key, SRS, setup ceremony and assumptions","description":"Circuit or relation digest and version, verification key, structured reference string, setup kind and ceremony evidence, assumptions and compatibility constraints.","questions":[{"text":"What identities, roles, versions, scope and values define circuit, relation, verification key, srs, setup ceremony and assumptions?","id":"circuit-relation-verification-key-srs-setup-ceremony-and-assumptions-q01","kind":"requirement"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support circuit, relation, verification key, srs, setup ceremony and assumptions?","id":"circuit-relation-verification-key-srs-setup-ceremony-and-assumptions-q02","kind":"decision"},{"text":"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?","id":"circuit-relation-verification-key-srs-setup-ceremony-and-assumptions-q03","kind":"exception"}]}]}]},{"id":"proof-presentation-transcript-and-verification","name":"Proof, presentation, transcript and verification","description":"Binds anti-replay context, proof material and attributable verification outcomes.","layers":[{"id":"challenge-domain-session-and-holder-binding","name":"Challenge, domain, session and holder binding","description":"Prevents replay and cross-context proof substitution.","findings":[{"id":"nonce-challenge-domain-audience-client-session-and-expiry-binding","name":"Nonce, challenge, domain, audience, client, session and expiry binding","description":"Fresh nonce or challenge, verifier domain, audience, client identifier, session, issue and expiry time, one-time-use state and entropy evidence.","questions":[{"text":"What identities, roles, versions, scope and values define nonce, challenge, domain, audience, client, session and expiry binding?","id":"nonce-challenge-domain-audience-client-session-and-expiry-binding-q01","kind":"ownership"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support nonce, challenge, domain, audience, client, session and expiry binding?","id":"nonce-challenge-domain-audience-client-session-and-expiry-binding-q02","kind":"provenance"},{"text":"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?","id":"nonce-challenge-domain-audience-client-session-and-expiry-binding-q03","kind":"privacy"}]},{"id":"holder-binding-key-binding-possession-and-replay-correlation-control","name":"Holder binding, key binding, possession and replay-correlation control","description":"Binding method, key or nonce reference, possession proof, replay cache reference, verifier-specific context, correlation risk and mitigation.","questions":[{"text":"What identities, roles, versions, scope and values define holder binding, key binding, possession and replay-correlation control?","id":"holder-binding-key-binding-possession-and-replay-correlation-control-q01","kind":"classification"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support holder binding, key binding, possession and replay-correlation control?","id":"holder-binding-key-binding-possession-and-replay-correlation-control-q02","kind":"quality"},{"text":"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?","id":"holder-binding-key-binding-possession-and-replay-correlation-control-q03","kind":"security"}]}]},{"id":"proof-artifact-processing-and-result","name":"Proof artifact, processing and result","description":"Preserves inputs, outputs and errors for independent review.","findings":[{"id":"proof-presentation-derived-proof-disclosure-set-format-and-integrity","name":"Proof, presentation, derived proof, disclosure set, format and integrity","description":"Proof value or external artifact, format and media type, derived-proof profile, disclosure manifest, host and request binding, digest and size.","questions":[{"text":"What identities, roles, versions, scope and values define proof, presentation, derived proof, disclosure set, format and integrity?","id":"proof-presentation-derived-proof-disclosure-set-format-and-integrity-q01","kind":"composition"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support proof, presentation, derived proof, disclosure set, format and integrity?","id":"proof-presentation-derived-proof-disclosure-set-format-and-integrity-q02","kind":"measurement"},{"text":"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?","id":"proof-presentation-derived-proof-disclosure-set-format-and-integrity-q03","kind":"validation"}]},{"id":"verification-activity-inputs-checks-result-errors-time-and-evidence","name":"Verification activity, inputs, checks, result, errors, time and evidence","description":"Verifier implementation and version, resolved inputs, algorithm checks, status and freshness checks, valid or invalid result, structured errors and provenance.","questions":[{"text":"What identities, roles, versions, scope and values define verification activity, inputs, checks, result, errors, time and evidence?","id":"verification-activity-inputs-checks-result-errors-time-and-evidence-q01","kind":"state"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support verification activity, inputs, checks, result, errors, time and evidence?","id":"verification-activity-inputs-checks-result-errors-time-and-evidence-q02","kind":"lifecycle"},{"text":"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?","id":"verification-activity-inputs-checks-result-errors-time-and-evidence-q03","kind":"retention"}]}]}]},{"id":"disclosure-privacy-status-and-lifecycle","name":"Disclosure, privacy, status and lifecycle","description":"Makes disclosure and correlation effects visible and preserves time-qualified validity.","layers":[{"id":"disclosure-minimization-linkability-and-leakage","name":"Disclosure minimization, linkability and leakage","description":"Records intended and observed privacy properties.","findings":[{"id":"requested-disclosed-derived-undisclosed-and-inferred-claim-manifest","name":"Requested, disclosed, derived, undisclosed and inferred claim manifest","description":"Claim paths or predicate IDs by category, necessity, derivation, value or commitment visibility, verifier purpose and minimization justification.","questions":[{"text":"What identities, roles, versions, scope and values define requested, disclosed, derived, undisclosed and inferred claim manifest?","id":"requested-disclosed-derived-undisclosed-and-inferred-claim-manifest-q01","kind":"identity"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support requested, disclosed, derived, undisclosed and inferred claim manifest?","id":"requested-disclosed-derived-undisclosed-and-inferred-claim-manifest-q02","kind":"evidence"},{"text":"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?","id":"requested-disclosed-derived-undisclosed-and-inferred-claim-manifest-q03","kind":"validation"}]},{"id":"zero-knowledge-selective-disclosure-unlinkability-anonymity-and-leakage-assessment","name":"Zero knowledge, selective disclosure, unlinkability, anonymity and leakage assessment","description":"Property claimed, proof-system basis, threat model, verifier collusion assumptions, linkable fields, status-channel leakage, residual inference and confidence.","questions":[{"text":"What identities, roles, versions, scope and values define zero knowledge, selective disclosure, unlinkability, anonymity and leakage assessment?","id":"zero-knowledge-selective-disclosure-unlinkability-anonymity-and-leakage-assessment-q01","kind":"definition"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support zero knowledge, selective disclosure, unlinkability, anonymity and leakage assessment?","id":"zero-knowledge-selective-disclosure-unlinkability-anonymity-and-leakage-assessment-q02","kind":"authority"},{"text":"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?","id":"zero-knowledge-selective-disclosure-unlinkability-anonymity-and-leakage-assessment-q03","kind":"interoperability"}]}]},{"id":"validity-status-change-and-event-history","name":"Validity, status change and event history","description":"Separates cryptographic, credential and policy time.","findings":[{"id":"proof-created-presented-received-verified-observed-and-knowledge-time","name":"Proof created, presented, received, verified, observed and knowledge time","description":"Distinct RFC 3339 event times, source clock, accuracy, ordering, observation and ingestion time, and later knowledge correction.","questions":[{"text":"What identities, roles, versions, scope and values define proof created, presented, received, verified, observed and knowledge time?","id":"proof-created-presented-received-verified-observed-and-knowledge-time-q01","kind":"relationship"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support proof created, presented, received, verified, observed and knowledge time?","id":"proof-created-presented-received-verified-observed-and-knowledge-time-q02","kind":"temporal"},{"text":"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?","id":"proof-created-presented-received-verified-observed-and-knowledge-time-q03","kind":"access"}]},{"id":"credential-proof-key-policy-and-trust-status-change-effect","name":"Credential, proof, key, policy and trust status change effect","description":"External status event, purpose, source, prior and next state, effective time, reversibility, affected verification and re-evaluation requirement.","questions":[{"text":"What identities, roles, versions, scope and values define credential, proof, key, policy and trust status change effect?","id":"credential-proof-key-policy-and-trust-status-change-effect-q01","kind":"requirement"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support credential, proof, key, policy and trust status change effect?","id":"credential-proof-key-policy-and-trust-status-change-effect-q02","kind":"decision"},{"text":"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?","id":"credential-proof-key-policy-and-trust-status-change-effect-q03","kind":"exception"}]}]}]},{"id":"interoperability-provenance-access-and-agent-governance","name":"Interoperability, provenance, access and agent governance","description":"Provides versioned projections, reproducibility and safe autonomous handling.","layers":[{"id":"format-protocol-crosswalk-and-reproducibility","name":"Format, protocol, crosswalk and reproducibility","description":"Maps proof families with explicit information loss and environment evidence.","findings":[{"id":"vc-data-integrity-bbs-sd-jwt-openid4vp-and-zkp-crosswalk","name":"VC Data Integrity, BBS, SD-JWT, OpenID4VP and ZKP crosswalk","description":"Source and target versions, field and event mappings, canonicalization, holder binding, disclosure semantics, omissions and round-trip limits.","questions":[{"text":"What identities, roles, versions, scope and values define vc data integrity, bbs, sd-jwt, openid4vp and zkp crosswalk?","id":"vc-data-integrity-bbs-sd-jwt-openid4vp-and-zkp-crosswalk-q01","kind":"ownership"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support vc data integrity, bbs, sd-jwt, openid4vp and zkp crosswalk?","id":"vc-data-integrity-bbs-sd-jwt-openid4vp-and-zkp-crosswalk-q02","kind":"provenance"},{"text":"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?","id":"vc-data-integrity-bbs-sd-jwt-openid4vp-and-zkp-crosswalk-q03","kind":"privacy"}]},{"id":"implementation-build-test-vector-verifier-environment-and-reproducibility","name":"Implementation, build, test vector, verifier environment and reproducibility","description":"Implementation and dependency versions, build digest, platform, test-vector set, conformance result, execution evidence and reproducibility status.","questions":[{"text":"What identities, roles, versions, scope and values define implementation, build, test vector, verifier environment and reproducibility?","id":"implementation-build-test-vector-verifier-environment-and-reproducibility-q01","kind":"classification"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support implementation, build, test vector, verifier environment and reproducibility?","id":"implementation-build-test-vector-verifier-environment-and-reproducibility-q02","kind":"quality"},{"text":"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?","id":"implementation-build-test-vector-verifier-environment-and-reproducibility-q03","kind":"security"}]}]},{"id":"purpose-bound-access-retention-and-safe-operations","name":"Purpose-bound access, retention and safe operations","description":"Controls sensitive proof metadata and agent changes.","findings":[{"id":"prover-verifier-auditor-regulator-public-and-analytical-view","name":"Prover, verifier, auditor, regulator, public and analytical view","description":"Audience, purpose, authority, permitted fields, witness exclusion, pseudonymization, correlation budget, expiry, disclosure event and re-identification risk.","questions":[{"text":"What identities, roles, versions, scope and values define prover, verifier, auditor, regulator, public and analytical view?","id":"prover-verifier-auditor-regulator-public-and-analytical-view-q01","kind":"composition"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support prover, verifier, auditor, regulator, public and analytical view?","id":"prover-verifier-auditor-regulator-public-and-analytical-view-q02","kind":"measurement"},{"text":"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?","id":"prover-verifier-auditor-regulator-public-and-analytical-view-q03","kind":"validation"}]},{"id":"agent-authority-operation-prewrite-postwrite-concurrency-recovery-and-retention","name":"Agent authority, operation, pre-write, post-write, concurrency, recovery and retention","description":"Actor and agent, delegated authority, operation, expected head, validation, idempotency, confirmation class, outcome, rollback, deletion and audit event.","questions":[{"text":"What identities, roles, versions, scope and values define agent authority, operation, pre-write, post-write, concurrency, recovery and retention?","id":"agent-authority-operation-prewrite-postwrite-concurrency-recovery-and-retention-q01","kind":"state"},{"text":"Which statement, authority, cryptographic evidence, event time and knowledge time support agent authority, operation, pre-write, post-write, concurrency, recovery and retention?","id":"agent-authority-operation-prewrite-postwrite-concurrency-recovery-and-retention-q02","kind":"lifecycle"},{"text":"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?","id":"agent-authority-operation-prewrite-postwrite-concurrency-recovery-and-retention-q03","kind":"retention"}]}]}]}]},"agentConduct":{"may":["Create a verification request with a fresh challenge and audience.","Verify a proof with the declared verification material and record the result.","Assess a disclosure manifest against the stated predicate.","Re-evaluate results when a proof system or key is later found weak."],"mustNot":["Persist a witness, holder secret or undisclosed claim.","Treat a valid proof as authorization or eligibility on its own.","Claim zero knowledge or unlinkability without naming the system and assumptions.","Request more attributes than the predicate needs.","Accept a presentation bound to a different challenge or audience."],"requiresHuman":["Choosing or approving a proof system and its trusted setup.","Accepting a verification result for a high-stakes decision such as age or eligibility gates."]},"ethics":{"considerations":["Zero-knowledge checks exist to protect privacy; over-requesting or logging undermines that purpose.","Verifiers can track people by correlating proofs; unlinkability needs design, not assumption.","People without suitable devices or credentials may be excluded from services."],"affectedParties":["Holders proving a claim","Verifiers and relying parties","Issuers of underlying credentials"]},"owners":{"steward":"Dimension identity, owner, verification authority, namespace and accountable privacy steward","roles":[{"name":"Attestation binding owner","responsibilities":["Own host attachment, identity, lifecycle and purpose boundary."]},{"name":"Issuer or attester","responsibilities":["Own claims or credentials and their source authority, validity and status semantics."]},{"name":"Holder or prover","responsibilities":["Control presentations and witnesses and authorize purpose-bound disclosure."]},{"name":"Verifier","responsibilities":["Issue bounded requests, verify according to pinned profiles and record attributable results."]},{"name":"Proof-system and key steward","responsibilities":["Maintain allowed suites, parameters, circuits, verification keys, setup evidence and deprecation."]},{"name":"Relying-party decision owner","responsibilities":["Apply external acceptance policy after verification and own the resulting decision."]},{"name":"Privacy and records steward","responsibilities":["Control minimization, correlation, access, retention, disposition and auditability."]}],"masterSystems":[]},"relations":[{"target":"Host Model","type":"composes","note":"Attach proof and verification semantics without replacing host identity or lifecycle."},{"target":"WM-XCT-034 Digital Signature / Proof","type":"references","note":"Reuse generic signature or proof artifact semantics while adding predicate, privacy, request, status and verification context."},{"target":"Credential, Actor, Key, Trust, Policy and Decision models","type":"references","note":"Resolve source claims, roles, verification material, trust and external acceptance decisions."},{"target":"VC Data Integrity, BBS, SD-JWT and OpenID4VP","type":"aligned","note":"Project credential proof, selective disclosure and presentation protocol data with declared loss."},{"target":"PROV-O and RFC 3339","type":"aligned","note":"Represent accountable generation and verification activities and explicit event times."},{"target":"Credential / Claim","type":"neighbor","note":"A credential or claim owns asserted content and issuer authority; this mixin binds a selected statement and proof or verification evidence to a host."},{"target":"Digital Signature / Proof","type":"neighbor","note":"WM-XCT-034 can provide a generic signature or proof artifact mixin; this model adds verifier request, formal predicate, privacy properties, challenge, status and verification-result semantics for attestation use."},{"target":"Key / Verification Method / Trust Registry","type":"neighbor","note":"Keys, controllers, trust anchors and status sources remain external masters; the attestation pins their identifiers, versions and observations."},{"target":"Authorization / Eligibility / Decision","type":"neighbor","note":"Cryptographic verification is evidence for an external policy decision and never establishes authorization, eligibility or business acceptance by itself."},{"target":"Audit Log / Evidence Record","type":"neighbor","note":"This mixin owns proof-specific provenance and result evidence but delegates generic append-only audit persistence and organization-wide retention."}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system attestation-binding identifier qualified by host record and owning Dimension.","Governed globally resolvable proof or verification IRI bound to the authoritative host and request.","Dimension UUID or ULID when no external identifier exists."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":["A verification record has a statement or predicate, a challenge, a proof reference, a proof-system profile and a result.","It is confused with the credential, a digital signature check or an authorization decision."]},"capabilities":{"applicability":"required","items":["Register attestation binding: Attach stable proof-binding identity and host path without importing the host record.","Define statement and predicate: Pin formal relation, public instance, predicate schema, parameters and canonical representation.","Create verification request: Record verifier, purpose, audience, requested predicates or disclosures, formats, nonce and expiry.","Bind proof system and verification material: Pin cryptosuite, circuit, algorithms, verification key, parameters, setup and assumptions.","Record proof generation: Append a prover-side generation event and proof artifact reference without persisting witness or secret input.","Receive and bind presentation: Record receipt, disclosed and derived claims, holder binding, challenge, domain and presentation integrity.","Verify proof and record result: Record the exact verifier, inputs, checks, status lookups, result and structured errors.","Assess disclosure and privacy properties: Compare requested, disclosed, derived and inferable data and record linkability and leakage claims.","Issue purpose-bound verification view: Create prover, verifier, auditor or regulator projection with minimum data and declared loss.","Correct, supersede, re-evaluate or retire: Append correction, status-triggered re-evaluation, supersession, expiry or tombstone while preserving evidence."]},"hazards":{"applicability":"required","items":["Replay of a proof when challenge binding is missing.","Unsound circuits or setups that accept false statements.","Correlation of holders through reused identifiers in proofs."]},"interfaces":{"applicability":"required","items":["W3C Verifiable Credentials Data Model 2.0.","W3C Data Integrity BBS Cryptosuites.","IETF SD-JWT selective disclosure.","ISO/IEC 18013-5 mobile driving licence presentations."]},"context":{"applicability":"required","items":["Credential trust, legal effect, age or residency predicates and acceptable assurance are jurisdiction and relying-party specific.","W3C and OpenID specifications define technical models and protocols but do not establish universal identity or authorization truth.","NIST and ZKProof materials provide conceptual and deployment guidance, not one mandatory universal ZKP suite."]}},"sources":[{"title":"Verifiable Credentials Data Model v2.0","url":"https://www.w3.org/TR/vc-data-model-2.0/","note":"World Wide Web Consortium"},{"title":"Verifiable Credential Data Integrity 1.0","url":"https://www.w3.org/TR/vc-data-integrity/","note":"World Wide Web Consortium"},{"title":"Bitstring Status List v1.0","url":"https://www.w3.org/TR/vc-bitstring-status-list/","note":"World Wide Web Consortium"},{"title":"Data Integrity BBS Cryptosuites v1.0","url":"https://www.w3.org/TR/vc-di-bbs/","note":"World Wide Web Consortium"},{"title":"Selective Disclosure for JSON Web Tokens","url":"https://www.rfc-editor.org/rfc/rfc9901","note":"Internet Engineering Task Force"},{"title":"OpenID for Verifiable Presentations 1.0","url":"https://openid.net/specs/openid-4-verifiable-presentations-1_0-final.html","note":"OpenID Foundation"},{"title":"Privacy-Enhancing Cryptography: Zero-Knowledge Proofs","url":"https://csrc.nist.gov/projects/pec/zkproof","note":"National Institute of Standards and Technology"},{"title":"ZKProof Community Reference","url":"https://docs.zkproof.org/reference","note":"ZKProof"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"World Wide Web Consortium"},{"title":"Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/rfc/rfc3339","note":"Internet Engineering Task Force"}],"openQuestions":["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.","No independent Claude or Grok result was available; later cryptography and credential review is required before canonical promotion.","No approved relation rows were supplied; the asserted parent-child relationship with WM-XCT-034 Digital Signature / Proof remains a governance hold.","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."],"resources":{"spec":"/models/wm-xct-006-verification-zk-attestation/spec.yaml","agents":"/models/wm-xct-006-verification-zk-attestation/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-xct-006"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-xct-006-verification-zk-attestation/spec.yaml","ver-cy/world-models/card-supplements/wm-xct-006-verification-zk-attestation.json"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-09-06T04:02:28Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"interaction.properties":"Institutional or informational subject: no invented physical properties.","_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}