@openvtc/trust-tasks 0.28.8 → 0.28.10

package/src/notifications/notify/0.1/payload.ts

@@ -0,0 +1,420 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/notifications/notify/0.1/payload.schema.json
+ */
+
+import type { Did_NotificationsV0_1 as Did, Ext, Kind_NotificationsV0_1 as Kind, Notification, NotificationId, Status, Subject } from "../../../_shared/components.js";
+
+
+/**
+ * An originator tells the party a DID names — an individual, a group, a community or a network — that a thing exists which that party, or the parties it stands for, may act on or take part in: where it is held, its identifier there, the task that opens it, and the audience it concerns. Nothing of the thing's content. The outer document members (id, type, issuer, recipient, issuedAt, expiresAt, proof) are owned by the framework — SPEC §6.3.
+ */
+export interface NotificationsNotifyPayload {
+  notification: Notification;
+  ext?: Ext;
+}
+/**
+ * Receipt of a notification the recipient verified. The same whether the recipient held it, declined it under its acceptance policy, or relayed it on, and never saying which (VTI-NTF-023).
+ */
+export interface NotificationsNotifyResponsePayload {
+  notificationId: NotificationId;
+  /**
+   * The revision received, echoed.
+   */
+  revision: number;
+}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { Did, Ext, Kind, Notification, NotificationId, Status, Subject };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/notifications/notify/0.1" as const;
+
+/**
+ * The earlier version of this specification that this one declares it
+ * extends (front matter `extends`, SPEC §5.2 "Declared extension"), or
+ * `null`. Only the direct declaration — follow the chain with
+ * `extendsChain` / `readForSpec`.
+ */
+export const EXTENDS: string | null = null;
+
+/**
+ * Why this version is deprecated, or `null` while it is current. A
+ * superseded or retired version is still supported, and is withdrawn from
+ * this package in a later scheduled batch (SPEC "Superseded and Withdrawn
+ * Versions").
+ */
+export const DEPRECATION: string | null = null;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = NotificationsNotifyPayload;
+
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/notifications/notify/0.1#response" as const;
+
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = NotificationsNotifyResponsePayload;
+
+/**
+ * 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/notifications/notify/0.1",
+  "title": "Notifications — Notify — payload",
+  "description": "An originator tells the party a DID names — an individual, a group, a community or a network — that a thing exists which that party, or the parties it stands for, may act on or take part in: where it is held, its identifier there, the task that opens it, and the audience it concerns. Nothing of the thing's content. The outer document members (id, type, issuer, recipient, issuedAt, expiresAt, proof) are owned by the framework — SPEC §6.3.",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "notification"
+  ],
+  "properties": {
+    "notification": {
+      "$ref": "#/$defs/Notification"
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext"
+    }
+  },
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "Notifications — Notify — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "notificationId",
+        "revision"
+      ],
+      "description": "Receipt of a notification the recipient verified. The same whether the recipient held it, declined it under its acceptance policy, or relayed it on, and never saying which (VTI-NTF-023).",
+      "properties": {
+        "notificationId": {
+          "$ref": "#/$defs/NotificationId"
+        },
+        "revision": {
+          "type": "integer",
+          "minimum": 1,
+          "maximum": 1000000,
+          "description": "The revision received, echoed."
+        }
+      }
+    },
+    "NotificationId": {
+      "title": "NotificationId",
+      "description": "The originator's identifier for one notification, unique among the notifications that originator issues and the same in every document that carries it — retries, re-issued documents and relayed copies alike. It is the notification's idempotency key (VTI-NTF-021). Compared for equality only. An originator SHOULD make it unguessable and SHOULD NOT make it descriptive: it travels as far as the notification does.",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 256,
+      "pattern": "^[A-Za-z0-9._~:-]+$"
+    },
+    "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-]+)+$"
+      }
+    },
+    "Notification": {
+      "title": "Notification",
+      "description": "The members of one notification, as notifications/notify carries them and as a recipient's agent records them. The originator is the `issuer` of the notifications/notify document and the addressee its `recipient`; neither is repeated here, because the originator's proof covers both.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "notificationId",
+        "revision",
+        "kind",
+        "subject",
+        "audience",
+        "status",
+        "relayable"
+      ],
+      "properties": {
+        "notificationId": {
+          "$ref": "#/$defs/NotificationId"
+        },
+        "revision": {
+          "type": "integer",
+          "minimum": 1,
+          "maximum": 1000000,
+          "description": "The revision of this notification. A recipient replaces the record it holds with a higher revision and leaves it unchanged for an equal or lower one (VTI-NTF-022). The first revision is 1."
+        },
+        "kind": {
+          "$ref": "#/$defs/Kind"
+        },
+        "subject": {
+          "$ref": "#/$defs/Subject"
+        },
+        "audience": {
+          "$ref": "#/$defs/Did",
+          "description": "The DID whose holders or members the thing concerns — for an election under a credential roll, the DID the roll names (`roll.memberOf`); otherwise the community's own. It says whom the thing is for, not that the recipient is one of them: a recipient may be the audience itself, or a party the audience relayed the notification to."
+        },
+        "status": {
+          "$ref": "#/$defs/Status"
+        },
+        "relayable": {
+          "type": "boolean",
+          "description": "Whether the addressee may relay this notification to the parties it stands for (notifications/relay). The originator states it explicitly; an addressee MUST NOT relay a notification whose `relayable` is false, or whose kind may not be relayed (VTI-NTF-041)."
+        },
+        "validFrom": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When the thing can first be acted on — for an election, when voting opens. Absent: it can be acted on now."
+        },
+        "validUntil": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When the thing can no longer be acted on, and the notification lapses — for an election, when voting closes. A recipient discards a notification received after it (VTI-NTF-032). Absent: the kind's definition says when it lapses."
+        }
+      }
+    },
+    "Status": {
+      "title": "Status",
+      "description": "Whether the thing is still open to the audience: `available`, or `withdrawn` — cancelled by its holder, or no longer open to the audience — in which case the recipient keeps the record only to show that it was withdrawn (VTI-NTF-024).",
+      "type": "string",
+      "enum": [
+        "available",
+        "withdrawn"
+      ]
+    },
+    "Did": {
+      "title": "Did",
+      "description": "A DID.",
+      "type": "string",
+      "minLength": 8,
+      "maxLength": 2048,
+      "pattern": "^did:[a-z0-9]+:\\S+$"
+    },
+    "Subject": {
+      "title": "Subject",
+      "description": "Where the thing is and how to open it. Only these three members: what the thing contains is shown by its holder, to a reader it admits, when the thing is opened with `openWith`.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "heldBy",
+        "id",
+        "openWith"
+      ],
+      "properties": {
+        "heldBy": {
+          "$ref": "#/$defs/Did",
+          "description": "The DID of the party holding the thing — for an election, the community. The party a recipient sends `openWith` to."
+        },
+        "id": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 256,
+          "description": "The thing's identifier at `heldBy`, in the form the `openWith` task takes it — for an election, its `electionId`."
+        },
+        "openWith": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 512,
+          "pattern": "^https://\\S+$",
+          "description": "The Type URI of the Trust Task by which a recipient opens the thing at `heldBy` — for an election, `https://trusttasks.org/spec/vtc/elections/show/0.6`. A recipient opens it only at its principal's choice (VTI-NTF-053), and only by a version of that task it and `heldBy` both serve."
+        }
+      }
+    },
+    "Kind": {
+      "title": "Kind",
+      "description": "What the thing is. Either a registered kind — one lowerCamelCase name in the VTI specification's notification kind registry (Appendix G), such as `election` — or an unregistered kind, written `<reverse-DNS domain>:<name>` under a domain its definer controls, such as `org.example:meetingInvite`. A recipient that does not recognise a kind holds, lists and discards it and does nothing else with it (VTI-NTF-012).",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 256,
+      "pattern": "^([a-z][a-zA-Z0-9]{0,63}|[a-z0-9]+(-[a-z0-9]+)*(\\.[a-z0-9]+(-[a-z0-9]+)*)+:[a-z][a-zA-Z0-9]{0,63})$"
+    }
+  }
+} 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": "Notifications — Notify — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "notificationId",
+        "revision"
+      ],
+      "description": "Receipt of a notification the recipient verified. The same whether the recipient held it, declined it under its acceptance policy, or relayed it on, and never saying which (VTI-NTF-023).",
+      "properties": {
+        "notificationId": {
+          "$ref": "#/$defs/NotificationId"
+        },
+        "revision": {
+          "type": "integer",
+          "minimum": 1,
+          "maximum": 1000000,
+          "description": "The revision received, echoed."
+        }
+      }
+    },
+    "NotificationId": {
+      "title": "NotificationId",
+      "description": "The originator's identifier for one notification, unique among the notifications that originator issues and the same in every document that carries it — retries, re-issued documents and relayed copies alike. It is the notification's idempotency key (VTI-NTF-021). Compared for equality only. An originator SHOULD make it unguessable and SHOULD NOT make it descriptive: it travels as far as the notification does.",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 256,
+      "pattern": "^[A-Za-z0-9._~:-]+$"
+    },
+    "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-]+)+$"
+      }
+    },
+    "Notification": {
+      "title": "Notification",
+      "description": "The members of one notification, as notifications/notify carries them and as a recipient's agent records them. The originator is the `issuer` of the notifications/notify document and the addressee its `recipient`; neither is repeated here, because the originator's proof covers both.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "notificationId",
+        "revision",
+        "kind",
+        "subject",
+        "audience",
+        "status",
+        "relayable"
+      ],
+      "properties": {
+        "notificationId": {
+          "$ref": "#/$defs/NotificationId"
+        },
+        "revision": {
+          "type": "integer",
+          "minimum": 1,
+          "maximum": 1000000,
+          "description": "The revision of this notification. A recipient replaces the record it holds with a higher revision and leaves it unchanged for an equal or lower one (VTI-NTF-022). The first revision is 1."
+        },
+        "kind": {
+          "$ref": "#/$defs/Kind"
+        },
+        "subject": {
+          "$ref": "#/$defs/Subject"
+        },
+        "audience": {
+          "$ref": "#/$defs/Did",
+          "description": "The DID whose holders or members the thing concerns — for an election under a credential roll, the DID the roll names (`roll.memberOf`); otherwise the community's own. It says whom the thing is for, not that the recipient is one of them: a recipient may be the audience itself, or a party the audience relayed the notification to."
+        },
+        "status": {
+          "$ref": "#/$defs/Status"
+        },
+        "relayable": {
+          "type": "boolean",
+          "description": "Whether the addressee may relay this notification to the parties it stands for (notifications/relay). The originator states it explicitly; an addressee MUST NOT relay a notification whose `relayable` is false, or whose kind may not be relayed (VTI-NTF-041)."
+        },
+        "validFrom": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When the thing can first be acted on — for an election, when voting opens. Absent: it can be acted on now."
+        },
+        "validUntil": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When the thing can no longer be acted on, and the notification lapses — for an election, when voting closes. A recipient discards a notification received after it (VTI-NTF-032). Absent: the kind's definition says when it lapses."
+        }
+      }
+    },
+    "Status": {
+      "title": "Status",
+      "description": "Whether the thing is still open to the audience: `available`, or `withdrawn` — cancelled by its holder, or no longer open to the audience — in which case the recipient keeps the record only to show that it was withdrawn (VTI-NTF-024).",
+      "type": "string",
+      "enum": [
+        "available",
+        "withdrawn"
+      ]
+    },
+    "Did": {
+      "title": "Did",
+      "description": "A DID.",
+      "type": "string",
+      "minLength": 8,
+      "maxLength": 2048,
+      "pattern": "^did:[a-z0-9]+:\\S+$"
+    },
+    "Subject": {
+      "title": "Subject",
+      "description": "Where the thing is and how to open it. Only these three members: what the thing contains is shown by its holder, to a reader it admits, when the thing is opened with `openWith`.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "heldBy",
+        "id",
+        "openWith"
+      ],
+      "properties": {
+        "heldBy": {
+          "$ref": "#/$defs/Did",
+          "description": "The DID of the party holding the thing — for an election, the community. The party a recipient sends `openWith` to."
+        },
+        "id": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 256,
+          "description": "The thing's identifier at `heldBy`, in the form the `openWith` task takes it — for an election, its `electionId`."
+        },
+        "openWith": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 512,
+          "pattern": "^https://\\S+$",
+          "description": "The Type URI of the Trust Task by which a recipient opens the thing at `heldBy` — for an election, `https://trusttasks.org/spec/vtc/elections/show/0.6`. A recipient opens it only at its principal's choice (VTI-NTF-053), and only by a version of that task it and `heldBy` both serve."
+        }
+      }
+    },
+    "Kind": {
+      "title": "Kind",
+      "description": "What the thing is. Either a registered kind — one lowerCamelCase name in the VTI specification's notification kind registry (Appendix G), such as `election` — or an unregistered kind, written `<reverse-DNS domain>:<name>` under a domain its definer controls, such as `org.example:meetingInvite`. A recipient that does not recognise a kind holds, lists and discards it and does nothing else with it (VTI-NTF-012).",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 256,
+      "pattern": "^([a-z][a-zA-Z0-9]{0,63}|[a-z0-9]+(-[a-z0-9]+)*(\\.[a-z0-9]+(-[a-z0-9]+)*)+:[a-z][a-zA-Z0-9]{0,63})$"
+    }
+  }
+} 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: false,
+  isRecipientRequired: true,
+  isIssuedAtRequired: true,
+  payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
+} as const;

package/src/notifications/relay/0.1/payload.ts

@@ -0,0 +1,220 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/notifications/relay/0.1/payload.schema.json
+ */
+
+import type { Ext, NotificationId } from "../../../_shared/components.js";
+
+
+/**
+ * A party that stands for others — a group, a community, a network — passes a notification it was addressed to on to one of them, carrying the document it received exactly as received, proof included, so the final recipient verifies the originator's own signature. The outer document members (id, type, issuer, recipient, issuedAt, expiresAt, proof) are owned by the framework — SPEC §6.3.
+ */
+export interface NotificationsRelayPayload {
+  forwarded: ForwardedDocument;
+  ext?: Ext;
+}
+/**
+ * The Trust Task document the relayer received, kept whole and exactly as received — proof included — never restated, re-serialised from a typed form, or re-signed: a notifications/notify/0.1 document, or a notifications/relay/0.1 document whose own `forwarded` carries the next layer in. Deliberately an opaque object, so that every member the originator signed — `issuedAt`, `expiresAt`, `threadId` and any other envelope member — survives every relay byte for byte. Its `recipient` MUST be this relay's `issuer`, because only the addressee of a notification may relay it (VTI-NTF-041). The recipient validates each layer as a document of its own `type`, to at most four relays in all (VTI-NTF-042).
+ */
+export interface ForwardedDocument {}
+/**
+ * Receipt of a relay the recipient verified, naming the innermost notification. The same whether the recipient held it, declined it under its acceptance policy, or relayed it on, and never saying which (VTI-NTF-023).
+ */
+export interface NotificationsRelayResponsePayload {
+  notificationId: NotificationId;
+  /**
+   * The revision of the innermost notification, echoed.
+   */
+  revision: number;
+}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { Ext, NotificationId };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/notifications/relay/0.1" as const;
+
+/**
+ * The earlier version of this specification that this one declares it
+ * extends (front matter `extends`, SPEC §5.2 "Declared extension"), or
+ * `null`. Only the direct declaration — follow the chain with
+ * `extendsChain` / `readForSpec`.
+ */
+export const EXTENDS: string | null = null;
+
+/**
+ * Why this version is deprecated, or `null` while it is current. A
+ * superseded or retired version is still supported, and is withdrawn from
+ * this package in a later scheduled batch (SPEC "Superseded and Withdrawn
+ * Versions").
+ */
+export const DEPRECATION: string | null = null;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = NotificationsRelayPayload;
+
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/notifications/relay/0.1#response" as const;
+
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = NotificationsRelayResponsePayload;
+
+/**
+ * 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/notifications/relay/0.1",
+  "title": "Notifications — Relay — payload",
+  "description": "A party that stands for others — a group, a community, a network — passes a notification it was addressed to on to one of them, carrying the document it received exactly as received, proof included, so the final recipient verifies the originator's own signature. The outer document members (id, type, issuer, recipient, issuedAt, expiresAt, proof) are owned by the framework — SPEC §6.3.",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "forwarded"
+  ],
+  "properties": {
+    "forwarded": {
+      "$ref": "#/$defs/ForwardedDocument"
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext"
+    }
+  },
+  "$defs": {
+    "ForwardedDocument": {
+      "title": "ForwardedDocument",
+      "description": "The Trust Task document the relayer received, kept whole and exactly as received — proof included — never restated, re-serialised from a typed form, or re-signed: a notifications/notify/0.1 document, or a notifications/relay/0.1 document whose own `forwarded` carries the next layer in. Deliberately an opaque object, so that every member the originator signed — `issuedAt`, `expiresAt`, `threadId` and any other envelope member — survives every relay byte for byte. Its `recipient` MUST be this relay's `issuer`, because only the addressee of a notification may relay it (VTI-NTF-041). The recipient validates each layer as a document of its own `type`, to at most four relays in all (VTI-NTF-042).",
+      "type": "object",
+      "minProperties": 1
+    },
+    "Response": {
+      "$anchor": "response",
+      "title": "Notifications — Relay — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "notificationId",
+        "revision"
+      ],
+      "description": "Receipt of a relay the recipient verified, naming the innermost notification. The same whether the recipient held it, declined it under its acceptance policy, or relayed it on, and never saying which (VTI-NTF-023).",
+      "properties": {
+        "notificationId": {
+          "$ref": "#/$defs/NotificationId"
+        },
+        "revision": {
+          "type": "integer",
+          "minimum": 1,
+          "maximum": 1000000,
+          "description": "The revision of the innermost notification, echoed."
+        }
+      }
+    },
+    "NotificationId": {
+      "title": "NotificationId",
+      "description": "The originator's identifier for one notification, unique among the notifications that originator issues and the same in every document that carries it — retries, re-issued documents and relayed copies alike. It is the notification's idempotency key (VTI-NTF-021). Compared for equality only. An originator SHOULD make it unguessable and SHOULD NOT make it descriptive: it travels as far as the notification does.",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 256,
+      "pattern": "^[A-Za-z0-9._~:-]+$"
+    },
+    "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": {
+    "ForwardedDocument": {
+      "title": "ForwardedDocument",
+      "description": "The Trust Task document the relayer received, kept whole and exactly as received — proof included — never restated, re-serialised from a typed form, or re-signed: a notifications/notify/0.1 document, or a notifications/relay/0.1 document whose own `forwarded` carries the next layer in. Deliberately an opaque object, so that every member the originator signed — `issuedAt`, `expiresAt`, `threadId` and any other envelope member — survives every relay byte for byte. Its `recipient` MUST be this relay's `issuer`, because only the addressee of a notification may relay it (VTI-NTF-041). The recipient validates each layer as a document of its own `type`, to at most four relays in all (VTI-NTF-042).",
+      "type": "object",
+      "minProperties": 1
+    },
+    "Response": {
+      "$anchor": "response",
+      "title": "Notifications — Relay — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "notificationId",
+        "revision"
+      ],
+      "description": "Receipt of a relay the recipient verified, naming the innermost notification. The same whether the recipient held it, declined it under its acceptance policy, or relayed it on, and never saying which (VTI-NTF-023).",
+      "properties": {
+        "notificationId": {
+          "$ref": "#/$defs/NotificationId"
+        },
+        "revision": {
+          "type": "integer",
+          "minimum": 1,
+          "maximum": 1000000,
+          "description": "The revision of the innermost notification, echoed."
+        }
+      }
+    },
+    "NotificationId": {
+      "title": "NotificationId",
+      "description": "The originator's identifier for one notification, unique among the notifications that originator issues and the same in every document that carries it — retries, re-issued documents and relayed copies alike. It is the notification's idempotency key (VTI-NTF-021). Compared for equality only. An originator SHOULD make it unguessable and SHOULD NOT make it descriptive: it travels as far as the notification does.",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 256,
+      "pattern": "^[A-Za-z0-9._~:-]+$"
+    },
+    "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: false,
+  isRecipientRequired: true,
+  isIssuedAtRequired: true,
+  payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
+} as const;

package/src/voting/_shared/0.4/voting.ts

@@ -0,0 +1,17 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/voting/_shared/0.4/voting.schema.json
+ */
+
+/**
+ * Reusable $defs for the voting/*, vtc/elections/* and vta/pcs/voter/* task families. Not itself a Trust Task specification. The conventions these shapes serve are in ../0.1/CONVENTIONS.md, which describes these definitions by their 0.2 member names (unchanged in 0.3 and 0.4) and notes the 0.1 names; the normative requirements are VTI-VOT-001 – 100 of the VTI specification.
+ */
+export interface CommunityVotingSharedDefinitions {
+  [k: string]: unknown | undefined;
+}
+
+/**
+ * The definitions this shared schema publishes, hoisted to one declaration each.
+ * See "../../../_shared/components.js".
+ */
+export type { Answer, Ballot, BoardHead, BoardVisibility, Disclosure_VotingV0_4 as Disclosure, ElectionId, ElectionKey, ElectionResult, ElectionState, ElectionSummary, GroupElement, Key_VotingV0_1 as Key, Manifest_VotingV0_4 as Manifest, Multibase_VotingV0_1 as Multibase, Question, QuestionOption, QuestionResult, Revote, RollCredentialDisclosure, RollRule_VotingV0_4 as RollRule, SecrecyLevel, SignedRequest, TrusteeCeremony, TrusteeIndex, Trustees, VotingParameters } from "../../../_shared/components.js";