@openvtc/trust-tasks 0.26.11 → 0.26.12

package/src/vtc/members/personhood/assert/0.2/payload.ts

@@ -0,0 +1,421 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vtc/members/personhood/assert/0.2/payload.schema.json
+ */
+
+import type { EvidenceDocument, Ext, OutcomeEvidence } from "../../../../../_shared/components.js";
+
+
+export interface VTCMembersPersonhoodAssertPayload {
+  /**
+   * The member asserting personhood; MUST equal the presentation's holder.
+   */
+  did: string;
+  /**
+   * A W3C Verifiable Presentation (opaque here). Its holder MUST match did, its proof.challenge MUST be the paired challengeId, and it MUST carry at least one credential satisfying the community's active personhood policy. A Verifiable Witness Credential in it counts only with paired outcomeEvidence.
+   */
+  presentation: {};
+  /**
+   * OPTIONAL. The outcome evidence of the witnessing sessions that the Verifiable Witness Credentials in presentation cite: one entry per VWC the member wants counted, each the witness/session document the VWC's taskContext names and the witness/session/submit #response that delivered it, exactly as stored, never re-serialised. A VWC with no paired entry counts for nothing; an entry pairing with no VWC in presentation is ignored.
+   *
+   * @minItems 1
+   * @maxItems 16
+   */
+  outcomeEvidence?:
+    | [OutcomeEvidence]
+    | [OutcomeEvidence, OutcomeEvidence]
+    | [OutcomeEvidence, OutcomeEvidence, OutcomeEvidence]
+    | [OutcomeEvidence, OutcomeEvidence, OutcomeEvidence, OutcomeEvidence]
+    | [OutcomeEvidence, OutcomeEvidence, OutcomeEvidence, OutcomeEvidence, OutcomeEvidence]
+    | [OutcomeEvidence, OutcomeEvidence, OutcomeEvidence, OutcomeEvidence, OutcomeEvidence, OutcomeEvidence]
+    | [
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence
+      ]
+    | [
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence
+      ]
+    | [
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence
+      ]
+    | [
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence
+      ]
+    | [
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence
+      ]
+    | [
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence
+      ]
+    | [
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence
+      ]
+    | [
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence
+      ]
+    | [
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence
+      ]
+    | [
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence,
+        OutcomeEvidence
+      ];
+  ext?: Ext;
+}
+export interface VTCMembersPersonhoodAssertResponsePayload {
+  did: string;
+  /**
+   * Always true on success — the flag flipped or stayed asserted.
+   */
+  personhood: true;
+  /**
+   * Re-issued membership credential carrying the asserted personhood (opaque here).
+   */
+  vmc: {};
+  /**
+   * Re-issued role credential (opaque here): a Verifiable Authority Credential (`type` including `AuthorityCredential`) issued by the community with `issuerScope` `public`, whose `credentialSubject.authority` is `{ scope: <community DID>, actions: ["role:<name>"] }` — the shape vtc/vetting/vetters/grant/0.1 issues.
+   */
+  roleVac: {};
+  ext?: Ext;
+}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { EvidenceDocument, Ext, OutcomeEvidence };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/vtc/members/personhood/assert/0.2" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = VTCMembersPersonhoodAssertPayload;
+
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/vtc/members/personhood/assert/0.2#response" as const;
+
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = VTCMembersPersonhoodAssertResponsePayload;
+
+/**
+ * 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/personhood/assert/0.2",
+  "title": "VTC Members Personhood-Assert — payload",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "did",
+    "presentation"
+  ],
+  "properties": {
+    "did": {
+      "type": "string",
+      "minLength": 1,
+      "description": "The member asserting personhood; MUST equal the presentation's holder."
+    },
+    "presentation": {
+      "type": "object",
+      "description": "A W3C Verifiable Presentation (opaque here). Its holder MUST match did, its proof.challenge MUST be the paired challengeId, and it MUST carry at least one credential satisfying the community's active personhood policy. A Verifiable Witness Credential in it counts only with paired outcomeEvidence."
+    },
+    "outcomeEvidence": {
+      "type": "array",
+      "minItems": 1,
+      "maxItems": 16,
+      "items": {
+        "$ref": "#/$defs/OutcomeEvidence"
+      },
+      "description": "OPTIONAL. The outcome evidence of the witnessing sessions that the Verifiable Witness Credentials in presentation cite: one entry per VWC the member wants counted, each the witness/session document the VWC's taskContext names and the witness/session/submit #response that delivered it, exactly as stored, never re-serialised. A VWC with no paired entry counts for nothing; an entry pairing with no VWC in presentation is ignored."
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext"
+    }
+  },
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "VTC Members Personhood-Assert — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "did",
+        "personhood",
+        "vmc",
+        "roleVac"
+      ],
+      "properties": {
+        "did": {
+          "type": "string",
+          "minLength": 1
+        },
+        "personhood": {
+          "type": "boolean",
+          "const": true,
+          "description": "Always true on success — the flag flipped or stayed asserted."
+        },
+        "vmc": {
+          "type": "object",
+          "description": "Re-issued membership credential carrying the asserted personhood (opaque here)."
+        },
+        "roleVac": {
+          "type": "object",
+          "description": "Re-issued role credential (opaque here): a Verifiable Authority Credential (`type` including `AuthorityCredential`) issued by the community with `issuerScope` `public`, whose `credentialSubject.authority` is `{ scope: <community DID>, actions: [\"role:<name>\"] }` — the shape vtc/vetting/vetters/grant/0.1 issues."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext"
+        }
+      }
+    },
+    "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-]+)+$"
+      }
+    },
+    "OutcomeEvidence": {
+      "title": "OutcomeEvidence",
+      "description": "One witnessing session's outcome evidence. `session` is the initiating witness/session document; `outcome` is the terminal witness/session/submit #response that the initiating document's own specification declares as its outcome evidence, under the witness's proof, delivering the VWC and its vwcDigestMultibase. A consumer pairs them with a presented VWC by SPEC §4.9.4's four checks and the witnessing checks of witness/session/submit (This response is the outcome evidence).",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "session",
+        "outcome"
+      ],
+      "properties": {
+        "session": {
+          "$ref": "#/$defs/EvidenceDocument",
+          "description": "The witness/session document that opened the session. The VWC's taskContext is its id and its taskDigestMultibase is computed over it (SPEC §4.9.3)."
+        },
+        "outcome": {
+          "$ref": "#/$defs/EvidenceDocument",
+          "description": "The witness/session/submit #response that closed the session, under the witness's proof. It carries the VWC and its vwcDigestMultibase."
+        }
+      }
+    },
+    "EvidenceDocument": {
+      "title": "EvidenceDocument",
+      "description": "A whole Trust Task document — `id`, `type`, `payload` and every other member, `proof` included — carried exactly as it was sent or received, never re-serialised: a task digest and a proof are taken over its members, and a re-serialised copy reproduces neither reliably. Typed as an open object so every member survives; the checks that give it meaning belong to the task that reads it.",
+      "type": "object",
+      "minProperties": 1
+    }
+  }
+} as const;
+
+/** As {@link PAYLOAD_SCHEMA}, for the success-response variant. */
+export const RESPONSE_PAYLOAD_SCHEMA = {
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$ref": "#/$defs/Response",
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "VTC Members Personhood-Assert — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "did",
+        "personhood",
+        "vmc",
+        "roleVac"
+      ],
+      "properties": {
+        "did": {
+          "type": "string",
+          "minLength": 1
+        },
+        "personhood": {
+          "type": "boolean",
+          "const": true,
+          "description": "Always true on success — the flag flipped or stayed asserted."
+        },
+        "vmc": {
+          "type": "object",
+          "description": "Re-issued membership credential carrying the asserted personhood (opaque here)."
+        },
+        "roleVac": {
+          "type": "object",
+          "description": "Re-issued role credential (opaque here): a Verifiable Authority Credential (`type` including `AuthorityCredential`) issued by the community with `issuerScope` `public`, whose `credentialSubject.authority` is `{ scope: <community DID>, actions: [\"role:<name>\"] }` — the shape vtc/vetting/vetters/grant/0.1 issues."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext"
+        }
+      }
+    },
+    "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-]+)+$"
+      }
+    },
+    "OutcomeEvidence": {
+      "title": "OutcomeEvidence",
+      "description": "One witnessing session's outcome evidence. `session` is the initiating witness/session document; `outcome` is the terminal witness/session/submit #response that the initiating document's own specification declares as its outcome evidence, under the witness's proof, delivering the VWC and its vwcDigestMultibase. A consumer pairs them with a presented VWC by SPEC §4.9.4's four checks and the witnessing checks of witness/session/submit (This response is the outcome evidence).",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "session",
+        "outcome"
+      ],
+      "properties": {
+        "session": {
+          "$ref": "#/$defs/EvidenceDocument",
+          "description": "The witness/session document that opened the session. The VWC's taskContext is its id and its taskDigestMultibase is computed over it (SPEC §4.9.3)."
+        },
+        "outcome": {
+          "$ref": "#/$defs/EvidenceDocument",
+          "description": "The witness/session/submit #response that closed the session, under the witness's proof. It carries the VWC and its vwcDigestMultibase."
+        }
+      }
+    },
+    "EvidenceDocument": {
+      "title": "EvidenceDocument",
+      "description": "A whole Trust Task document — `id`, `type`, `payload` and every other member, `proof` included — carried exactly as it was sent or received, never re-serialised: a task digest and a proof are taken over its members, and a re-serialised copy reproduces neither reliably. Typed as an open object so every member survives; the checks that give it meaning belong to the task that reads it.",
+      "type": "object",
+      "minProperties": 1
+    }
+  }
+} as const;
+
+/**
+ * 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,
+} as const;
+
+/**
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
+ * tracks the *issuer* party's requirement because a response swaps the
+ * parties (§7.3 item 5).
+ */
+export const RESPONSE_SPEC = {
+  typeUri: RESPONSE_TYPE_URI,
+  isBearer: false,
+  isProofRequired: true,
+  isRecipientRequired: true,
+  isIssuedAtRequired: true,
+  payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
+} as const;

package/src/vtc/members/registry-consent/0.1/payload.ts

@@ -0,0 +1,231 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vtc/members/registry-consent/0.1/payload.schema.json
+ */
+
+import type { Ext } from "../../../../_shared/components.js";
+
+
+export interface VTCMembersRegistryConsentPayload {
+  /**
+   * The member's own decision on trust-registry publication: `true` consents to the community publishing their membership in its trust registry, `false` withdraws that consent. Applies to the member who signed the document, and to no one else.
+   */
+  publishConsent: boolean;
+  ext?: Ext;
+}
+export interface VTCMembersRegistryConsentResponsePayload {
+  /**
+   * The member whose consent this is: the document's signer.
+   */
+  did: string;
+  /**
+   * The consent now recorded on the member record.
+   */
+  publishConsent: boolean;
+  /**
+   * Whether this document changed the recorded consent. `false` when the member restated the value already recorded.
+   */
+  changed: boolean;
+  /**
+   * What the community did about its trust registry. `queued`: a registry sync job carrying the change is queued (publication on a grant, removal on a withdrawal). `notConfigured`: the community publishes to no trust registry at present; the consent is recorded and governs any registry configured later. `unchanged`: nothing to sync, because the consent did not change, or because the community does not publish this member on other grounds (consent permits publication; it does not oblige it).
+   */
+  registrySync: "queued" | "notConfigured" | "unchanged";
+  /**
+   * When the community recorded the consent now in force — this document's execution when `changed` is `true`, the earlier change otherwise.
+   */
+  effectiveAt: 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 const TYPE_URI = "https://trusttasks.org/spec/vtc/members/registry-consent/0.1" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = VTCMembersRegistryConsentPayload;
+
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/vtc/members/registry-consent/0.1#response" as const;
+
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = VTCMembersRegistryConsentResponsePayload;
+
+/**
+ * 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/registry-consent/0.1",
+  "title": "VTC Members Registry Consent — payload",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "publishConsent"
+  ],
+  "properties": {
+    "publishConsent": {
+      "type": "boolean",
+      "description": "The member's own decision on trust-registry publication: `true` consents to the community publishing their membership in its trust registry, `false` withdraws that consent. Applies to the member who signed the document, and to no one else."
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext"
+    }
+  },
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "VTC Members Registry Consent — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "did",
+        "publishConsent",
+        "changed",
+        "registrySync",
+        "effectiveAt"
+      ],
+      "properties": {
+        "did": {
+          "type": "string",
+          "minLength": 1,
+          "description": "The member whose consent this is: the document's signer."
+        },
+        "publishConsent": {
+          "type": "boolean",
+          "description": "The consent now recorded on the member record."
+        },
+        "changed": {
+          "type": "boolean",
+          "description": "Whether this document changed the recorded consent. `false` when the member restated the value already recorded."
+        },
+        "registrySync": {
+          "type": "string",
+          "enum": [
+            "queued",
+            "notConfigured",
+            "unchanged"
+          ],
+          "description": "What the community did about its trust registry. `queued`: a registry sync job carrying the change is queued (publication on a grant, removal on a withdrawal). `notConfigured`: the community publishes to no trust registry at present; the consent is recorded and governs any registry configured later. `unchanged`: nothing to sync, because the consent did not change, or because the community does not publish this member on other grounds (consent permits publication; it does not oblige it)."
+        },
+        "effectiveAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When the community recorded the consent now in force — this document's execution when `changed` is `true`, the earlier change otherwise."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext"
+        }
+      }
+    },
+    "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-]+)+$"
+      }
+    }
+  }
+} as const;
+
+/** As {@link PAYLOAD_SCHEMA}, for the success-response variant. */
+export const RESPONSE_PAYLOAD_SCHEMA = {
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$ref": "#/$defs/Response",
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "VTC Members Registry Consent — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "did",
+        "publishConsent",
+        "changed",
+        "registrySync",
+        "effectiveAt"
+      ],
+      "properties": {
+        "did": {
+          "type": "string",
+          "minLength": 1,
+          "description": "The member whose consent this is: the document's signer."
+        },
+        "publishConsent": {
+          "type": "boolean",
+          "description": "The consent now recorded on the member record."
+        },
+        "changed": {
+          "type": "boolean",
+          "description": "Whether this document changed the recorded consent. `false` when the member restated the value already recorded."
+        },
+        "registrySync": {
+          "type": "string",
+          "enum": [
+            "queued",
+            "notConfigured",
+            "unchanged"
+          ],
+          "description": "What the community did about its trust registry. `queued`: a registry sync job carrying the change is queued (publication on a grant, removal on a withdrawal). `notConfigured`: the community publishes to no trust registry at present; the consent is recorded and governs any registry configured later. `unchanged`: nothing to sync, because the consent did not change, or because the community does not publish this member on other grounds (consent permits publication; it does not oblige it)."
+        },
+        "effectiveAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When the community recorded the consent now in force — this document's execution when `changed` is `true`, the earlier change otherwise."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext"
+        }
+      }
+    },
+    "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-]+)+$"
+      }
+    }
+  }
+} as const;
+
+/**
+ * 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,
+} as const;
+
+/**
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
+ * tracks the *issuer* party's requirement because a response swaps the
+ * parties (§7.3 item 5).
+ */
+export const RESPONSE_SPEC = {
+  typeUri: RESPONSE_TYPE_URI,
+  isBearer: false,
+  isProofRequired: true,
+  isRecipientRequired: true,
+  isIssuedAtRequired: true,
+  payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
+} as const;

package/src/vtc/members/update/0.1/payload.ts

@@ -20,7 +20,7 @@ export interface VTCMembersUpdatePayload {
    */
   label?: string | null;
   /**
-   * New directory-publish consent.
+   * New directory-publish consent. May only withdraw consent (`true` → `false`) or restate the current value; `true` for a member whose record does not already carry it is refused with `consentGrantForbidden`. Consent is the member's own, given by `registryConsent` on `vtc/join-requests/submit`.
    */
   publishConsent?: boolean;
   departurePreference?: "purge" | "tombstone" | "historical" | "policydefault";
@@ -89,7 +89,7 @@ export const PAYLOAD_SCHEMA = {
     },
     "publishConsent": {
       "type": "boolean",
-      "description": "New directory-publish consent."
+      "description": "New directory-publish consent. May only withdraw consent (`true` → `false`) or restate the current value; `true` for a member whose record does not already carry it is refused with `consentGrantForbidden`. Consent is the member's own, given by `registryConsent` on `vtc/join-requests/submit`."
     },
     "departurePreference": {
       "type": "string",

package/src/witness/_shared/0.1/outcome-evidence.ts

@@ -0,0 +1,17 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/witness/_shared/0.1/outcome-evidence.schema.json
+ */
+
+/**
+ * The outcome evidence of one witnessing session (SPEC §4.9.4): the witness/session document that opened it and the witness/session/submit #response that closed it, which together let a party outside the exchange pair a Verifiable Witness Credential with the session it cites. Defined once because more than one task carries it: the VTA that stores a VWC returns it (vta/witness/accept), and a holder presenting a VWC ships it beside the presentation (vtc/members/personhood/assert). Not itself a Trust Task specification: the `_shared` folder is skipped by the registry build and the codegen.
+ */
+export interface WitnessingOutcomeEvidenceSharedDefinitions {
+  [k: string]: unknown | undefined;
+}
+
+/**
+ * The definitions this shared schema publishes, hoisted to one declaration each.
+ * See "../../../_shared/components.js".
+ */
+export type { EvidenceDocument, OutcomeEvidence } from "../../../_shared/components.js";