@openvtc/trust-tasks 0.19.3 → 0.19.4

package/src/vetting/request/0.1/payload.ts

@@ -0,0 +1,799 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vetting/request/0.1/payload.schema.json
+ */
+
+import type { DigestMultibase, Ext, VettingDocumentation, VettingMethod } from "../../../_shared/components.js";
+
+
+/**
+ * A ticket the vetter issued: the short code a person reads or types, or the full-entropy QR form.
+ */
+export type Ticket = ShortCodeTicket | QrTicket;
+
+/**
+ * An applicant asks one vetter to vet them for one community. The applicant is the document's issuer, and `joinDid` repeats that DID: it is the DID the applicant is applying with, and every card and statement that follows names it. Carries a ticket the vetter issued or an introduction, never both. The vetter's response accepts the request and proves the vetter is currently eligible to vet for that community.
+ */
+export interface VettingRequestPayload {
+  /**
+   * The community the applicant is applying to and asks to be vetted for.
+   */
+  community: string;
+  /**
+   * The `requirementsDigest` of the community's manifest criterion the applicant is gathering for, recorded when the application started. RECOMMENDED; a community that publishes no digest leaves the applicant nothing to cite.
+   */
+  requirementsDigest?: DigestMultibase;
+  /**
+   * The DID the applicant will join the community with. MUST equal the document's `issuer`. Every card and statement this request leads to names it, and it is the holder of the presentation the applicant eventually submits.
+   */
+  joinDid: string;
+  ticket?: Ticket;
+  /**
+   * A verifiable invitation credential for `community` whose subject is the applicant's DID, issued by the community or a member (opaque here). An alternative to a ticket for vetters who accept introductions.
+   */
+  introduction?: {};
+  /**
+   * The method the applicant would prefer. A preference: the vetter chooses the session's method.
+   */
+  preferredMethod?: VettingMethod;
+  /**
+   * BCP 47 language tags the applicant can hold a session in, most preferred first.
+   *
+   * @maxItems 16
+   */
+  languages?:
+    | []
+    | [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
+      ];
+  /**
+   * OPTIONAL applicant-authored text for the vetter — typically how they know each other. Untrusted: read by the vetter, attributed to the applicant on every surface that renders it, never shown to the community.
+   */
+  message?: string;
+  /**
+   * OPTIONAL applicant-authored free text on when they can meet. Scheduling is out of band; this is a hint, attributed to the applicant.
+   */
+  availability?: string;
+  ext?: Ext;
+}
+export interface ShortCodeTicket {
+  /**
+   * Eight Crockford base32 characters, grouped four and four (40 bits). A secret the vetter handed over; not derived from anything.
+   */
+  code: string;
+}
+export interface QrTicket {
+  ticketId: string;
+  /**
+   * 32 random bytes, base64url without padding.
+   */
+  secret: string;
+}
+/**
+ * The vetter accepts the request. A refusal is a trust-task-error, never a response document.
+ */
+export interface VettingRequestResponsePayload {
+  /**
+   * The vetter's handle for this accepted request, carried by the session and any decline.
+   */
+  requestId: string;
+  eligibilityVp?: EligibilityPresentation;
+  /**
+   * RECOMMENDED. What this vetter will rely on, so the applicant brings it — the vetter's own choice. `none` means the vetter attests from prior acquaintance.
+   *
+   * @minItems 1
+   */
+  acceptsDocumentation?: [VettingDocumentation, ...VettingDocumentation[]];
+  /**
+   * OPTIONAL vetter-authored free text on how and when the session will happen. Attributed to the vetter.
+   */
+  sessionHint?: string;
+  ext?: Ext;
+}
+/**
+ * OPTIONAL. A W3C Verifiable Presentation by which the vetter shows the applicant that it currently holds the community's vetter role. Bound to this request by `nonce` (the vetting/request document's `id`, which the applicant chose) and to this applicant by `domain` (its `joinDid`), so it cannot be replayed to another request or another applicant. The applicant's check is advisory; the community evaluates eligibility again, authoritatively, when it decides. Members other than those defined here are permitted, as the VC data model allows.
+ */
+export interface EligibilityPresentation {
+  /**
+   * JSON-LD contexts. The first item MUST be `https://www.w3.org/ns/credentials/v2` (stated here rather than as `prefixItems`, which the Rust generator cannot express).
+   *
+   * @minItems 1
+   */
+  "@context": [string, ...string[]];
+  /**
+   * MUST include `VerifiablePresentation` (stated here rather than as `contains`, which the Rust generator cannot express).
+   *
+   * @minItems 1
+   */
+  type: [string, ...string[]];
+  /**
+   * The vetter's DID — the response's `issuer`.
+   */
+  holder: string;
+  /**
+   * Credentials presented (opaque here). MUST include the community-issued `CommunityRole` endorsement credential naming `holder`, whose `endorsement.role` is the manifest's `eligibleVetters.role` — see vtc/vetting/vetters/grant/0.1. MAY include others, such as the membership credential.
+   *
+   * @minItems 1
+   */
+  verifiableCredential: [{}, ...{}[]];
+  /**
+   * The `id` of the vetting/request document this responds to.
+   */
+  nonce: string;
+  /**
+   * The applicant's `joinDid` from that request.
+   */
+  domain: string;
+  proof: EligibilityPresentationProof;
+  [k: string]: unknown | undefined;
+}
+/**
+ * A W3C Data Integrity proof by `holder` over the presentation, `nonce` and `domain` included.
+ */
+export interface EligibilityPresentationProof {
+  type: "DataIntegrityProof";
+  /**
+   * e.g. `eddsa-jcs-2022`.
+   */
+  cryptosuite: string;
+  /**
+   * A verification method of `holder`, authorized for `authentication`.
+   */
+  verificationMethod: string;
+  proofPurpose: "authentication";
+  created?: string;
+  proofValue: string;
+  [k: string]: unknown | undefined;
+}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { DigestMultibase, Ext, VettingDocumentation, VettingMethod };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/vetting/request/0.1" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = VettingRequestPayload;
+
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/vetting/request/0.1#response" as const;
+
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = VettingRequestResponsePayload;
+
+/**
+ * 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/vetting/request/0.1",
+  "title": "Vetting Request — payload",
+  "description": "An applicant asks one vetter to vet them for one community. The applicant is the document's issuer, and `joinDid` repeats that DID: it is the DID the applicant is applying with, and every card and statement that follows names it. Carries a ticket the vetter issued or an introduction, never both. The vetter's response accepts the request and proves the vetter is currently eligible to vet for that community.",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "community",
+    "joinDid"
+  ],
+  "dependentSchemas": {
+    "ticket": {
+      "not": {
+        "required": [
+          "introduction"
+        ]
+      }
+    }
+  },
+  "properties": {
+    "community": {
+      "type": "string",
+      "pattern": "^did:",
+      "description": "The community the applicant is applying to and asks to be vetted for."
+    },
+    "requirementsDigest": {
+      "$ref": "#/$defs/DigestMultibase",
+      "description": "The `requirementsDigest` of the community's manifest criterion the applicant is gathering for, recorded when the application started. RECOMMENDED; a community that publishes no digest leaves the applicant nothing to cite."
+    },
+    "joinDid": {
+      "type": "string",
+      "pattern": "^did:",
+      "description": "The DID the applicant will join the community with. MUST equal the document's `issuer`. Every card and statement this request leads to names it, and it is the holder of the presentation the applicant eventually submits."
+    },
+    "ticket": {
+      "$ref": "#/$defs/Ticket"
+    },
+    "introduction": {
+      "type": "object",
+      "description": "A verifiable invitation credential for `community` whose subject is the applicant's DID, issued by the community or a member (opaque here). An alternative to a ticket for vetters who accept introductions."
+    },
+    "preferredMethod": {
+      "$ref": "#/$defs/VettingMethod",
+      "description": "The method the applicant would prefer. A preference: the vetter chooses the session's method."
+    },
+    "languages": {
+      "type": "array",
+      "maxItems": 16,
+      "uniqueItems": true,
+      "items": {
+        "type": "string",
+        "maxLength": 35,
+        "pattern": "^[A-Za-z]{2,3}(-[A-Za-z0-9]{1,8})*$"
+      },
+      "description": "BCP 47 language tags the applicant can hold a session in, most preferred first."
+    },
+    "message": {
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 1000,
+      "description": "OPTIONAL applicant-authored text for the vetter — typically how they know each other. Untrusted: read by the vetter, attributed to the applicant on every surface that renders it, never shown to the community."
+    },
+    "availability": {
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 256,
+      "description": "OPTIONAL applicant-authored free text on when they can meet. Scheduling is out of band; this is a hint, attributed to the applicant."
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext"
+    }
+  },
+  "$defs": {
+    "Ticket": {
+      "title": "Ticket",
+      "description": "A ticket the vetter issued: the short code a person reads or types, or the full-entropy QR form.",
+      "oneOf": [
+        {
+          "$ref": "#/$defs/ShortCodeTicket"
+        },
+        {
+          "$ref": "#/$defs/QrTicket"
+        }
+      ]
+    },
+    "ShortCodeTicket": {
+      "title": "ShortCodeTicket",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "code"
+      ],
+      "properties": {
+        "code": {
+          "type": "string",
+          "pattern": "^[0-9A-HJKMNP-TV-Z]{4}-[0-9A-HJKMNP-TV-Z]{4}$",
+          "description": "Eight Crockford base32 characters, grouped four and four (40 bits). A secret the vetter handed over; not derived from anything."
+        }
+      }
+    },
+    "QrTicket": {
+      "title": "QrTicket",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "ticketId",
+        "secret"
+      ],
+      "properties": {
+        "ticketId": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 128,
+          "pattern": "^[A-Za-z0-9._:-]+$"
+        },
+        "secret": {
+          "type": "string",
+          "pattern": "^[A-Za-z0-9_-]{43}$",
+          "description": "32 random bytes, base64url without padding."
+        }
+      }
+    },
+    "EligibilityPresentation": {
+      "title": "EligibilityPresentation",
+      "description": "OPTIONAL. A W3C Verifiable Presentation by which the vetter shows the applicant that it currently holds the community's vetter role. Bound to this request by `nonce` (the vetting/request document's `id`, which the applicant chose) and to this applicant by `domain` (its `joinDid`), so it cannot be replayed to another request or another applicant. The applicant's check is advisory; the community evaluates eligibility again, authoritatively, when it decides. Members other than those defined here are permitted, as the VC data model allows.",
+      "type": "object",
+      "additionalProperties": true,
+      "required": [
+        "@context",
+        "type",
+        "holder",
+        "verifiableCredential",
+        "nonce",
+        "domain",
+        "proof"
+      ],
+      "properties": {
+        "@context": {
+          "type": "array",
+          "minItems": 1,
+          "items": {
+            "type": "string",
+            "minLength": 1,
+            "maxLength": 2048
+          },
+          "description": "JSON-LD contexts. The first item MUST be `https://www.w3.org/ns/credentials/v2` (stated here rather than as `prefixItems`, which the Rust generator cannot express)."
+        },
+        "type": {
+          "type": "array",
+          "minItems": 1,
+          "uniqueItems": true,
+          "items": {
+            "type": "string",
+            "minLength": 1,
+            "maxLength": 128
+          },
+          "description": "MUST include `VerifiablePresentation` (stated here rather than as `contains`, which the Rust generator cannot express)."
+        },
+        "holder": {
+          "type": "string",
+          "pattern": "^did:",
+          "description": "The vetter's DID — the response's `issuer`."
+        },
+        "verifiableCredential": {
+          "type": "array",
+          "minItems": 1,
+          "items": {
+            "type": "object"
+          },
+          "description": "Credentials presented (opaque here). MUST include the community-issued `CommunityRole` endorsement credential naming `holder`, whose `endorsement.role` is the manifest's `eligibleVetters.role` — see vtc/vetting/vetters/grant/0.1. MAY include others, such as the membership credential."
+        },
+        "nonce": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 512,
+          "description": "The `id` of the vetting/request document this responds to."
+        },
+        "domain": {
+          "type": "string",
+          "pattern": "^did:",
+          "description": "The applicant's `joinDid` from that request."
+        },
+        "proof": {
+          "$ref": "#/$defs/EligibilityPresentationProof"
+        }
+      }
+    },
+    "EligibilityPresentationProof": {
+      "title": "EligibilityPresentationProof",
+      "description": "A W3C Data Integrity proof by `holder` over the presentation, `nonce` and `domain` included.",
+      "type": "object",
+      "additionalProperties": true,
+      "required": [
+        "type",
+        "cryptosuite",
+        "verificationMethod",
+        "proofPurpose",
+        "proofValue"
+      ],
+      "properties": {
+        "type": {
+          "type": "string",
+          "const": "DataIntegrityProof"
+        },
+        "cryptosuite": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 64,
+          "pattern": "^[a-z0-9-]+$",
+          "description": "e.g. `eddsa-jcs-2022`."
+        },
+        "verificationMethod": {
+          "type": "string",
+          "pattern": "^did:",
+          "description": "A verification method of `holder`, authorized for `authentication`."
+        },
+        "proofPurpose": {
+          "type": "string",
+          "const": "authentication"
+        },
+        "created": {
+          "type": "string",
+          "format": "date-time"
+        },
+        "proofValue": {
+          "type": "string",
+          "pattern": "^z[1-9A-HJ-NP-Za-km-z]+$"
+        }
+      }
+    },
+    "Response": {
+      "$anchor": "response",
+      "title": "Vetting Request — response payload",
+      "description": "The vetter accepts the request. A refusal is a trust-task-error, never a response document.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "requestId"
+      ],
+      "properties": {
+        "requestId": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 128,
+          "description": "The vetter's handle for this accepted request, carried by the session and any decline."
+        },
+        "eligibilityVp": {
+          "$ref": "#/$defs/EligibilityPresentation"
+        },
+        "acceptsDocumentation": {
+          "type": "array",
+          "minItems": 1,
+          "uniqueItems": true,
+          "items": {
+            "$ref": "#/$defs/VettingDocumentation"
+          },
+          "description": "RECOMMENDED. What this vetter will rely on, so the applicant brings it — the vetter's own choice. `none` means the vetter attests from prior acquaintance."
+        },
+        "sessionHint": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 500,
+          "description": "OPTIONAL vetter-authored free text on how and when the session will happen. Attributed to the vetter."
+        },
+        "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-]+)+$"
+      }
+    },
+    "VettingDocumentation": {
+      "title": "VettingDocumentation",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 64,
+      "pattern": "^[a-z][a-zA-Z0-9]*$",
+      "description": "A class of documentation, named in lowerCamelCase. Open rather than enumerated, because what documentation a vetter accepts is each vetter's own choice. Well-known values: `passport`, `nationalId`, `driverLicence`, and `none` — the vetter will attest without a document, which is the `priorAcquaintance` case. Only the class ever travels — never a document number, an image, an issuing authority or an expiry date. `none` states a policy (what a vetter accepts); a record of what was relied on expresses 'no document' as an empty list instead."
+    },
+    "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"
+      ]
+    }
+  }
+} 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": {
+    "Ticket": {
+      "title": "Ticket",
+      "description": "A ticket the vetter issued: the short code a person reads or types, or the full-entropy QR form.",
+      "oneOf": [
+        {
+          "$ref": "#/$defs/ShortCodeTicket"
+        },
+        {
+          "$ref": "#/$defs/QrTicket"
+        }
+      ]
+    },
+    "ShortCodeTicket": {
+      "title": "ShortCodeTicket",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "code"
+      ],
+      "properties": {
+        "code": {
+          "type": "string",
+          "pattern": "^[0-9A-HJKMNP-TV-Z]{4}-[0-9A-HJKMNP-TV-Z]{4}$",
+          "description": "Eight Crockford base32 characters, grouped four and four (40 bits). A secret the vetter handed over; not derived from anything."
+        }
+      }
+    },
+    "QrTicket": {
+      "title": "QrTicket",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "ticketId",
+        "secret"
+      ],
+      "properties": {
+        "ticketId": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 128,
+          "pattern": "^[A-Za-z0-9._:-]+$"
+        },
+        "secret": {
+          "type": "string",
+          "pattern": "^[A-Za-z0-9_-]{43}$",
+          "description": "32 random bytes, base64url without padding."
+        }
+      }
+    },
+    "EligibilityPresentation": {
+      "title": "EligibilityPresentation",
+      "description": "OPTIONAL. A W3C Verifiable Presentation by which the vetter shows the applicant that it currently holds the community's vetter role. Bound to this request by `nonce` (the vetting/request document's `id`, which the applicant chose) and to this applicant by `domain` (its `joinDid`), so it cannot be replayed to another request or another applicant. The applicant's check is advisory; the community evaluates eligibility again, authoritatively, when it decides. Members other than those defined here are permitted, as the VC data model allows.",
+      "type": "object",
+      "additionalProperties": true,
+      "required": [
+        "@context",
+        "type",
+        "holder",
+        "verifiableCredential",
+        "nonce",
+        "domain",
+        "proof"
+      ],
+      "properties": {
+        "@context": {
+          "type": "array",
+          "minItems": 1,
+          "items": {
+            "type": "string",
+            "minLength": 1,
+            "maxLength": 2048
+          },
+          "description": "JSON-LD contexts. The first item MUST be `https://www.w3.org/ns/credentials/v2` (stated here rather than as `prefixItems`, which the Rust generator cannot express)."
+        },
+        "type": {
+          "type": "array",
+          "minItems": 1,
+          "uniqueItems": true,
+          "items": {
+            "type": "string",
+            "minLength": 1,
+            "maxLength": 128
+          },
+          "description": "MUST include `VerifiablePresentation` (stated here rather than as `contains`, which the Rust generator cannot express)."
+        },
+        "holder": {
+          "type": "string",
+          "pattern": "^did:",
+          "description": "The vetter's DID — the response's `issuer`."
+        },
+        "verifiableCredential": {
+          "type": "array",
+          "minItems": 1,
+          "items": {
+            "type": "object"
+          },
+          "description": "Credentials presented (opaque here). MUST include the community-issued `CommunityRole` endorsement credential naming `holder`, whose `endorsement.role` is the manifest's `eligibleVetters.role` — see vtc/vetting/vetters/grant/0.1. MAY include others, such as the membership credential."
+        },
+        "nonce": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 512,
+          "description": "The `id` of the vetting/request document this responds to."
+        },
+        "domain": {
+          "type": "string",
+          "pattern": "^did:",
+          "description": "The applicant's `joinDid` from that request."
+        },
+        "proof": {
+          "$ref": "#/$defs/EligibilityPresentationProof"
+        }
+      }
+    },
+    "EligibilityPresentationProof": {
+      "title": "EligibilityPresentationProof",
+      "description": "A W3C Data Integrity proof by `holder` over the presentation, `nonce` and `domain` included.",
+      "type": "object",
+      "additionalProperties": true,
+      "required": [
+        "type",
+        "cryptosuite",
+        "verificationMethod",
+        "proofPurpose",
+        "proofValue"
+      ],
+      "properties": {
+        "type": {
+          "type": "string",
+          "const": "DataIntegrityProof"
+        },
+        "cryptosuite": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 64,
+          "pattern": "^[a-z0-9-]+$",
+          "description": "e.g. `eddsa-jcs-2022`."
+        },
+        "verificationMethod": {
+          "type": "string",
+          "pattern": "^did:",
+          "description": "A verification method of `holder`, authorized for `authentication`."
+        },
+        "proofPurpose": {
+          "type": "string",
+          "const": "authentication"
+        },
+        "created": {
+          "type": "string",
+          "format": "date-time"
+        },
+        "proofValue": {
+          "type": "string",
+          "pattern": "^z[1-9A-HJ-NP-Za-km-z]+$"
+        }
+      }
+    },
+    "Response": {
+      "$anchor": "response",
+      "title": "Vetting Request — response payload",
+      "description": "The vetter accepts the request. A refusal is a trust-task-error, never a response document.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "requestId"
+      ],
+      "properties": {
+        "requestId": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 128,
+          "description": "The vetter's handle for this accepted request, carried by the session and any decline."
+        },
+        "eligibilityVp": {
+          "$ref": "#/$defs/EligibilityPresentation"
+        },
+        "acceptsDocumentation": {
+          "type": "array",
+          "minItems": 1,
+          "uniqueItems": true,
+          "items": {
+            "$ref": "#/$defs/VettingDocumentation"
+          },
+          "description": "RECOMMENDED. What this vetter will rely on, so the applicant brings it — the vetter's own choice. `none` means the vetter attests from prior acquaintance."
+        },
+        "sessionHint": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 500,
+          "description": "OPTIONAL vetter-authored free text on how and when the session will happen. Attributed to the vetter."
+        },
+        "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-]+)+$"
+      }
+    },
+    "VettingDocumentation": {
+      "title": "VettingDocumentation",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 64,
+      "pattern": "^[a-z][a-zA-Z0-9]*$",
+      "description": "A class of documentation, named in lowerCamelCase. Open rather than enumerated, because what documentation a vetter accepts is each vetter's own choice. Well-known values: `passport`, `nationalId`, `driverLicence`, and `none` — the vetter will attest without a document, which is the `priorAcquaintance` case. Only the class ever travels — never a document number, an image, an issuing authority or an expiry date. `none` states a policy (what a vetter accepts); a record of what was relied on expresses 'no document' as an empty list instead."
+    },
+    "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"
+      ]
+    }
+  }
+} 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;