@openvtc/trust-tasks 0.21.11 → 0.21.13

package/src/vtc/join-requests/vetting/show/0.1/payload.ts

@@ -0,0 +1,740 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vtc/join-requests/vetting/show/0.1/payload.schema.json
+ */
+
+import type { DigestMultibase, Ext, VettingMethod, VettingRelationship } from "../../../../../_shared/components.js";
+
+
+/**
+ * An administrator reads the vetting facts one join request was decided on. The outer document members are owned by the framework — SPEC §6.3.
+ */
+export interface VTCJoinRequestsVettingShowPayload {
+  /**
+   * The join request, as vtc/join-requests/list returns it.
+   */
+  id: string;
+  ext?: Ext;
+}
+export interface VTCJoinRequestsVettingShowResponsePayload {
+  /**
+   * Echoed.
+   */
+  requestId: string;
+  vetting?: VettingFacts;
+  ext?: Ext;
+}
+/**
+ * What the community established about a request's vetting evidence when it decided — the join policy's vetting input, in lowerCamelCase.
+ */
+export interface VettingFacts {
+  /**
+   * The Accepts criterion whose requirements were applied.
+   */
+  criterionId: string;
+  requirementsDigest: DigestMultibase;
+  /**
+   * The applicant named the same `requirementsDigest` — they applied under the version of the requirements that was applied.
+   */
+  applicantDigestMatches: boolean;
+  /**
+   * @maxItems 64
+   */
+  statements: VettingStatementFacts[];
+  /**
+   * Distinct eligible vetters counted, each once however many DIDs they hold.
+   */
+  distinctCountedVetters: number;
+  /**
+   * Counted statements by method.
+   */
+  byMethod: {
+    [k: string]: number | undefined;
+  };
+  /**
+   * Every counted statement carries the same identity commitment.
+   */
+  commitmentsConsistent: boolean;
+  /**
+   * No declared-relationship cap was exceeded.
+   */
+  independenceOk: boolean;
+  /**
+   * The requirements demanded an invitation.
+   */
+  invitationRequired: boolean;
+  /**
+   * Count, method floors, consistency and independence all held.
+   */
+  satisfied: boolean;
+  /**
+   * What was still missing, in the `vetting:*` grammar. Empty when `satisfied`.
+   *
+   * @maxItems 16
+   */
+  needs:
+    | []
+    | [string]
+    | [string, string]
+    | [string, string, string]
+    | [string, string, string, string]
+    | [string, string, string, string, string]
+    | [string, string, string, string, string, string]
+    | [string, string, string, string, string, string, string]
+    | [string, string, string, string, string, string, string, string]
+    | [string, string, string, string, string, string, string, string, string]
+    | [string, string, string, string, string, string, string, string, string, string]
+    | [string, string, string, string, string, string, string, string, string, string, string]
+    | [string, string, string, string, string, string, string, string, string, string, string, string]
+    | [string, string, string, string, string, string, string, string, string, string, string, string, string]
+    | [string, string, string, string, string, string, string, string, string, string, string, string, string, string]
+    | [
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string
+      ]
+    | [
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string
+      ];
+  /**
+   * When the facts were recorded.
+   */
+  recordedAt: string;
+}
+/**
+ * One identity-vetting statement the applicant's presentation carried, as the community saw it at the decision — plus whether its vetter has withdrawn it since.
+ */
+export interface VettingStatementFacts {
+  /**
+   * The statement's `id`, when it had one.
+   */
+  id?: string;
+  /**
+   * The vetter who issued it, when it could be read.
+   */
+  issuer?: string;
+  /**
+   * Its proof, type, validity window and body verified.
+   */
+  verified: boolean;
+  /**
+   * Its issuer was an eligible vetter at the decision.
+   */
+  eligible: boolean;
+  /**
+   * Withdrawn by its vetter before the decision.
+   */
+  revoked: boolean;
+  /**
+   * Withdrawn by its vetter now — after the decision, when `revoked` is false. Read live, not recorded.
+   */
+  withdrawnNow: boolean;
+  method?: VettingMethod;
+  declaredRelationship?: VettingRelationship;
+  /**
+   * It counted toward the requirements.
+   */
+  counted: boolean;
+  /**
+   * Why it did not count, as machine codes in the `vetting:*` grammar the join policy reads. Empty when it counted.
+   *
+   * @maxItems 16
+   */
+  failures:
+    | []
+    | [string]
+    | [string, string]
+    | [string, string, string]
+    | [string, string, string, string]
+    | [string, string, string, string, string]
+    | [string, string, string, string, string, string]
+    | [string, string, string, string, string, string, string]
+    | [string, string, string, string, string, string, string, string]
+    | [string, string, string, string, string, string, string, string, string]
+    | [string, string, string, string, string, string, string, string, string, string]
+    | [string, string, string, string, string, string, string, string, string, string, string]
+    | [string, string, string, string, string, string, string, string, string, string, string, string]
+    | [string, string, string, string, string, string, string, string, string, string, string, string, string]
+    | [string, string, string, string, string, string, string, string, string, string, string, string, string, string]
+    | [
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string
+      ]
+    | [
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string,
+        string
+      ];
+}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { DigestMultibase, Ext, VettingMethod, VettingRelationship };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/vtc/join-requests/vetting/show/0.1" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = VTCJoinRequestsVettingShowPayload;
+
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/vtc/join-requests/vetting/show/0.1#response" as const;
+
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = VTCJoinRequestsVettingShowResponsePayload;
+
+/**
+ * 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/vetting/show/0.1",
+  "title": "VTC Join Requests — Vetting — Show — payload",
+  "description": "An administrator reads the vetting facts one join request was decided on. The outer document members are owned by the framework — SPEC §6.3.",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "id"
+  ],
+  "properties": {
+    "id": {
+      "type": "string",
+      "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
+      "description": "The join request, as vtc/join-requests/list returns it."
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext"
+    }
+  },
+  "$defs": {
+    "VettingStatementFacts": {
+      "title": "VettingStatementFacts",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "verified",
+        "eligible",
+        "revoked",
+        "withdrawnNow",
+        "counted",
+        "failures"
+      ],
+      "description": "One identity-vetting statement the applicant's presentation carried, as the community saw it at the decision — plus whether its vetter has withdrawn it since.",
+      "properties": {
+        "id": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 2048,
+          "description": "The statement's `id`, when it had one."
+        },
+        "issuer": {
+          "type": "string",
+          "pattern": "^did:",
+          "maxLength": 2048,
+          "description": "The vetter who issued it, when it could be read."
+        },
+        "verified": {
+          "type": "boolean",
+          "description": "Its proof, type, validity window and body verified."
+        },
+        "eligible": {
+          "type": "boolean",
+          "description": "Its issuer was an eligible vetter at the decision."
+        },
+        "revoked": {
+          "type": "boolean",
+          "description": "Withdrawn by its vetter before the decision."
+        },
+        "withdrawnNow": {
+          "type": "boolean",
+          "description": "Withdrawn by its vetter now — after the decision, when `revoked` is false. Read live, not recorded."
+        },
+        "method": {
+          "$ref": "#/$defs/VettingMethod"
+        },
+        "declaredRelationship": {
+          "$ref": "#/$defs/VettingRelationship"
+        },
+        "counted": {
+          "type": "boolean",
+          "description": "It counted toward the requirements."
+        },
+        "failures": {
+          "type": "array",
+          "maxItems": 16,
+          "items": {
+            "type": "string",
+            "minLength": 1,
+            "maxLength": 128
+          },
+          "description": "Why it did not count, as machine codes in the `vetting:*` grammar the join policy reads. Empty when it counted."
+        }
+      }
+    },
+    "VettingFacts": {
+      "title": "VettingFacts",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "criterionId",
+        "requirementsDigest",
+        "applicantDigestMatches",
+        "statements",
+        "distinctCountedVetters",
+        "byMethod",
+        "commitmentsConsistent",
+        "independenceOk",
+        "invitationRequired",
+        "satisfied",
+        "needs",
+        "recordedAt"
+      ],
+      "description": "What the community established about a request's vetting evidence when it decided — the join policy's vetting input, in lowerCamelCase.",
+      "properties": {
+        "criterionId": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 128,
+          "description": "The Accepts criterion whose requirements were applied."
+        },
+        "requirementsDigest": {
+          "$ref": "#/$defs/DigestMultibase"
+        },
+        "applicantDigestMatches": {
+          "type": "boolean",
+          "description": "The applicant named the same `requirementsDigest` — they applied under the version of the requirements that was applied."
+        },
+        "statements": {
+          "type": "array",
+          "maxItems": 64,
+          "items": {
+            "$ref": "#/$defs/VettingStatementFacts"
+          }
+        },
+        "distinctCountedVetters": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "Distinct eligible vetters counted, each once however many DIDs they hold."
+        },
+        "byMethod": {
+          "type": "object",
+          "propertyNames": {
+            "$ref": "#/$defs/VettingMethod"
+          },
+          "additionalProperties": {
+            "type": "integer",
+            "minimum": 0
+          },
+          "description": "Counted statements by method."
+        },
+        "commitmentsConsistent": {
+          "type": "boolean",
+          "description": "Every counted statement carries the same identity commitment."
+        },
+        "independenceOk": {
+          "type": "boolean",
+          "description": "No declared-relationship cap was exceeded."
+        },
+        "invitationRequired": {
+          "type": "boolean",
+          "description": "The requirements demanded an invitation."
+        },
+        "satisfied": {
+          "type": "boolean",
+          "description": "Count, method floors, consistency and independence all held."
+        },
+        "needs": {
+          "type": "array",
+          "maxItems": 16,
+          "items": {
+            "type": "string",
+            "minLength": 1,
+            "maxLength": 128
+          },
+          "description": "What was still missing, in the `vetting:*` grammar. Empty when `satisfied`."
+        },
+        "recordedAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When the facts were recorded."
+        }
+      }
+    },
+    "Response": {
+      "$anchor": "response",
+      "title": "VTC Join Requests — Vetting — Show — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "requestId"
+      ],
+      "properties": {
+        "requestId": {
+          "type": "string",
+          "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
+          "description": "Echoed."
+        },
+        "vetting": {
+          "$ref": "#/$defs/VettingFacts"
+        },
+        "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-]+)+$"
+      }
+    },
+    "VettingMethod": {
+      "title": "VettingMethod",
+      "type": "string",
+      "enum": [
+        "inPerson",
+        "video",
+        "priorAcquaintance"
+      ],
+      "description": "How the vetter established that the person they checked is the person controlling the applicant's DID. `inPerson` — both people were physically together. `video` — a live, two-way video call. `priorAcquaintance` — the vetter has known or worked with this person over a period, and attests from that knowledge rather than from a document. A method is a description of what happened, not an assurance level: which methods count, and how many of each, is community policy."
+    },
+    "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"
+      ]
+    },
+    "VettingRelationship": {
+      "title": "VettingRelationship",
+      "type": "string",
+      "enum": [
+        "none",
+        "communityColleague",
+        "sameEmployer",
+        "family",
+        "otherPersonal"
+      ],
+      "description": "The vetter's own declaration of how they relate to the applicant. Declared, not verified: it exists so community policy can cap how much evidence comes from people close to the applicant, and a false declaration is the vetter's attributable act."
+    }
+  }
+} 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": {
+    "VettingStatementFacts": {
+      "title": "VettingStatementFacts",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "verified",
+        "eligible",
+        "revoked",
+        "withdrawnNow",
+        "counted",
+        "failures"
+      ],
+      "description": "One identity-vetting statement the applicant's presentation carried, as the community saw it at the decision — plus whether its vetter has withdrawn it since.",
+      "properties": {
+        "id": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 2048,
+          "description": "The statement's `id`, when it had one."
+        },
+        "issuer": {
+          "type": "string",
+          "pattern": "^did:",
+          "maxLength": 2048,
+          "description": "The vetter who issued it, when it could be read."
+        },
+        "verified": {
+          "type": "boolean",
+          "description": "Its proof, type, validity window and body verified."
+        },
+        "eligible": {
+          "type": "boolean",
+          "description": "Its issuer was an eligible vetter at the decision."
+        },
+        "revoked": {
+          "type": "boolean",
+          "description": "Withdrawn by its vetter before the decision."
+        },
+        "withdrawnNow": {
+          "type": "boolean",
+          "description": "Withdrawn by its vetter now — after the decision, when `revoked` is false. Read live, not recorded."
+        },
+        "method": {
+          "$ref": "#/$defs/VettingMethod"
+        },
+        "declaredRelationship": {
+          "$ref": "#/$defs/VettingRelationship"
+        },
+        "counted": {
+          "type": "boolean",
+          "description": "It counted toward the requirements."
+        },
+        "failures": {
+          "type": "array",
+          "maxItems": 16,
+          "items": {
+            "type": "string",
+            "minLength": 1,
+            "maxLength": 128
+          },
+          "description": "Why it did not count, as machine codes in the `vetting:*` grammar the join policy reads. Empty when it counted."
+        }
+      }
+    },
+    "VettingFacts": {
+      "title": "VettingFacts",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "criterionId",
+        "requirementsDigest",
+        "applicantDigestMatches",
+        "statements",
+        "distinctCountedVetters",
+        "byMethod",
+        "commitmentsConsistent",
+        "independenceOk",
+        "invitationRequired",
+        "satisfied",
+        "needs",
+        "recordedAt"
+      ],
+      "description": "What the community established about a request's vetting evidence when it decided — the join policy's vetting input, in lowerCamelCase.",
+      "properties": {
+        "criterionId": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 128,
+          "description": "The Accepts criterion whose requirements were applied."
+        },
+        "requirementsDigest": {
+          "$ref": "#/$defs/DigestMultibase"
+        },
+        "applicantDigestMatches": {
+          "type": "boolean",
+          "description": "The applicant named the same `requirementsDigest` — they applied under the version of the requirements that was applied."
+        },
+        "statements": {
+          "type": "array",
+          "maxItems": 64,
+          "items": {
+            "$ref": "#/$defs/VettingStatementFacts"
+          }
+        },
+        "distinctCountedVetters": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "Distinct eligible vetters counted, each once however many DIDs they hold."
+        },
+        "byMethod": {
+          "type": "object",
+          "propertyNames": {
+            "$ref": "#/$defs/VettingMethod"
+          },
+          "additionalProperties": {
+            "type": "integer",
+            "minimum": 0
+          },
+          "description": "Counted statements by method."
+        },
+        "commitmentsConsistent": {
+          "type": "boolean",
+          "description": "Every counted statement carries the same identity commitment."
+        },
+        "independenceOk": {
+          "type": "boolean",
+          "description": "No declared-relationship cap was exceeded."
+        },
+        "invitationRequired": {
+          "type": "boolean",
+          "description": "The requirements demanded an invitation."
+        },
+        "satisfied": {
+          "type": "boolean",
+          "description": "Count, method floors, consistency and independence all held."
+        },
+        "needs": {
+          "type": "array",
+          "maxItems": 16,
+          "items": {
+            "type": "string",
+            "minLength": 1,
+            "maxLength": 128
+          },
+          "description": "What was still missing, in the `vetting:*` grammar. Empty when `satisfied`."
+        },
+        "recordedAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When the facts were recorded."
+        }
+      }
+    },
+    "Response": {
+      "$anchor": "response",
+      "title": "VTC Join Requests — Vetting — Show — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "requestId"
+      ],
+      "properties": {
+        "requestId": {
+          "type": "string",
+          "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
+          "description": "Echoed."
+        },
+        "vetting": {
+          "$ref": "#/$defs/VettingFacts"
+        },
+        "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-]+)+$"
+      }
+    },
+    "VettingMethod": {
+      "title": "VettingMethod",
+      "type": "string",
+      "enum": [
+        "inPerson",
+        "video",
+        "priorAcquaintance"
+      ],
+      "description": "How the vetter established that the person they checked is the person controlling the applicant's DID. `inPerson` — both people were physically together. `video` — a live, two-way video call. `priorAcquaintance` — the vetter has known or worked with this person over a period, and attests from that knowledge rather than from a document. A method is a description of what happened, not an assurance level: which methods count, and how many of each, is community policy."
+    },
+    "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"
+      ]
+    },
+    "VettingRelationship": {
+      "title": "VettingRelationship",
+      "type": "string",
+      "enum": [
+        "none",
+        "communityColleague",
+        "sameEmployer",
+        "family",
+        "otherPersonal"
+      ],
+      "description": "The vetter's own declaration of how they relate to the applicant. Declared, not verified: it exists so community policy can cap how much evidence comes from people close to the applicant, and a false declaration is the vetter's attributable act."
+    }
+  }
+} 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: false,
+  isRecipientRequired: true,
+  isIssuedAtRequired: false,
+  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: false,
+  payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
+} as const;