@openvtc/trust-tasks 0.22.1 → 0.22.3

package/dist/vtc/members/step-up-passkey-notice/0.1/payload.d.ts

@@ -0,0 +1,176 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vtc/members/step-up-passkey-notice/0.1/payload.schema.json
+ */
+import type { Ext } from "../../../../_shared/components.js";
+/**
+ * The VTC tells a member that a step-up passkey was enrolled for them or revoked from them, naming who acted and when. Unsolicited: the member did not ask, and may be offline.
+ */
+export interface VTCMembersStepUpPasskeyNoticePayload {
+    /**
+     * `enrolled` — a step-up passkey (auth/passkey/enroll/invite or auth/passkey/enroll/finish, purpose stepUp) is now bound to the member. `revoked` — one was unbound (auth/passkey/revoke/finish).
+     */
+    event: "enrolled" | "revoked";
+    /**
+     * The member's own DID — the notice's recipient. Carried in the payload as well as the envelope so that a forwarded notice, detached from its transport, still names its subject.
+     */
+    did: string;
+    /**
+     * Durable identifier of the step-up credential, as auth/passkey/revoke/start and auth/passkey/admin-list carry it: opaque, non-secret metadata, never key material. Lets the member recognise or distinguish a credential without disclosing anything that would help an attacker.
+     */
+    credentialId: string;
+    /**
+     * Who acted: the member themselves (equal to `did`) when they enrolled or revoked it on their own session, or an administrator's DID when they invited the enrollment or revoked for the member. A `by` other than `did` is the signal this task exists to carry — act on someone else's behalf is exactly the account-takeover shape a silent change would hide.
+     */
+    by: string;
+    /**
+     * When the event took effect at the VTC — not when the notice was sent, which differs whenever the member was offline.
+     */
+    at: string;
+    /**
+     * The acting administrator's stated reason, verbatim, when one was given. Absent rather than empty when none was: a community that chose not to explain is itself information. Never populated for a member acting on their own credential — they already know why.
+     */
+    reason?: string;
+    ext?: Ext;
+}
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { Ext };
+/** Trust Task type URI. */
+export declare const TYPE_URI: "https://trusttasks.org/spec/vtc/members/step-up-passkey-notice/0.1";
+/** Stable alias for this specification's request payload shape. */
+export type Payload = VTCMembersStepUpPasskeyNoticePayload;
+/**
+ * This specification's payload schema, as a value.
+ *
+ * SPEC.md §7.2 item 2 is performed against this. It is shipped as data
+ * rather than only as a `.json` file because TypeScript types are erased
+ * at runtime: without a schema a consumer has nothing to validate, and
+ * every REQUIRED payload member is optional in practice. Cross-file
+ * `$ref`s are already inlined, so it needs no resolver.
+ */
+export declare const PAYLOAD_SCHEMA: {
+    readonly $schema: "https://json-schema.org/draft/2020-12/schema";
+    readonly $id: "https://trusttasks.org/spec/vtc/members/step-up-passkey-notice/0.1";
+    readonly title: "VTC Members — Step-up Passkey Notice — payload";
+    readonly description: "The VTC tells a member that a step-up passkey was enrolled for them or revoked from them, naming who acted and when. Unsolicited: the member did not ask, and may be offline.";
+    readonly type: "object";
+    readonly additionalProperties: false;
+    readonly required: readonly ["event", "did", "credentialId", "by", "at"];
+    readonly properties: {
+        readonly event: {
+            readonly type: "string";
+            readonly enum: readonly ["enrolled", "revoked"];
+            readonly description: "`enrolled` — a step-up passkey (auth/passkey/enroll/invite or auth/passkey/enroll/finish, purpose stepUp) is now bound to the member. `revoked` — one was unbound (auth/passkey/revoke/finish).";
+        };
+        readonly did: {
+            readonly type: "string";
+            readonly minLength: 1;
+            readonly description: "The member's own DID — the notice's recipient. Carried in the payload as well as the envelope so that a forwarded notice, detached from its transport, still names its subject.";
+        };
+        readonly credentialId: {
+            readonly type: "string";
+            readonly minLength: 1;
+            readonly description: "Durable identifier of the step-up credential, as auth/passkey/revoke/start and auth/passkey/admin-list carry it: opaque, non-secret metadata, never key material. Lets the member recognise or distinguish a credential without disclosing anything that would help an attacker.";
+        };
+        readonly by: {
+            readonly type: "string";
+            readonly minLength: 1;
+            readonly description: "Who acted: the member themselves (equal to `did`) when they enrolled or revoked it on their own session, or an administrator's DID when they invited the enrollment or revoked for the member. A `by` other than `did` is the signal this task exists to carry — act on someone else's behalf is exactly the account-takeover shape a silent change would hide.";
+        };
+        readonly at: {
+            readonly type: "string";
+            readonly format: "date-time";
+            readonly description: "When the event took effect at the VTC — not when the notice was sent, which differs whenever the member was offline.";
+        };
+        readonly reason: {
+            readonly type: "string";
+            readonly maxLength: 1024;
+            readonly description: "The acting administrator's stated reason, verbatim, when one was given. Absent rather than empty when none was: a community that chose not to explain is itself information. Never populated for a member acting on their own credential — they already know why.";
+        };
+        readonly ext: {
+            readonly $ref: "#/$defs/Ext";
+        };
+    };
+    readonly $defs: {
+        readonly Ext: {
+            readonly title: "Ext";
+            readonly description: "Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a reverse-DNS namespace; structure under each namespace is opaque to the framework.";
+            readonly type: "object";
+            readonly minProperties: 1;
+            readonly additionalProperties: true;
+            readonly propertyNames: {
+                readonly pattern: "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$";
+            };
+        };
+    };
+};
+/**
+ * SPEC.md §7.2 policy for the request variant, from this specification's
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
+ * per-specification and cannot be derived from the document alone, and
+ * item 2 needs the schema this carries.
+ */
+export declare const SPEC: {
+    readonly typeUri: "https://trusttasks.org/spec/vtc/members/step-up-passkey-notice/0.1";
+    readonly isBearer: false;
+    readonly isProofRequired: true;
+    readonly isRecipientRequired: true;
+    readonly isIssuedAtRequired: true;
+    readonly payloadSchema: {
+        readonly $schema: "https://json-schema.org/draft/2020-12/schema";
+        readonly $id: "https://trusttasks.org/spec/vtc/members/step-up-passkey-notice/0.1";
+        readonly title: "VTC Members — Step-up Passkey Notice — payload";
+        readonly description: "The VTC tells a member that a step-up passkey was enrolled for them or revoked from them, naming who acted and when. Unsolicited: the member did not ask, and may be offline.";
+        readonly type: "object";
+        readonly additionalProperties: false;
+        readonly required: readonly ["event", "did", "credentialId", "by", "at"];
+        readonly properties: {
+            readonly event: {
+                readonly type: "string";
+                readonly enum: readonly ["enrolled", "revoked"];
+                readonly description: "`enrolled` — a step-up passkey (auth/passkey/enroll/invite or auth/passkey/enroll/finish, purpose stepUp) is now bound to the member. `revoked` — one was unbound (auth/passkey/revoke/finish).";
+            };
+            readonly did: {
+                readonly type: "string";
+                readonly minLength: 1;
+                readonly description: "The member's own DID — the notice's recipient. Carried in the payload as well as the envelope so that a forwarded notice, detached from its transport, still names its subject.";
+            };
+            readonly credentialId: {
+                readonly type: "string";
+                readonly minLength: 1;
+                readonly description: "Durable identifier of the step-up credential, as auth/passkey/revoke/start and auth/passkey/admin-list carry it: opaque, non-secret metadata, never key material. Lets the member recognise or distinguish a credential without disclosing anything that would help an attacker.";
+            };
+            readonly by: {
+                readonly type: "string";
+                readonly minLength: 1;
+                readonly description: "Who acted: the member themselves (equal to `did`) when they enrolled or revoked it on their own session, or an administrator's DID when they invited the enrollment or revoked for the member. A `by` other than `did` is the signal this task exists to carry — act on someone else's behalf is exactly the account-takeover shape a silent change would hide.";
+            };
+            readonly at: {
+                readonly type: "string";
+                readonly format: "date-time";
+                readonly description: "When the event took effect at the VTC — not when the notice was sent, which differs whenever the member was offline.";
+            };
+            readonly reason: {
+                readonly type: "string";
+                readonly maxLength: 1024;
+                readonly description: "The acting administrator's stated reason, verbatim, when one was given. Absent rather than empty when none was: a community that chose not to explain is itself information. Never populated for a member acting on their own credential — they already know why.";
+            };
+            readonly ext: {
+                readonly $ref: "#/$defs/Ext";
+            };
+        };
+        readonly $defs: {
+            readonly Ext: {
+                readonly title: "Ext";
+                readonly description: "Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a reverse-DNS namespace; structure under each namespace is opaque to the framework.";
+                readonly type: "object";
+                readonly minProperties: 1;
+                readonly additionalProperties: true;
+                readonly propertyNames: {
+                    readonly pattern: "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$";
+                };
+            };
+        };
+    };
+};
+//# sourceMappingURL=payload.d.ts.map

package/dist/vtc/members/step-up-passkey-notice/0.1/payload.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"payload.d.ts","sourceRoot":"","sources":["../../../../../src/vtc/members/step-up-passkey-notice/0.1/payload.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,OAAO,KAAK,EAAE,GAAG,EAAE,MAAM,mCAAmC,CAAC;AAG7D;;GAEG;AACH,MAAM,WAAW,oCAAoC;IACnD;;OAEG;IACH,KAAK,EAAE,UAAU,GAAG,SAAS,CAAC;IAC9B;;OAEG;IACH,GAAG,EAAE,MAAM,CAAC;IACZ;;OAEG;IACH,YAAY,EAAE,MAAM,CAAC;IACrB;;OAEG;IACH,EAAE,EAAE,MAAM,CAAC;IACX;;OAEG;IACH,EAAE,EAAE,MAAM,CAAC;IACX;;OAEG;IACH,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,GAAG,CAAC,EAAE,GAAG,CAAC;CACX;AAED,kHAAkH;AAClH,YAAY,EAAE,GAAG,EAAE,CAAC;AAEpB,2BAA2B;AAC3B,eAAO,MAAM,QAAQ,EAAG,oEAA6E,CAAC;AAEtG,mEAAmE;AACnE,MAAM,MAAM,OAAO,GAAG,oCAAoC,CAAC;AAE3D;;;;;;;;GAQG;AACH,eAAO,MAAM,cAAc;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAgEjB,CAAC;AAEX;;;;;GAKG;AACH,eAAO,MAAM,IAAI;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAOP,CAAC"}

package/dist/vtc/members/step-up-passkey-notice/0.1/payload.js

@@ -0,0 +1,95 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vtc/members/step-up-passkey-notice/0.1/payload.schema.json
+ */
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/vtc/members/step-up-passkey-notice/0.1";
+/**
+ * This specification's payload schema, as a value.
+ *
+ * SPEC.md §7.2 item 2 is performed against this. It is shipped as data
+ * rather than only as a `.json` file because TypeScript types are erased
+ * at runtime: without a schema a consumer has nothing to validate, and
+ * every REQUIRED payload member is optional in practice. Cross-file
+ * `$ref`s are already inlined, so it needs no resolver.
+ */
+export const PAYLOAD_SCHEMA = {
+    "$schema": "https://json-schema.org/draft/2020-12/schema",
+    "$id": "https://trusttasks.org/spec/vtc/members/step-up-passkey-notice/0.1",
+    "title": "VTC Members — Step-up Passkey Notice — payload",
+    "description": "The VTC tells a member that a step-up passkey was enrolled for them or revoked from them, naming who acted and when. Unsolicited: the member did not ask, and may be offline.",
+    "type": "object",
+    "additionalProperties": false,
+    "required": [
+        "event",
+        "did",
+        "credentialId",
+        "by",
+        "at"
+    ],
+    "properties": {
+        "event": {
+            "type": "string",
+            "enum": [
+                "enrolled",
+                "revoked"
+            ],
+            "description": "`enrolled` — a step-up passkey (auth/passkey/enroll/invite or auth/passkey/enroll/finish, purpose stepUp) is now bound to the member. `revoked` — one was unbound (auth/passkey/revoke/finish)."
+        },
+        "did": {
+            "type": "string",
+            "minLength": 1,
+            "description": "The member's own DID — the notice's recipient. Carried in the payload as well as the envelope so that a forwarded notice, detached from its transport, still names its subject."
+        },
+        "credentialId": {
+            "type": "string",
+            "minLength": 1,
+            "description": "Durable identifier of the step-up credential, as auth/passkey/revoke/start and auth/passkey/admin-list carry it: opaque, non-secret metadata, never key material. Lets the member recognise or distinguish a credential without disclosing anything that would help an attacker."
+        },
+        "by": {
+            "type": "string",
+            "minLength": 1,
+            "description": "Who acted: the member themselves (equal to `did`) when they enrolled or revoked it on their own session, or an administrator's DID when they invited the enrollment or revoked for the member. A `by` other than `did` is the signal this task exists to carry — act on someone else's behalf is exactly the account-takeover shape a silent change would hide."
+        },
+        "at": {
+            "type": "string",
+            "format": "date-time",
+            "description": "When the event took effect at the VTC — not when the notice was sent, which differs whenever the member was offline."
+        },
+        "reason": {
+            "type": "string",
+            "maxLength": 1024,
+            "description": "The acting administrator's stated reason, verbatim, when one was given. Absent rather than empty when none was: a community that chose not to explain is itself information. Never populated for a member acting on their own credential — they already know why."
+        },
+        "ext": {
+            "$ref": "#/$defs/Ext"
+        }
+    },
+    "$defs": {
+        "Ext": {
+            "title": "Ext",
+            "description": "Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a reverse-DNS namespace; structure under each namespace is opaque to the framework.",
+            "type": "object",
+            "minProperties": 1,
+            "additionalProperties": true,
+            "propertyNames": {
+                "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
+            }
+        }
+    }
+};
+/**
+ * SPEC.md §7.2 policy for the request variant, from this specification's
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
+ * per-specification and cannot be derived from the document alone, and
+ * item 2 needs the schema this carries.
+ */
+export const SPEC = {
+    typeUri: TYPE_URI,
+    isBearer: false,
+    isProofRequired: true,
+    isRecipientRequired: true,
+    isIssuedAtRequired: true,
+    payloadSchema: PAYLOAD_SCHEMA,
+};
+//# sourceMappingURL=payload.js.map

package/dist/vtc/members/step-up-passkey-notice/0.1/payload.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"payload.js","sourceRoot":"","sources":["../../../../../src/vtc/members/step-up-passkey-notice/0.1/payload.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAuCH,2BAA2B;AAC3B,MAAM,CAAC,MAAM,QAAQ,GAAG,oEAA6E,CAAC;AAKtG;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,cAAc,GAAG;IAC5B,SAAS,EAAE,8CAA8C;IACzD,KAAK,EAAE,oEAAoE;IAC3E,OAAO,EAAE,gDAAgD;IACzD,aAAa,EAAE,+KAA+K;IAC9L,MAAM,EAAE,QAAQ;IAChB,sBAAsB,EAAE,KAAK;IAC7B,UAAU,EAAE;QACV,OAAO;QACP,KAAK;QACL,cAAc;QACd,IAAI;QACJ,IAAI;KACL;IACD,YAAY,EAAE;QACZ,OAAO,EAAE;YACP,MAAM,EAAE,QAAQ;YAChB,MAAM,EAAE;gBACN,UAAU;gBACV,SAAS;aACV;YACD,aAAa,EAAE,iMAAiM;SACjN;QACD,KAAK,EAAE;YACL,MAAM,EAAE,QAAQ;YAChB,WAAW,EAAE,CAAC;YACd,aAAa,EAAE,iLAAiL;SACjM;QACD,cAAc,EAAE;YACd,MAAM,EAAE,QAAQ;YAChB,WAAW,EAAE,CAAC;YACd,aAAa,EAAE,kRAAkR;SAClS;QACD,IAAI,EAAE;YACJ,MAAM,EAAE,QAAQ;YAChB,WAAW,EAAE,CAAC;YACd,aAAa,EAAE,iWAAiW;SACjX;QACD,IAAI,EAAE;YACJ,MAAM,EAAE,QAAQ;YAChB,QAAQ,EAAE,WAAW;YACrB,aAAa,EAAE,sHAAsH;SACtI;QACD,QAAQ,EAAE;YACR,MAAM,EAAE,QAAQ;YAChB,WAAW,EAAE,IAAI;YACjB,aAAa,EAAE,mQAAmQ;SACnR;QACD,KAAK,EAAE;YACL,MAAM,EAAE,aAAa;SACtB;KACF;IACD,OAAO,EAAE;QACP,KAAK,EAAE;YACL,OAAO,EAAE,KAAK;YACd,aAAa,EAAE,uKAAuK;YACtL,MAAM,EAAE,QAAQ;YAChB,eAAe,EAAE,CAAC;YAClB,sBAAsB,EAAE,IAAI;YAC5B,eAAe,EAAE;gBACf,SAAS,EAAE,mCAAmC;aAC/C;SACF;KACF;CACO,CAAC;AAEX;;;;;GAKG;AACH,MAAM,CAAC,MAAM,IAAI,GAAG;IAClB,OAAO,EAAE,QAAQ;IACjB,QAAQ,EAAE,KAAK;IACf,eAAe,EAAE,IAAI;IACrB,mBAAmB,EAAE,IAAI;IACzB,kBAAkB,EAAE,IAAI;IACxB,aAAa,EAAE,cAAc;CACrB,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openvtc/trust-tasks",
-  "version": "0.22.1",
+  "version": "0.22.3",
   "description": "Generated TypeScript bindings for the Trust Tasks framework registry.",
   "type": "module",
   "main": "./dist/index.js",

package/src/_shared/components.ts

@@ -2834,7 +2834,7 @@ export interface Endorsement {
    */
   endorsementId: string;
   /**
-   * What the row records. A registered predicate IRI: a statement (StatementCredential) whose `credentialSubject.predicate` it is — see vtc/endorsement-types/*. `role:vetter`: a vetter role credential (Verifiable Authority Credential) issued by vtc/vetting/vetters/grant. `IdentityVerificationCredential`: the community's identity-verification credential, a plain W3C VC (not a DTGCredential). The two reserved values are not IRIs, so they never collide with a registered predicate.
+   * What the row records. A registered predicate IRI: a statement (StatementCredential) whose `credentialSubject.predicate` it is — see vtc/endorsement-types/*. `role:vetter`: a vetter role credential (Verifiable Authority Credential) issued by vtc/vetting/vetters/grant. The reserved value is not an IRI, so it never collides with a registered predicate. A community's own identity check is a statement like any other, under `https://registry.trustoverip.org/dtg/vsc/vetted/1`.
    */
   typeUri: string;
   /**
@@ -2860,7 +2860,7 @@ export interface Endorsement {
 }
 export interface EndorsementType {
   /**
-   * The predicate IRI the community accepts, compared as an exact string. Always an absolute IRI: a DTG VSC predicate registry IRI (e.g. `https://registry.trustoverip.org/dtg/vsc/vetted/1`) or a community-namespace IRI defined in the registry's predicate definition format. The four core predicates — endorses/1, witnessed/1, vetted/1 and presented/1 under `https://registry.trustoverip.org/dtg/vsc/` — are seeded when the community starts. The reserved values `IdentityVerificationCredential` and `role:vetter`, which name the other kinds of record vtc/endorsements/* keeps, are never registered.
+   * The predicate IRI the community accepts, compared as an exact string. Always an absolute IRI: a DTG VSC predicate registry IRI (e.g. `https://registry.trustoverip.org/dtg/vsc/vetted/1`) or a community-namespace IRI defined in the registry's predicate definition format. The four core predicates — endorses/1, witnessed/1, vetted/1 and presented/1 under `https://registry.trustoverip.org/dtg/vsc/` — are seeded when the community starts. The reserved value `role:vetter`, which names the vetter-role record vtc/endorsements/* keeps beside statements, is never registered.
    */
   typeUri: string;
   description?: string;
@@ -3834,7 +3834,7 @@ export interface PersonhoodGovernance {
    */
   singleMembership?: boolean;
   /**
-   * DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence. A community that vets its own members in person lists its own community DID here — it is acting as its own IDVP, which §IDVC permits — and issues the evidence as an `IdentityVerificationCredential` (a plain W3C VC, not a DTGCredential) through vtc/endorsements/issue. An empty list means no list has been published, not that everything is accepted.
+   * DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence: any W3C VC from a listed provider that meets the community's identity-proofing requirements. A community that checks its members' identity in person does not act as a provider to do so: it records each check as a `vetted/1` statement (`https://registry.trustoverip.org/dtg/vsc/vetted/1`) issued under its own DID through vtc/endorsements/issue, which its personhood policy may accept beside these credentials. Either is evidence only — personhood is the community's decision, recorded on the member's VMC. An empty list means no list has been published, not that everything is accepted.
    */
   acceptedIdvps?: string[];
   /**

package/src/index.ts

@@ -670,6 +670,7 @@ export * as VtcMembersSelfRemoveReceipt_v0_1 from "./vtc/members/self-remove-rec
 export * as VtcMembersSelfRemove_v0_1 from "./vtc/members/self-remove/0.1/payload.js";
 export * as VtcMembersShow_v0_1 from "./vtc/members/show/0.1/payload.js";
 export * as VtcMembersSolicitVmc_v0_1 from "./vtc/members/solicit-vmc/0.1/payload.js";
+export * as VtcMembersStepUpPasskeyNotice_v0_1 from "./vtc/members/step-up-passkey-notice/0.1/payload.js";
 export * as VtcMembersUpdate_v0_1 from "./vtc/members/update/0.1/payload.js";
 export * as VtcMembersVmc_v0_1 from "./vtc/members/vmc/0.1/payload.js";
 export * as VtcPoliciesTest_v0_1 from "./vtc/policies/test/0.1/payload.js";

package/src/vetting/_shared/0.1/identity-vetting.ts

@@ -4,7 +4,7 @@
  */
 
 /**
- * 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, the required 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 — 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).
+ * 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).
  */
 export interface IdentityVettingStatementValueSharedDefinition {
   [k: string]: unknown | undefined;

package/src/vtc/_shared/0.1/endorsement.ts

@@ -4,7 +4,7 @@
  */
 
 /**
- * Shared type for the vtc/endorsements/* family: one community-issued, community-revocable credential row. Usually a statement — `typeUri` says which kind of row it is. The statement credential is a DTG Verifiable Statement Credential (`type` [VerifiableCredential, DTGCredential, StatementCredential], `issuerScope` public) — a Verifiable Endorsement Credential (VEC) when its predicate is `https://registry.trustoverip.org/dtg/vsc/endorses/1`. Embeds the registry-wide credentials/_shared CredentialReference and adds the VTC-specific parts — the registered predicate and the shared status-list slot that makes the statement third-party revocation-checkable. The family and member names (`endorsementId`, `typeUri`, `claim`) are kept from when these were `EndorsementCredential`s.
+ * Shared type for the vtc/endorsements/* family: one community-issued, community-revocable credential row: a statement, or a vetter role grant — `typeUri` says which. The statement credential is a DTG Verifiable Statement Credential (`type` [VerifiableCredential, DTGCredential, StatementCredential], `issuerScope` public) — a Verifiable Endorsement Credential (VEC) when its predicate is `https://registry.trustoverip.org/dtg/vsc/endorses/1`. Embeds the registry-wide credentials/_shared CredentialReference and adds the VTC-specific parts — the registered predicate and the shared status-list slot that makes the statement third-party revocation-checkable. The family and member names (`endorsementId`, `typeUri`, `claim`) are kept from when these were `EndorsementCredential`s.
  */
 export interface VTCSharedEndorsementDefinitions {
   [k: string]: unknown | undefined;

package/src/vtc/community/profile/show/0.1/payload.ts

@@ -181,7 +181,7 @@ export const PAYLOAD_SCHEMA = {
             "type": "string",
             "minLength": 1
           },
-          "description": "DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence. A community that vets its own members in person lists its own community DID here — it is acting as its own IDVP, which §IDVC permits — and issues the evidence as an `IdentityVerificationCredential` (a plain W3C VC, not a DTGCredential) through vtc/endorsements/issue. An empty list means no list has been published, not that everything is accepted."
+          "description": "DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence: any W3C VC from a listed provider that meets the community's identity-proofing requirements. A community that checks its members' identity in person does not act as a provider to do so: it records each check as a `vetted/1` statement (`https://registry.trustoverip.org/dtg/vsc/vetted/1`) issued under its own DID through vtc/endorsements/issue, which its personhood policy may accept beside these credentials. Either is evidence only — personhood is the community's decision, recorded on the member's VMC. An empty list means no list has been published, not that everything is accepted."
         },
         "governanceFrameworkUrl": {
           "type": [
@@ -328,7 +328,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
             "type": "string",
             "minLength": 1
           },
-          "description": "DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence. A community that vets its own members in person lists its own community DID here — it is acting as its own IDVP, which §IDVC permits — and issues the evidence as an `IdentityVerificationCredential` (a plain W3C VC, not a DTGCredential) through vtc/endorsements/issue. An empty list means no list has been published, not that everything is accepted."
+          "description": "DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence: any W3C VC from a listed provider that meets the community's identity-proofing requirements. A community that checks its members' identity in person does not act as a provider to do so: it records each check as a `vetted/1` statement (`https://registry.trustoverip.org/dtg/vsc/vetted/1`) issued under its own DID through vtc/endorsements/issue, which its personhood policy may accept beside these credentials. Either is evidence only — personhood is the community's decision, recorded on the member's VMC. An empty list means no list has been published, not that everything is accepted."
         },
         "governanceFrameworkUrl": {
           "type": [

package/src/vtc/community/profile/update/0.1/payload.ts

@@ -257,7 +257,7 @@ export const PAYLOAD_SCHEMA = {
             "type": "string",
             "minLength": 1
           },
-          "description": "DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence. A community that vets its own members in person lists its own community DID here — it is acting as its own IDVP, which §IDVC permits — and issues the evidence as an `IdentityVerificationCredential` (a plain W3C VC, not a DTGCredential) through vtc/endorsements/issue. An empty list means no list has been published, not that everything is accepted."
+          "description": "DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence: any W3C VC from a listed provider that meets the community's identity-proofing requirements. A community that checks its members' identity in person does not act as a provider to do so: it records each check as a `vetted/1` statement (`https://registry.trustoverip.org/dtg/vsc/vetted/1`) issued under its own DID through vtc/endorsements/issue, which its personhood policy may accept beside these credentials. Either is evidence only — personhood is the community's decision, recorded on the member's VMC. An empty list means no list has been published, not that everything is accepted."
         },
         "governanceFrameworkUrl": {
           "type": [
@@ -411,7 +411,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
             "type": "string",
             "minLength": 1
           },
-          "description": "DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence. A community that vets its own members in person lists its own community DID here — it is acting as its own IDVP, which §IDVC permits — and issues the evidence as an `IdentityVerificationCredential` (a plain W3C VC, not a DTGCredential) through vtc/endorsements/issue. An empty list means no list has been published, not that everything is accepted."
+          "description": "DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence: any W3C VC from a listed provider that meets the community's identity-proofing requirements. A community that checks its members' identity in person does not act as a provider to do so: it records each check as a `vetted/1` statement (`https://registry.trustoverip.org/dtg/vsc/vetted/1`) issued under its own DID through vtc/endorsements/issue, which its personhood policy may accept beside these credentials. Either is evidence only — personhood is the community's decision, recorded on the member's VMC. An empty list means no list has been published, not that everything is accepted."
         },
         "governanceFrameworkUrl": {
           "type": [

package/src/vtc/config/export/0.1/payload.ts

@@ -214,7 +214,7 @@ export const PAYLOAD_SCHEMA = {
             "type": "string",
             "minLength": 1
           },
-          "description": "DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence. A community that vets its own members in person lists its own community DID here — it is acting as its own IDVP, which §IDVC permits — and issues the evidence as an `IdentityVerificationCredential` (a plain W3C VC, not a DTGCredential) through vtc/endorsements/issue. An empty list means no list has been published, not that everything is accepted."
+          "description": "DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence: any W3C VC from a listed provider that meets the community's identity-proofing requirements. A community that checks its members' identity in person does not act as a provider to do so: it records each check as a `vetted/1` statement (`https://registry.trustoverip.org/dtg/vsc/vetted/1`) issued under its own DID through vtc/endorsements/issue, which its personhood policy may accept beside these credentials. Either is evidence only — personhood is the community's decision, recorded on the member's VMC. An empty list means no list has been published, not that everything is accepted."
         },
         "governanceFrameworkUrl": {
           "type": [
@@ -390,7 +390,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
             "type": "string",
             "minLength": 1
           },
-          "description": "DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence. A community that vets its own members in person lists its own community DID here — it is acting as its own IDVP, which §IDVC permits — and issues the evidence as an `IdentityVerificationCredential` (a plain W3C VC, not a DTGCredential) through vtc/endorsements/issue. An empty list means no list has been published, not that everything is accepted."
+          "description": "DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence: any W3C VC from a listed provider that meets the community's identity-proofing requirements. A community that checks its members' identity in person does not act as a provider to do so: it records each check as a `vetted/1` statement (`https://registry.trustoverip.org/dtg/vsc/vetted/1`) issued under its own DID through vtc/endorsements/issue, which its personhood policy may accept beside these credentials. Either is evidence only — personhood is the community's decision, recorded on the member's VMC. An empty list means no list has been published, not that everything is accepted."
         },
         "governanceFrameworkUrl": {
           "type": [

package/src/vtc/config/import/0.1/payload.ts

@@ -333,7 +333,7 @@ export const PAYLOAD_SCHEMA = {
             "type": "string",
             "minLength": 1
           },
-          "description": "DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence. A community that vets its own members in person lists its own community DID here — it is acting as its own IDVP, which §IDVC permits — and issues the evidence as an `IdentityVerificationCredential` (a plain W3C VC, not a DTGCredential) through vtc/endorsements/issue. An empty list means no list has been published, not that everything is accepted."
+          "description": "DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence: any W3C VC from a listed provider that meets the community's identity-proofing requirements. A community that checks its members' identity in person does not act as a provider to do so: it records each check as a `vetted/1` statement (`https://registry.trustoverip.org/dtg/vsc/vetted/1`) issued under its own DID through vtc/endorsements/issue, which its personhood policy may accept beside these credentials. Either is evidence only — personhood is the community's decision, recorded on the member's VMC. An empty list means no list has been published, not that everything is accepted."
         },
         "governanceFrameworkUrl": {
           "type": [
@@ -592,7 +592,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
             "type": "string",
             "minLength": 1
           },
-          "description": "DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence. A community that vets its own members in person lists its own community DID here — it is acting as its own IDVP, which §IDVC permits — and issues the evidence as an `IdentityVerificationCredential` (a plain W3C VC, not a DTGCredential) through vtc/endorsements/issue. An empty list means no list has been published, not that everything is accepted."
+          "description": "DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence: any W3C VC from a listed provider that meets the community's identity-proofing requirements. A community that checks its members' identity in person does not act as a provider to do so: it records each check as a `vetted/1` statement (`https://registry.trustoverip.org/dtg/vsc/vetted/1`) issued under its own DID through vtc/endorsements/issue, which its personhood policy may accept beside these credentials. Either is evidence only — personhood is the community's decision, recorded on the member's VMC. An empty list means no list has been published, not that everything is accepted."
         },
         "governanceFrameworkUrl": {
           "type": [

package/src/vtc/endorsement-types/list/0.1/payload.ts

@@ -110,7 +110,7 @@ export const PAYLOAD_SCHEMA = {
           "type": "string",
           "minLength": 1,
           "maxLength": 512,
-          "description": "The predicate IRI the community accepts, compared as an exact string. Always an absolute IRI: a DTG VSC predicate registry IRI (e.g. `https://registry.trustoverip.org/dtg/vsc/vetted/1`) or a community-namespace IRI defined in the registry's predicate definition format. The four core predicates — endorses/1, witnessed/1, vetted/1 and presented/1 under `https://registry.trustoverip.org/dtg/vsc/` — are seeded when the community starts. The reserved values `IdentityVerificationCredential` and `role:vetter`, which name the other kinds of record vtc/endorsements/* keeps, are never registered."
+          "description": "The predicate IRI the community accepts, compared as an exact string. Always an absolute IRI: a DTG VSC predicate registry IRI (e.g. `https://registry.trustoverip.org/dtg/vsc/vetted/1`) or a community-namespace IRI defined in the registry's predicate definition format. The four core predicates — endorses/1, witnessed/1, vetted/1 and presented/1 under `https://registry.trustoverip.org/dtg/vsc/` — are seeded when the community starts. The reserved value `role:vetter`, which names the vetter-role record vtc/endorsements/* keeps beside statements, is never registered."
         },
         "description": {
           "type": "string",
@@ -187,7 +187,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
           "type": "string",
           "minLength": 1,
           "maxLength": 512,
-          "description": "The predicate IRI the community accepts, compared as an exact string. Always an absolute IRI: a DTG VSC predicate registry IRI (e.g. `https://registry.trustoverip.org/dtg/vsc/vetted/1`) or a community-namespace IRI defined in the registry's predicate definition format. The four core predicates — endorses/1, witnessed/1, vetted/1 and presented/1 under `https://registry.trustoverip.org/dtg/vsc/` — are seeded when the community starts. The reserved values `IdentityVerificationCredential` and `role:vetter`, which name the other kinds of record vtc/endorsements/* keeps, are never registered."
+          "description": "The predicate IRI the community accepts, compared as an exact string. Always an absolute IRI: a DTG VSC predicate registry IRI (e.g. `https://registry.trustoverip.org/dtg/vsc/vetted/1`) or a community-namespace IRI defined in the registry's predicate definition format. The four core predicates — endorses/1, witnessed/1, vetted/1 and presented/1 under `https://registry.trustoverip.org/dtg/vsc/` — are seeded when the community starts. The reserved value `role:vetter`, which names the vetter-role record vtc/endorsements/* keeps beside statements, is never registered."
         },
         "description": {
           "type": "string",

package/src/vtc/endorsement-types/register/0.1/payload.ts

@@ -8,7 +8,7 @@ import type { EndorsementType, Ext } from "../../../../_shared/components.js";
 
 export interface VTCEndorsementTypesRegisterPayload {
   /**
-   * The predicate IRI to accept, an absolute IRI: a DTG VSC predicate registry IRI or a community-namespace IRI. The reserved values `IdentityVerificationCredential` and `role:vetter` are refused with `reserved`, and a value that is not an absolute IRI with `invalidUri`.
+   * The predicate IRI to accept, an absolute IRI: a DTG VSC predicate registry IRI or a community-namespace IRI. The reserved value `role:vetter` is refused with `reserved`, and a value that is not an absolute IRI with `invalidUri`.
    */
   typeUri: string;
   description?: string;
@@ -61,7 +61,7 @@ export const PAYLOAD_SCHEMA = {
       "type": "string",
       "minLength": 1,
       "maxLength": 512,
-      "description": "The predicate IRI to accept, an absolute IRI: a DTG VSC predicate registry IRI or a community-namespace IRI. The reserved values `IdentityVerificationCredential` and `role:vetter` are refused with `reserved`, and a value that is not an absolute IRI with `invalidUri`."
+      "description": "The predicate IRI to accept, an absolute IRI: a DTG VSC predicate registry IRI or a community-namespace IRI. The reserved value `role:vetter` is refused with `reserved`, and a value that is not an absolute IRI with `invalidUri`."
     },
     "description": {
       "type": "string",
@@ -116,7 +116,7 @@ export const PAYLOAD_SCHEMA = {
           "type": "string",
           "minLength": 1,
           "maxLength": 512,
-          "description": "The predicate IRI the community accepts, compared as an exact string. Always an absolute IRI: a DTG VSC predicate registry IRI (e.g. `https://registry.trustoverip.org/dtg/vsc/vetted/1`) or a community-namespace IRI defined in the registry's predicate definition format. The four core predicates — endorses/1, witnessed/1, vetted/1 and presented/1 under `https://registry.trustoverip.org/dtg/vsc/` — are seeded when the community starts. The reserved values `IdentityVerificationCredential` and `role:vetter`, which name the other kinds of record vtc/endorsements/* keeps, are never registered."
+          "description": "The predicate IRI the community accepts, compared as an exact string. Always an absolute IRI: a DTG VSC predicate registry IRI (e.g. `https://registry.trustoverip.org/dtg/vsc/vetted/1`) or a community-namespace IRI defined in the registry's predicate definition format. The four core predicates — endorses/1, witnessed/1, vetted/1 and presented/1 under `https://registry.trustoverip.org/dtg/vsc/` — are seeded when the community starts. The reserved value `role:vetter`, which names the vetter-role record vtc/endorsements/* keeps beside statements, is never registered."
         },
         "description": {
           "type": "string",
@@ -184,7 +184,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
           "type": "string",
           "minLength": 1,
           "maxLength": 512,
-          "description": "The predicate IRI the community accepts, compared as an exact string. Always an absolute IRI: a DTG VSC predicate registry IRI (e.g. `https://registry.trustoverip.org/dtg/vsc/vetted/1`) or a community-namespace IRI defined in the registry's predicate definition format. The four core predicates — endorses/1, witnessed/1, vetted/1 and presented/1 under `https://registry.trustoverip.org/dtg/vsc/` — are seeded when the community starts. The reserved values `IdentityVerificationCredential` and `role:vetter`, which name the other kinds of record vtc/endorsements/* keeps, are never registered."
+          "description": "The predicate IRI the community accepts, compared as an exact string. Always an absolute IRI: a DTG VSC predicate registry IRI (e.g. `https://registry.trustoverip.org/dtg/vsc/vetted/1`) or a community-namespace IRI defined in the registry's predicate definition format. The four core predicates — endorses/1, witnessed/1, vetted/1 and presented/1 under `https://registry.trustoverip.org/dtg/vsc/` — are seeded when the community starts. The reserved value `role:vetter`, which names the vetter-role record vtc/endorsements/* keeps beside statements, is never registered."
         },
         "description": {
           "type": "string",