@openvtc/trust-tasks 0.22.3 → 0.22.5

package/src/vtc/join-requests/status/0.1/payload.ts

@@ -11,6 +11,10 @@ export interface VTCJoinRequestsStatusPayload {
    * The request to poll. Optional: an applicant whose first reply was lost never received an id, and the id-less poll — resolved from the authenticated applicant's own DID — is the only form available to them. Supply it when you have it; a consumer that has it MUST prefer it over inferring the request from the caller.
    */
   requestId?: string;
+  /**
+   * Ask the community to deliver again the membership credential and role credential it already issued for this request, when the request is `approved` and they have not arrived. Set it only after a response of `approved` with `credentialsDelivered: false` and a reasonable wait; the community rate-limits it and answers in `credentialResend`. The community never issues new credentials in response.
+   */
+  resendCredentials?: boolean;
   ext?: Ext;
 }
 export interface VTCJoinRequestsStatusResponsePayload {
@@ -36,6 +40,18 @@ export interface VTCJoinRequestsStatusResponsePayload {
    * When more evidence is needed, the presentation-definition to satisfy (opaque here).
    */
   presentationDefinition?: {};
+  /**
+   * Whether the community holds the applicant's acknowledgement that the membership credential arrived. Present only when `status` is `approved`.
+   */
+  credentialsDelivered?: boolean;
+  /**
+   * The community's answer to `resendCredentials`. `queued`: a re-delivery of the already-issued credentials is queued. `notNeeded`: delivery is already acknowledged. `rateLimited`: a re-delivery was honoured too recently; see `retryAfter`. Present only when `resendCredentials` was set and `status` is `approved`; absent then means the community does not support re-delivery.
+   */
+  credentialResend?: "queued" | "notNeeded" | "rateLimited";
+  /**
+   * The earliest time the community will honour another `resendCredentials`. Present only when `credentialResend` is `rateLimited`.
+   */
+  retryAfter?: string;
   ext?: Ext;
 }
 
@@ -75,6 +91,10 @@ export const PAYLOAD_SCHEMA = {
       "minLength": 1,
       "description": "The request to poll. Optional: an applicant whose first reply was lost never received an id, and the id-less poll — resolved from the authenticated applicant's own DID — is the only form available to them. Supply it when you have it; a consumer that has it MUST prefer it over inferring the request from the caller."
     },
+    "resendCredentials": {
+      "type": "boolean",
+      "description": "Ask the community to deliver again the membership credential and role credential it already issued for this request, when the request is `approved` and they have not arrived. Set it only after a response of `approved` with `credentialsDelivered: false` and a reasonable wait; the community rate-limits it and answers in `credentialResend`. The community never issues new credentials in response."
+    },
     "ext": {
       "$ref": "#/$defs/Ext"
     }
@@ -132,6 +152,24 @@ export const PAYLOAD_SCHEMA = {
           "type": "object",
           "description": "When more evidence is needed, the presentation-definition to satisfy (opaque here)."
         },
+        "credentialsDelivered": {
+          "type": "boolean",
+          "description": "Whether the community holds the applicant's acknowledgement that the membership credential arrived. Present only when `status` is `approved`."
+        },
+        "credentialResend": {
+          "type": "string",
+          "enum": [
+            "queued",
+            "notNeeded",
+            "rateLimited"
+          ],
+          "description": "The community's answer to `resendCredentials`. `queued`: a re-delivery of the already-issued credentials is queued. `notNeeded`: delivery is already acknowledged. `rateLimited`: a re-delivery was honoured too recently; see `retryAfter`. Present only when `resendCredentials` was set and `status` is `approved`; absent then means the community does not support re-delivery."
+        },
+        "retryAfter": {
+          "type": "string",
+          "format": "date-time",
+          "description": "The earliest time the community will honour another `resendCredentials`. Present only when `credentialResend` is `rateLimited`."
+        },
         "ext": {
           "$ref": "#/$defs/Ext"
         }
@@ -207,6 +245,24 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
           "type": "object",
           "description": "When more evidence is needed, the presentation-definition to satisfy (opaque here)."
         },
+        "credentialsDelivered": {
+          "type": "boolean",
+          "description": "Whether the community holds the applicant's acknowledgement that the membership credential arrived. Present only when `status` is `approved`."
+        },
+        "credentialResend": {
+          "type": "string",
+          "enum": [
+            "queued",
+            "notNeeded",
+            "rateLimited"
+          ],
+          "description": "The community's answer to `resendCredentials`. `queued`: a re-delivery of the already-issued credentials is queued. `notNeeded`: delivery is already acknowledged. `rateLimited`: a re-delivery was honoured too recently; see `retryAfter`. Present only when `resendCredentials` was set and `status` is `approved`; absent then means the community does not support re-delivery."
+        },
+        "retryAfter": {
+          "type": "string",
+          "format": "date-time",
+          "description": "The earliest time the community will honour another `resendCredentials`. Present only when `credentialResend` is `rateLimited`."
+        },
         "ext": {
           "$ref": "#/$defs/Ext"
         }
@@ -236,7 +292,7 @@ export const SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
-  isIssuedAtRequired: false,
+  isIssuedAtRequired: true,
   payloadSchema: PAYLOAD_SCHEMA,
 } as const;
 
@@ -250,6 +306,6 @@ export const RESPONSE_SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
-  isIssuedAtRequired: false,
+  isIssuedAtRequired: true,
   payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
 } as const;

package/src/vtc/join-requests/submit/0.3/payload.ts

@@ -0,0 +1,431 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vtc/join-requests/submit/0.3/payload.schema.json
+ */
+
+import type { DigestMultibase, Ext, Verdict, VerdictEffect, VerdictWith } from "../../../../_shared/components.js";
+
+
+export interface VTCJoinRequestsSubmitPayload {
+  /**
+   * The applicant's W3C Verifiable Presentation (opaque here), satisfying the community's join policy. The applicant DID is the document proof's signer — not a payload field.
+   */
+  vp: {};
+  /**
+   * The `requirementsDigest` of the criterion this submission is made under, as vtc/join-requests/manifest/0.3 published it. Absent: the community decides the submission under the first criterion, in the order it publishes them, that the submission meets.
+   */
+  criterion?: DigestMultibase;
+  /**
+   * Whether the applicant consents to trust-registry publication.
+   */
+  registryConsent?: boolean;
+  /**
+   * Opaque applicant-supplied extension bag.
+   */
+  extensions?: {};
+  /**
+   * The applicant's answers to the manifest's `requestedAttributes`: one entry per attribute given. Self-asserted and bound to the applicant by the document proof. A maintainer MUST refuse the submission with `attributesMissing` when a required attribute is absent and with `attributesUnrequested` when an entry names a type the manifest does not request.
+   *
+   * @maxItems 32
+   */
+  attributes?: {
+    /**
+     * A claim-type token from the persona claim-type registry (persona/_shared/0.1/CLAIM-TYPES.md) — `name.display`, `address.country` — or an `x:` extension token.
+     */
+    type: string;
+    /**
+     * The value the applicant gives. Self-asserted: the applicant's own statement, bound to them by the document proof, and attested by nobody.
+     */
+    value: {
+      [k: string]: unknown | undefined;
+    };
+  }[];
+  ext?: Ext;
+}
+export interface VTCJoinRequestsSubmitResponsePayload {
+  /**
+   * Id of the created join request (a UUID).
+   */
+  requestId: string;
+  /**
+   * What the community decided about this submission.
+   *
+   * `0.1` returned `status: "pending"` — a constant, which could express only one of the four outcomes a submission actually has. A policy that admits outright, refuses outright, or asks for more evidence had to be reported as 'pending' or not at all.
+   */
+  verdict: Verdict;
+  ext?: Ext;
+}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { DigestMultibase, Ext, Verdict, VerdictEffect, VerdictWith };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/vtc/join-requests/submit/0.3" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = VTCJoinRequestsSubmitPayload;
+
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/vtc/join-requests/submit/0.3#response" as const;
+
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = VTCJoinRequestsSubmitResponsePayload;
+
+/**
+ * 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/join-requests/submit/0.3",
+  "title": "VTC Join-Requests Submit — payload",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "vp"
+  ],
+  "properties": {
+    "vp": {
+      "type": "object",
+      "description": "The applicant's W3C Verifiable Presentation (opaque here), satisfying the community's join policy. The applicant DID is the document proof's signer — not a payload field."
+    },
+    "criterion": {
+      "$ref": "#/$defs/DigestMultibase",
+      "description": "The `requirementsDigest` of the criterion this submission is made under, as vtc/join-requests/manifest/0.3 published it. Absent: the community decides the submission under the first criterion, in the order it publishes them, that the submission meets."
+    },
+    "registryConsent": {
+      "type": "boolean",
+      "description": "Whether the applicant consents to trust-registry publication."
+    },
+    "extensions": {
+      "type": "object",
+      "description": "Opaque applicant-supplied extension bag."
+    },
+    "attributes": {
+      "type": "array",
+      "maxItems": 32,
+      "description": "The applicant's answers to the manifest's `requestedAttributes`: one entry per attribute given. Self-asserted and bound to the applicant by the document proof. A maintainer MUST refuse the submission with `attributesMissing` when a required attribute is absent and with `attributesUnrequested` when an entry names a type the manifest does not request.",
+      "items": {
+        "type": "object",
+        "additionalProperties": false,
+        "required": [
+          "type",
+          "value"
+        ],
+        "properties": {
+          "type": {
+            "type": "string",
+            "minLength": 1,
+            "maxLength": 128,
+            "pattern": "^(x:)?[a-z][A-Za-z0-9]*(\\.[a-z][A-Za-z0-9]*)*$",
+            "description": "A claim-type token from the persona claim-type registry (persona/_shared/0.1/CLAIM-TYPES.md) — `name.display`, `address.country` — or an `x:` extension token."
+          },
+          "value": {
+            "description": "The value the applicant gives. Self-asserted: the applicant's own statement, bound to them by the document proof, and attested by nobody."
+          }
+        }
+      }
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext"
+    }
+  },
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "VTC Join-Requests Submit — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "requestId",
+        "verdict"
+      ],
+      "properties": {
+        "requestId": {
+          "type": "string",
+          "minLength": 1,
+          "description": "Id of the created join request (a UUID)."
+        },
+        "verdict": {
+          "$ref": "#/$defs/Verdict",
+          "description": "What the community decided about this submission.\n\n`0.1` returned `status: \"pending\"` — a constant, which could express only one of the four outcomes a submission actually has. A policy that admits outright, refuses outright, or asks for more evidence had to be reported as 'pending' or not at all."
+        },
+        "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-]+)+$"
+      }
+    },
+    "Verdict": {
+      "$anchor": "verdict",
+      "title": "Verdict",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "effect",
+        "with"
+      ],
+      "description": "A ceremony decision: the effect, plus its effect-dependent detail.",
+      "properties": {
+        "effect": {
+          "$ref": "#/$defs/VerdictEffect"
+        },
+        "with": {
+          "$ref": "#/$defs/VerdictWith"
+        }
+      }
+    },
+    "VerdictWith": {
+      "$anchor": "verdictWith",
+      "title": "VerdictWith",
+      "type": "object",
+      "additionalProperties": false,
+      "description": "The effect-dependent detail of a verdict.\n\nEvery member is optional at the schema level and which ones are meaningful depends on `effect`: `role` / `obligations` / `bundleRef` on `allow`, `code` / `reason` on `deny`, `queue` / `reason` on `refer`, `needs` / `presentationDefinition` on `requestMore`. The dependency is stated here rather than enforced by `if`/`then` per effect, so that the shape stays a single flat object a generated type can carry without a discriminated union per family — a deliberate trade of schema strictness for implementability, and the reason a consumer MUST branch on `effect` rather than on which members happen to be present.",
+      "properties": {
+        "role": {
+          "type": "string",
+          "minLength": 1,
+          "description": "The granted local role. `allow` only."
+        },
+        "obligations": {
+          "type": "object",
+          "description": "Conditions attached to the grant. `allow` only."
+        },
+        "bundleRef": {
+          "type": "object",
+          "description": "Pointer to a sealed credential bundle, added by the community where issuance occurred rather than emitted by the policy. `allow` only."
+        },
+        "code": {
+          "type": "string",
+          "minLength": 1,
+          "description": "Stable refusal code, safe to branch on. `deny` only."
+        },
+        "reason": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "maxLength": 1024,
+          "description": "Elaboration in prose, when the decider gave one. `deny` and `refer`."
+        },
+        "queue": {
+          "type": "string",
+          "minLength": 1,
+          "description": "Which review queue the decision was parked in, so an applicant can be told who now holds it. `refer` only."
+        },
+        "needs": {
+          "type": "array",
+          "items": {
+            "type": "string",
+            "minLength": 1
+          },
+          "description": "What further evidence is required, named so the applicant can act without a support conversation. `requestMore` only."
+        },
+        "presentationDefinition": {
+          "type": "object",
+          "description": "A machine-readable statement of the same request, so a wallet can satisfy it without a human reading `needs`. `requestMore` only."
+        }
+      }
+    },
+    "VerdictEffect": {
+      "$anchor": "verdictEffect",
+      "title": "VerdictEffect",
+      "type": "string",
+      "enum": [
+        "allow",
+        "deny",
+        "refer",
+        "requestMore"
+      ],
+      "description": "What the policy decided.\n\n`allow` — admitted. `deny` — refused, terminally for this submission. `refer` — parked for a human or quorum decision; the applicant is neither in nor out. `requestMore` — the policy cannot decide yet and names what further evidence it needs.\n\nThe four are not reducible to a pending/decided pair. `refer` and `requestMore` are both 'not decided', but they place the next action with different parties: `refer` waits on the community, `requestMore` waits on the applicant. A consumer that cannot tell them apart cannot tell a user whether to wait or to act."
+    },
+    "DigestMultibase": {
+      "title": "DigestMultibase",
+      "description": "A cryptographic digest as a multibase-encoded multihash — the encoding the W3C Verifiable Credentials Data Model 2.0 defines for `digestMultibase`, and the one `did:webvh` uses for its SCID and entry hashes.\n\nMultihash carries the hash algorithm in-band, so the value is self-describing and the wire format survives an algorithm change without a schema revision; multibase does the same for the base encoding, so a verifier never infers base58 from base64url by context. A bare hex string or a `sha-256:`-style prefix hard-codes one algorithm into the wire contract and is non-conforming here.\n\nThis definition constrains the *encoding only*. What the digest is computed over is stated by each referencing field, because it differs legitimately: a digest over a JSON document is taken over its RFC 8785 (JCS) canonicalization, while a digest over an opaque artifact is taken over its bytes. A field whose input is a JSON document and which does not name a canonicalization is not reproducible.\n\nRestricted to the two multibase headers W3C Controlled Identifiers 1.0 §2.4 normatively requires — `z` (base58btc) and `u` (base64url-no-pad). CID permits others but states that \"interoperability is not guaranteed between implementations using such values\", and a registry whose purpose is interoperability should not mint digests a conforming verifier may be unable to read. The alphabets are enforced rather than assumed: base58btc excludes 0, O, I and l, and an earlier permissive pattern let three published examples carry digests that were not valid base58 at all. base58btc is RECOMMENDED, for consistency with `did:key` and `did:webvh`.",
+      "type": "string",
+      "minLength": 16,
+      "pattern": "^(z[1-9A-HJ-NP-Za-km-z]+|u[A-Za-z0-9_-]+)$",
+      "examples": [
+        "zQmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR"
+      ]
+    }
+  }
+} 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 Join-Requests Submit — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "requestId",
+        "verdict"
+      ],
+      "properties": {
+        "requestId": {
+          "type": "string",
+          "minLength": 1,
+          "description": "Id of the created join request (a UUID)."
+        },
+        "verdict": {
+          "$ref": "#/$defs/Verdict",
+          "description": "What the community decided about this submission.\n\n`0.1` returned `status: \"pending\"` — a constant, which could express only one of the four outcomes a submission actually has. A policy that admits outright, refuses outright, or asks for more evidence had to be reported as 'pending' or not at all."
+        },
+        "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-]+)+$"
+      }
+    },
+    "Verdict": {
+      "$anchor": "verdict",
+      "title": "Verdict",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "effect",
+        "with"
+      ],
+      "description": "A ceremony decision: the effect, plus its effect-dependent detail.",
+      "properties": {
+        "effect": {
+          "$ref": "#/$defs/VerdictEffect"
+        },
+        "with": {
+          "$ref": "#/$defs/VerdictWith"
+        }
+      }
+    },
+    "VerdictWith": {
+      "$anchor": "verdictWith",
+      "title": "VerdictWith",
+      "type": "object",
+      "additionalProperties": false,
+      "description": "The effect-dependent detail of a verdict.\n\nEvery member is optional at the schema level and which ones are meaningful depends on `effect`: `role` / `obligations` / `bundleRef` on `allow`, `code` / `reason` on `deny`, `queue` / `reason` on `refer`, `needs` / `presentationDefinition` on `requestMore`. The dependency is stated here rather than enforced by `if`/`then` per effect, so that the shape stays a single flat object a generated type can carry without a discriminated union per family — a deliberate trade of schema strictness for implementability, and the reason a consumer MUST branch on `effect` rather than on which members happen to be present.",
+      "properties": {
+        "role": {
+          "type": "string",
+          "minLength": 1,
+          "description": "The granted local role. `allow` only."
+        },
+        "obligations": {
+          "type": "object",
+          "description": "Conditions attached to the grant. `allow` only."
+        },
+        "bundleRef": {
+          "type": "object",
+          "description": "Pointer to a sealed credential bundle, added by the community where issuance occurred rather than emitted by the policy. `allow` only."
+        },
+        "code": {
+          "type": "string",
+          "minLength": 1,
+          "description": "Stable refusal code, safe to branch on. `deny` only."
+        },
+        "reason": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "maxLength": 1024,
+          "description": "Elaboration in prose, when the decider gave one. `deny` and `refer`."
+        },
+        "queue": {
+          "type": "string",
+          "minLength": 1,
+          "description": "Which review queue the decision was parked in, so an applicant can be told who now holds it. `refer` only."
+        },
+        "needs": {
+          "type": "array",
+          "items": {
+            "type": "string",
+            "minLength": 1
+          },
+          "description": "What further evidence is required, named so the applicant can act without a support conversation. `requestMore` only."
+        },
+        "presentationDefinition": {
+          "type": "object",
+          "description": "A machine-readable statement of the same request, so a wallet can satisfy it without a human reading `needs`. `requestMore` only."
+        }
+      }
+    },
+    "VerdictEffect": {
+      "$anchor": "verdictEffect",
+      "title": "VerdictEffect",
+      "type": "string",
+      "enum": [
+        "allow",
+        "deny",
+        "refer",
+        "requestMore"
+      ],
+      "description": "What the policy decided.\n\n`allow` — admitted. `deny` — refused, terminally for this submission. `refer` — parked for a human or quorum decision; the applicant is neither in nor out. `requestMore` — the policy cannot decide yet and names what further evidence it needs.\n\nThe four are not reducible to a pending/decided pair. `refer` and `requestMore` are both 'not decided', but they place the next action with different parties: `refer` waits on the community, `requestMore` waits on the applicant. A consumer that cannot tell them apart cannot tell a user whether to wait or to act."
+    },
+    "DigestMultibase": {
+      "title": "DigestMultibase",
+      "description": "A cryptographic digest as a multibase-encoded multihash — the encoding the W3C Verifiable Credentials Data Model 2.0 defines for `digestMultibase`, and the one `did:webvh` uses for its SCID and entry hashes.\n\nMultihash carries the hash algorithm in-band, so the value is self-describing and the wire format survives an algorithm change without a schema revision; multibase does the same for the base encoding, so a verifier never infers base58 from base64url by context. A bare hex string or a `sha-256:`-style prefix hard-codes one algorithm into the wire contract and is non-conforming here.\n\nThis definition constrains the *encoding only*. What the digest is computed over is stated by each referencing field, because it differs legitimately: a digest over a JSON document is taken over its RFC 8785 (JCS) canonicalization, while a digest over an opaque artifact is taken over its bytes. A field whose input is a JSON document and which does not name a canonicalization is not reproducible.\n\nRestricted to the two multibase headers W3C Controlled Identifiers 1.0 §2.4 normatively requires — `z` (base58btc) and `u` (base64url-no-pad). CID permits others but states that \"interoperability is not guaranteed between implementations using such values\", and a registry whose purpose is interoperability should not mint digests a conforming verifier may be unable to read. The alphabets are enforced rather than assumed: base58btc excludes 0, O, I and l, and an earlier permissive pattern let three published examples carry digests that were not valid base58 at all. base58btc is RECOMMENDED, for consistency with `did:key` and `did:webvh`.",
+      "type": "string",
+      "minLength": 16,
+      "pattern": "^(z[1-9A-HJ-NP-Za-km-z]+|u[A-Za-z0-9_-]+)$",
+      "examples": [
+        "zQmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR"
+      ]
+    }
+  }
+} 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/schemas/accepts/list/0.1/payload.ts

@@ -3,7 +3,7 @@
  * Source: specs/vtc/schemas/accepts/list/0.1/payload.schema.json
  */
 
-import type { AcceptsCriterion, AcceptsCriterionId, ClaimType, CriterionDescription, DcqlQuery, Duration, Ext, ExtCritical, VettingDocumentation, VettingMethod, VettingRequirements } from "../../../../../_shared/components.js";
+import type { AcceptsCriterion_VtcV0_1 as AcceptsCriterion, AcceptsCriterionId, ClaimType, CriterionDescription_VtcV0_1 as CriterionDescription, DcqlQuery, Duration, Ext, ExtCritical, VettingDocumentation, VettingMethod, VettingRequirements } from "../../../../../_shared/components.js";
 
 
 /**