The `credentialSubject.object.value` of a Vetting Statement: a DTG Verifiable Statement Credential (`StatementCredential`) under the predicate `https://registry.trustoverip.org/dtg/vsc/vetted/1`, issued by a vetter's member DID about an applicant's DID, attesting that the vetter checked the applicant's claimed identity in a vetting session. The member set and the enumerated values are exactly those of the predicate's object schema in the DTG VSC predicate registry (`https://registry.trustoverip.org/dtg/vsc/vetted/1/vetting.schema.json`); where this definition is narrower — it requires the three vetter-only members `identityCommitment`, `cardDigestMultibase` and `declaredRelationship`, which a vetter's statement always carries and the registry makes all-or-nothing because a statement the community issues for itself carries none of them, and claim and document types use the vetting vocabularies — every value it accepts is also valid under the registry schema. There is no `type` member: the statement's `predicate` carries its meaning. A community names that predicate in its manifest as `vetting.statementType`. The credential envelope — `issuer`, `issuerScope`, validity, `taskContext`, `taskDigestMultibase`, proof — belongs to DTG credentials; only the object value is defined here. It records what the vetter did and relied on, never what they saw: no document number, no image, no claimed name. Not itself a Trust Task specification (the `_shared` folder is skipped by the registry build and the codegen).
https://trusttasks.org/spec/vetting/_shared/0.1/identity-vettingTrust Tasks — the registry of Trust Task specifications.
Loading the registry… If this message stays, the page's scripts could not load or run. The site needs JavaScript and access to unpkg.com.
Every specification is also on GitHub: trustoverip/dtgwg-trust-tasks-tf/specs, and the framework specification at /SPEC.md.