@openvtc/trust-tasks 0.19.3 → 0.19.5

package/src/vtc/join-requests/manifest/0.2/payload.ts

@@ -0,0 +1,815 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vtc/join-requests/manifest/0.2/payload.schema.json
+ */
+
+import type { ClaimType, DigestMultibase, Ext, VettingDocumentation, VettingMethod } from "../../../../_shared/components.js";
+
+
+/**
+ * An ISO 8601 duration in weeks, days, hours, minutes and seconds only (e.g. `P120D`, `P2W`, `P1DT12H`, `PT15M`). Years and months are refused: their length depends on the calendar, and an age limit that means different things on different days is not a limit.
+ */
+export type Duration = string;
+
+/**
+ * Discover a community's join criteria before applying. The request carries nothing. Version 0.2 adds, per criterion, an optional `vetting` requirements object — how many identity-vetting statements a community needs, by which methods, from whom — and a `requirementsDigest` that names the exact version of the criterion an applicant started under. The response may also carry `branding`, how the community asks to be shown.
+ */
+export interface VTCJoinRequestsManifestPayload {
+  ext?: Ext;
+}
+export interface VTCJoinRequestsManifestResponsePayload {
+  communityDid: string;
+  criteria: Criterion[];
+  branding?: CommunityBranding;
+  ext?: Ext;
+}
+export interface Criterion {
+  id: string;
+  /**
+   * Plain-language summary of the criterion, authored by the community and shown to prospective applicants. Informative: where it and `vetting` disagree, `vetting` governs.
+   */
+  description?: string;
+  /**
+   * The presentation-definition an applicant must satisfy for this criterion (opaque here).
+   */
+  presentationDefinition: {};
+  vetting?: VettingRequirements;
+  /**
+   * Digest over the RFC 8785 (JCS) canonicalization of this criterion object with the `requirementsDigest` member removed, as a multibase-encoded multihash (SHA-256 and base58btc RECOMMENDED). Names one version of the criterion: an applicant records it when starting an application and echoes it to vetters and at submission. REQUIRED when `vetting` is present.
+   */
+  requirementsDigest?: DigestMultibase;
+}
+/**
+ * What identity-vetting evidence a criterion needs, beyond what a presentation-definition can express: distinct eligible vetters, per-method floors, independence caps. Every number is the community's own policy. This schema supplies no defaults — an absent optional member means the community imposes no constraint of that kind, never that some protocol value applies. Deliberately open: a consumer MUST ignore members it does not recognise, so a community publishing a newer shape does not make an older client unable to read the rest. Durations: `maxStatementAge` — a statement older than this at decision time does not count (absent: no limit beyond the statement's own validity); `decisionSla` — how long after submission the community undertakes to decide, including on a referred application; `requirementsGrace` — how long an application started under an earlier `requirementsDigest` is still evaluated under that version.
+ */
+export interface VettingRequirements {
+  /**
+   * Version of this requirements object's shape. `0.1` for the members defined here.
+   */
+  version: string;
+  /**
+   * The endorsement type URI a counted vetting statement carries as `credentialSubject.endorsement.type`, as registered with the community via vtc/endorsement-types/register.
+   */
+  statementType: string;
+  /**
+   * How many counted statements are needed, counting each vetter once however many DIDs they hold.
+   */
+  minStatements: number;
+  /**
+   * Per-method floors within `minStatements` — e.g. `{ "inPerson": 1 }`. Every method named MUST also be in `acceptedMethods`. Absent: no method floor.
+   */
+  minByMethod?: {
+    [k: string]: number | undefined;
+  };
+  /**
+   * Methods whose statements count at all.
+   *
+   * @minItems 1
+   */
+  acceptedMethods: [VettingMethod, ...VettingMethod[]];
+  /**
+   * Documentation a statement must have relied on in order to count. Absent — the expected case — means each vetter decides what documentation they accept, including none for prior acquaintance, and the community counts what they attest.
+   *
+   * @minItems 1
+   */
+  acceptedDocumentClasses?: [VettingDocumentation, ...VettingDocumentation[]];
+  /**
+   * Claim types the applicant's Vetting Card must carry, which the identity commitment is computed over, and which a counted statement must list as verified. Absent: none.
+   */
+  requiredClaims?: ClaimType[];
+  /**
+   * Claim types an applicant MAY add to the card and a vetter MAY verify. They never affect whether a statement counts.
+   */
+  optionalClaims?: ClaimType[];
+  maxStatementAge?: Duration;
+  /**
+   * How a vetter's eligibility is established.
+   */
+  eligibleVetters: {
+    /**
+     * The role named in a community-issued `CommunityRole` endorsement credential (see `vtc/vetting/vetters/grant/0.1`). A statement counts only if its issuer holds that credential.
+     */
+    role: string;
+  };
+  /**
+   * Caps on how much evidence may come from people close to the applicant. Absent: no caps.
+   */
+  independence?: {
+    /**
+     * The most counted statements that may come from vetters declaring each relationship — e.g. `{ "family": 0 }`.
+     */
+    maxByDeclaredRelationship?: {
+      [k: string]: number | undefined;
+    };
+    /**
+     * When true, every counted statement must carry the same identity commitment — all vetters verified the same claimed identity. Absent: false.
+     */
+    requireConsistentIdentityCommitment?: boolean;
+  };
+  /**
+   * Whether an invitation credential must accompany the statements at submission (`required`), may (`optional`), or plays no part (`none`). Absent: the presentation-definition alone governs.
+   */
+  invitation?: "required" | "optional" | "none";
+  decisionSla?: Duration;
+  requirementsGrace?: Duration;
+  /**
+   * Where the community's vetting governance — including the attestation text vetters sign — is published.
+   */
+  governanceFrameworkUrl?: string;
+  [k: string]: unknown | undefined;
+}
+/**
+ * OPTIONAL. How the community asks to be shown to a prospective applicant: a name, an accent colour and a logo. Presentation only, self-asserted and unverified — `communityDid` identifies the community, never `branding`. Not part of any criterion, so not covered by a `requirementsDigest`. Every member is optional.
+ */
+export interface CommunityBranding {
+  /**
+   * The community's name as it asks to be shown.
+   */
+  displayName?: string;
+  /**
+   * An sRGB colour as `#rrggbb`, compared case-insensitively. A community SHOULD write it in lower case.
+   */
+  accentColor?: string;
+  /**
+   * An https URL of the community's logo. Fetched by the client, so an untrusted image from wherever it points.
+   */
+  logoUrl?: string;
+  ext?: Ext;
+}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { ClaimType, DigestMultibase, Ext, VettingDocumentation, VettingMethod };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/vtc/join-requests/manifest/0.2" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = VTCJoinRequestsManifestPayload;
+
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/vtc/join-requests/manifest/0.2#response" as const;
+
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = VTCJoinRequestsManifestResponsePayload;
+
+/**
+ * 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/manifest/0.2",
+  "title": "VTC Join-Requests Manifest — payload",
+  "description": "Discover a community's join criteria before applying. The request carries nothing. Version 0.2 adds, per criterion, an optional `vetting` requirements object — how many identity-vetting statements a community needs, by which methods, from whom — and a `requirementsDigest` that names the exact version of the criterion an applicant started under. The response may also carry `branding`, how the community asks to be shown.",
+  "type": "object",
+  "additionalProperties": false,
+  "properties": {
+    "ext": {
+      "$ref": "#/$defs/Ext"
+    }
+  },
+  "$defs": {
+    "Duration": {
+      "title": "Duration",
+      "type": "string",
+      "maxLength": 32,
+      "pattern": "^P(([0-9]+W)?([0-9]+D)?T([0-9]+H([0-9]+M)?([0-9]+S)?|[0-9]+M([0-9]+S)?|[0-9]+S)|[0-9]+W([0-9]+D)?|[0-9]+D)$",
+      "description": "An ISO 8601 duration in weeks, days, hours, minutes and seconds only (e.g. `P120D`, `P2W`, `P1DT12H`, `PT15M`). Years and months are refused: their length depends on the calendar, and an age limit that means different things on different days is not a limit."
+    },
+    "Criterion": {
+      "title": "Criterion",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "id",
+        "presentationDefinition"
+      ],
+      "dependentRequired": {
+        "vetting": [
+          "requirementsDigest"
+        ]
+      },
+      "properties": {
+        "id": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 128
+        },
+        "description": {
+          "type": "string",
+          "maxLength": 1024,
+          "description": "Plain-language summary of the criterion, authored by the community and shown to prospective applicants. Informative: where it and `vetting` disagree, `vetting` governs."
+        },
+        "presentationDefinition": {
+          "type": "object",
+          "description": "The presentation-definition an applicant must satisfy for this criterion (opaque here)."
+        },
+        "vetting": {
+          "$ref": "#/$defs/VettingRequirements"
+        },
+        "requirementsDigest": {
+          "$ref": "#/$defs/DigestMultibase",
+          "description": "Digest over the RFC 8785 (JCS) canonicalization of this criterion object with the `requirementsDigest` member removed, as a multibase-encoded multihash (SHA-256 and base58btc RECOMMENDED). Names one version of the criterion: an applicant records it when starting an application and echoes it to vetters and at submission. REQUIRED when `vetting` is present."
+        }
+      }
+    },
+    "VettingRequirements": {
+      "title": "VettingRequirements",
+      "type": "object",
+      "additionalProperties": true,
+      "required": [
+        "version",
+        "statementType",
+        "minStatements",
+        "acceptedMethods",
+        "eligibleVetters"
+      ],
+      "description": "What identity-vetting evidence a criterion needs, beyond what a presentation-definition can express: distinct eligible vetters, per-method floors, independence caps. Every number is the community's own policy. This schema supplies no defaults — an absent optional member means the community imposes no constraint of that kind, never that some protocol value applies. Deliberately open: a consumer MUST ignore members it does not recognise, so a community publishing a newer shape does not make an older client unable to read the rest. Durations: `maxStatementAge` — a statement older than this at decision time does not count (absent: no limit beyond the statement's own validity); `decisionSla` — how long after submission the community undertakes to decide, including on a referred application; `requirementsGrace` — how long an application started under an earlier `requirementsDigest` is still evaluated under that version.",
+      "properties": {
+        "version": {
+          "type": "string",
+          "pattern": "^(0|[1-9][0-9]*)\\.(0|[1-9][0-9]*)$",
+          "description": "Version of this requirements object's shape. `0.1` for the members defined here."
+        },
+        "statementType": {
+          "type": "string",
+          "format": "uri",
+          "minLength": 1,
+          "maxLength": 512,
+          "description": "The endorsement type URI a counted vetting statement carries as `credentialSubject.endorsement.type`, as registered with the community via vtc/endorsement-types/register."
+        },
+        "minStatements": {
+          "type": "integer",
+          "minimum": 1,
+          "description": "How many counted statements are needed, counting each vetter once however many DIDs they hold."
+        },
+        "minByMethod": {
+          "type": "object",
+          "propertyNames": {
+            "$ref": "#/$defs/VettingMethod"
+          },
+          "additionalProperties": {
+            "type": "integer",
+            "minimum": 0
+          },
+          "description": "Per-method floors within `minStatements` — e.g. `{ \"inPerson\": 1 }`. Every method named MUST also be in `acceptedMethods`. Absent: no method floor."
+        },
+        "acceptedMethods": {
+          "type": "array",
+          "minItems": 1,
+          "uniqueItems": true,
+          "items": {
+            "$ref": "#/$defs/VettingMethod"
+          },
+          "description": "Methods whose statements count at all."
+        },
+        "acceptedDocumentClasses": {
+          "type": "array",
+          "minItems": 1,
+          "uniqueItems": true,
+          "items": {
+            "$ref": "#/$defs/VettingDocumentation"
+          },
+          "description": "Documentation a statement must have relied on in order to count. Absent — the expected case — means each vetter decides what documentation they accept, including none for prior acquaintance, and the community counts what they attest."
+        },
+        "requiredClaims": {
+          "type": "array",
+          "uniqueItems": true,
+          "items": {
+            "$ref": "#/$defs/ClaimType"
+          },
+          "description": "Claim types the applicant's Vetting Card must carry, which the identity commitment is computed over, and which a counted statement must list as verified. Absent: none."
+        },
+        "optionalClaims": {
+          "type": "array",
+          "uniqueItems": true,
+          "items": {
+            "$ref": "#/$defs/ClaimType"
+          },
+          "description": "Claim types an applicant MAY add to the card and a vetter MAY verify. They never affect whether a statement counts."
+        },
+        "maxStatementAge": {
+          "$ref": "#/$defs/Duration"
+        },
+        "eligibleVetters": {
+          "type": "object",
+          "additionalProperties": false,
+          "required": [
+            "role"
+          ],
+          "properties": {
+            "role": {
+              "type": "string",
+              "minLength": 1,
+              "maxLength": 128,
+              "pattern": "^[a-zA-Z][a-zA-Z0-9_-]*$",
+              "description": "The role named in a community-issued `CommunityRole` endorsement credential (see `vtc/vetting/vetters/grant/0.1`). A statement counts only if its issuer holds that credential."
+            }
+          },
+          "description": "How a vetter's eligibility is established."
+        },
+        "independence": {
+          "type": "object",
+          "additionalProperties": false,
+          "properties": {
+            "maxByDeclaredRelationship": {
+              "type": "object",
+              "propertyNames": {
+                "$ref": "#/$defs/VettingRelationship"
+              },
+              "additionalProperties": {
+                "type": "integer",
+                "minimum": 0
+              },
+              "description": "The most counted statements that may come from vetters declaring each relationship — e.g. `{ \"family\": 0 }`."
+            },
+            "requireConsistentIdentityCommitment": {
+              "type": "boolean",
+              "description": "When true, every counted statement must carry the same identity commitment — all vetters verified the same claimed identity. Absent: false."
+            }
+          },
+          "description": "Caps on how much evidence may come from people close to the applicant. Absent: no caps."
+        },
+        "invitation": {
+          "type": "string",
+          "enum": [
+            "required",
+            "optional",
+            "none"
+          ],
+          "description": "Whether an invitation credential must accompany the statements at submission (`required`), may (`optional`), or plays no part (`none`). Absent: the presentation-definition alone governs."
+        },
+        "decisionSla": {
+          "$ref": "#/$defs/Duration"
+        },
+        "requirementsGrace": {
+          "$ref": "#/$defs/Duration"
+        },
+        "governanceFrameworkUrl": {
+          "type": "string",
+          "format": "uri",
+          "pattern": "^https://",
+          "maxLength": 2048,
+          "description": "Where the community's vetting governance — including the attestation text vetters sign — is published."
+        }
+      }
+    },
+    "CommunityBranding": {
+      "title": "CommunityBranding",
+      "type": "object",
+      "additionalProperties": false,
+      "description": "OPTIONAL. How the community asks to be shown to a prospective applicant: a name, an accent colour and a logo. Presentation only, self-asserted and unverified — `communityDid` identifies the community, never `branding`. Not part of any criterion, so not covered by a `requirementsDigest`. Every member is optional.",
+      "properties": {
+        "displayName": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 128,
+          "description": "The community's name as it asks to be shown."
+        },
+        "accentColor": {
+          "type": "string",
+          "pattern": "^#[0-9a-fA-F]{6}$",
+          "description": "An sRGB colour as `#rrggbb`, compared case-insensitively. A community SHOULD write it in lower case."
+        },
+        "logoUrl": {
+          "type": "string",
+          "format": "uri",
+          "pattern": "^https://",
+          "maxLength": 2048,
+          "description": "An https URL of the community's logo. Fetched by the client, so an untrusted image from wherever it points."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext"
+        }
+      }
+    },
+    "Response": {
+      "$anchor": "response",
+      "title": "VTC Join-Requests Manifest — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "communityDid",
+        "criteria"
+      ],
+      "properties": {
+        "communityDid": {
+          "type": "string",
+          "pattern": "^did:"
+        },
+        "criteria": {
+          "type": "array",
+          "items": {
+            "$ref": "#/$defs/Criterion"
+          }
+        },
+        "branding": {
+          "$ref": "#/$defs/CommunityBranding"
+        },
+        "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-]+)+$"
+      }
+    },
+    "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."
+    },
+    "ClaimType": {
+      "title": "ClaimType",
+      "description": "The vocabulary token naming what a value IS — `name.legal`, `phone.mobile`, `address.postal`, `person.birthDate`. Dotted, most-general segment first, so that a consumer with no knowledge of the specific token can still group by its prefix.\n\nThe token is the maintainer's own; no external vocabulary is primary. External vocabularies (vCard/jCard, OIDC standard claims, schema.org) are mappings applied at PRESENTATION by a renderer, not at rest, so that a query written in any of them can be matched without the store having to live inside any one of them.\n\nThe `x:` prefix is an open extension namespace and is not decoration. The closest prior art — Windows CardSpace's self-issued card — supported exactly fifteen predefined claim types with no extensibility, and that is the specific way it failed the requirement a holder actually has. An `x:` attribute stores, composes, binds and discloses exactly like a known one; it renders generically and matches only an explicit query.",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 128,
+      "pattern": "^(x:)?[a-z][a-zA-Z0-9]*(\\.[a-z][a-zA-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": {
+    "Duration": {
+      "title": "Duration",
+      "type": "string",
+      "maxLength": 32,
+      "pattern": "^P(([0-9]+W)?([0-9]+D)?T([0-9]+H([0-9]+M)?([0-9]+S)?|[0-9]+M([0-9]+S)?|[0-9]+S)|[0-9]+W([0-9]+D)?|[0-9]+D)$",
+      "description": "An ISO 8601 duration in weeks, days, hours, minutes and seconds only (e.g. `P120D`, `P2W`, `P1DT12H`, `PT15M`). Years and months are refused: their length depends on the calendar, and an age limit that means different things on different days is not a limit."
+    },
+    "Criterion": {
+      "title": "Criterion",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "id",
+        "presentationDefinition"
+      ],
+      "dependentRequired": {
+        "vetting": [
+          "requirementsDigest"
+        ]
+      },
+      "properties": {
+        "id": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 128
+        },
+        "description": {
+          "type": "string",
+          "maxLength": 1024,
+          "description": "Plain-language summary of the criterion, authored by the community and shown to prospective applicants. Informative: where it and `vetting` disagree, `vetting` governs."
+        },
+        "presentationDefinition": {
+          "type": "object",
+          "description": "The presentation-definition an applicant must satisfy for this criterion (opaque here)."
+        },
+        "vetting": {
+          "$ref": "#/$defs/VettingRequirements"
+        },
+        "requirementsDigest": {
+          "$ref": "#/$defs/DigestMultibase",
+          "description": "Digest over the RFC 8785 (JCS) canonicalization of this criterion object with the `requirementsDigest` member removed, as a multibase-encoded multihash (SHA-256 and base58btc RECOMMENDED). Names one version of the criterion: an applicant records it when starting an application and echoes it to vetters and at submission. REQUIRED when `vetting` is present."
+        }
+      }
+    },
+    "VettingRequirements": {
+      "title": "VettingRequirements",
+      "type": "object",
+      "additionalProperties": true,
+      "required": [
+        "version",
+        "statementType",
+        "minStatements",
+        "acceptedMethods",
+        "eligibleVetters"
+      ],
+      "description": "What identity-vetting evidence a criterion needs, beyond what a presentation-definition can express: distinct eligible vetters, per-method floors, independence caps. Every number is the community's own policy. This schema supplies no defaults — an absent optional member means the community imposes no constraint of that kind, never that some protocol value applies. Deliberately open: a consumer MUST ignore members it does not recognise, so a community publishing a newer shape does not make an older client unable to read the rest. Durations: `maxStatementAge` — a statement older than this at decision time does not count (absent: no limit beyond the statement's own validity); `decisionSla` — how long after submission the community undertakes to decide, including on a referred application; `requirementsGrace` — how long an application started under an earlier `requirementsDigest` is still evaluated under that version.",
+      "properties": {
+        "version": {
+          "type": "string",
+          "pattern": "^(0|[1-9][0-9]*)\\.(0|[1-9][0-9]*)$",
+          "description": "Version of this requirements object's shape. `0.1` for the members defined here."
+        },
+        "statementType": {
+          "type": "string",
+          "format": "uri",
+          "minLength": 1,
+          "maxLength": 512,
+          "description": "The endorsement type URI a counted vetting statement carries as `credentialSubject.endorsement.type`, as registered with the community via vtc/endorsement-types/register."
+        },
+        "minStatements": {
+          "type": "integer",
+          "minimum": 1,
+          "description": "How many counted statements are needed, counting each vetter once however many DIDs they hold."
+        },
+        "minByMethod": {
+          "type": "object",
+          "propertyNames": {
+            "$ref": "#/$defs/VettingMethod"
+          },
+          "additionalProperties": {
+            "type": "integer",
+            "minimum": 0
+          },
+          "description": "Per-method floors within `minStatements` — e.g. `{ \"inPerson\": 1 }`. Every method named MUST also be in `acceptedMethods`. Absent: no method floor."
+        },
+        "acceptedMethods": {
+          "type": "array",
+          "minItems": 1,
+          "uniqueItems": true,
+          "items": {
+            "$ref": "#/$defs/VettingMethod"
+          },
+          "description": "Methods whose statements count at all."
+        },
+        "acceptedDocumentClasses": {
+          "type": "array",
+          "minItems": 1,
+          "uniqueItems": true,
+          "items": {
+            "$ref": "#/$defs/VettingDocumentation"
+          },
+          "description": "Documentation a statement must have relied on in order to count. Absent — the expected case — means each vetter decides what documentation they accept, including none for prior acquaintance, and the community counts what they attest."
+        },
+        "requiredClaims": {
+          "type": "array",
+          "uniqueItems": true,
+          "items": {
+            "$ref": "#/$defs/ClaimType"
+          },
+          "description": "Claim types the applicant's Vetting Card must carry, which the identity commitment is computed over, and which a counted statement must list as verified. Absent: none."
+        },
+        "optionalClaims": {
+          "type": "array",
+          "uniqueItems": true,
+          "items": {
+            "$ref": "#/$defs/ClaimType"
+          },
+          "description": "Claim types an applicant MAY add to the card and a vetter MAY verify. They never affect whether a statement counts."
+        },
+        "maxStatementAge": {
+          "$ref": "#/$defs/Duration"
+        },
+        "eligibleVetters": {
+          "type": "object",
+          "additionalProperties": false,
+          "required": [
+            "role"
+          ],
+          "properties": {
+            "role": {
+              "type": "string",
+              "minLength": 1,
+              "maxLength": 128,
+              "pattern": "^[a-zA-Z][a-zA-Z0-9_-]*$",
+              "description": "The role named in a community-issued `CommunityRole` endorsement credential (see `vtc/vetting/vetters/grant/0.1`). A statement counts only if its issuer holds that credential."
+            }
+          },
+          "description": "How a vetter's eligibility is established."
+        },
+        "independence": {
+          "type": "object",
+          "additionalProperties": false,
+          "properties": {
+            "maxByDeclaredRelationship": {
+              "type": "object",
+              "propertyNames": {
+                "$ref": "#/$defs/VettingRelationship"
+              },
+              "additionalProperties": {
+                "type": "integer",
+                "minimum": 0
+              },
+              "description": "The most counted statements that may come from vetters declaring each relationship — e.g. `{ \"family\": 0 }`."
+            },
+            "requireConsistentIdentityCommitment": {
+              "type": "boolean",
+              "description": "When true, every counted statement must carry the same identity commitment — all vetters verified the same claimed identity. Absent: false."
+            }
+          },
+          "description": "Caps on how much evidence may come from people close to the applicant. Absent: no caps."
+        },
+        "invitation": {
+          "type": "string",
+          "enum": [
+            "required",
+            "optional",
+            "none"
+          ],
+          "description": "Whether an invitation credential must accompany the statements at submission (`required`), may (`optional`), or plays no part (`none`). Absent: the presentation-definition alone governs."
+        },
+        "decisionSla": {
+          "$ref": "#/$defs/Duration"
+        },
+        "requirementsGrace": {
+          "$ref": "#/$defs/Duration"
+        },
+        "governanceFrameworkUrl": {
+          "type": "string",
+          "format": "uri",
+          "pattern": "^https://",
+          "maxLength": 2048,
+          "description": "Where the community's vetting governance — including the attestation text vetters sign — is published."
+        }
+      }
+    },
+    "CommunityBranding": {
+      "title": "CommunityBranding",
+      "type": "object",
+      "additionalProperties": false,
+      "description": "OPTIONAL. How the community asks to be shown to a prospective applicant: a name, an accent colour and a logo. Presentation only, self-asserted and unverified — `communityDid` identifies the community, never `branding`. Not part of any criterion, so not covered by a `requirementsDigest`. Every member is optional.",
+      "properties": {
+        "displayName": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 128,
+          "description": "The community's name as it asks to be shown."
+        },
+        "accentColor": {
+          "type": "string",
+          "pattern": "^#[0-9a-fA-F]{6}$",
+          "description": "An sRGB colour as `#rrggbb`, compared case-insensitively. A community SHOULD write it in lower case."
+        },
+        "logoUrl": {
+          "type": "string",
+          "format": "uri",
+          "pattern": "^https://",
+          "maxLength": 2048,
+          "description": "An https URL of the community's logo. Fetched by the client, so an untrusted image from wherever it points."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext"
+        }
+      }
+    },
+    "Response": {
+      "$anchor": "response",
+      "title": "VTC Join-Requests Manifest — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "communityDid",
+        "criteria"
+      ],
+      "properties": {
+        "communityDid": {
+          "type": "string",
+          "pattern": "^did:"
+        },
+        "criteria": {
+          "type": "array",
+          "items": {
+            "$ref": "#/$defs/Criterion"
+          }
+        },
+        "branding": {
+          "$ref": "#/$defs/CommunityBranding"
+        },
+        "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-]+)+$"
+      }
+    },
+    "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."
+    },
+    "ClaimType": {
+      "title": "ClaimType",
+      "description": "The vocabulary token naming what a value IS — `name.legal`, `phone.mobile`, `address.postal`, `person.birthDate`. Dotted, most-general segment first, so that a consumer with no knowledge of the specific token can still group by its prefix.\n\nThe token is the maintainer's own; no external vocabulary is primary. External vocabularies (vCard/jCard, OIDC standard claims, schema.org) are mappings applied at PRESENTATION by a renderer, not at rest, so that a query written in any of them can be matched without the store having to live inside any one of them.\n\nThe `x:` prefix is an open extension namespace and is not decoration. The closest prior art — Windows CardSpace's self-issued card — supported exactly fifteen predefined claim types with no extensibility, and that is the specific way it failed the requirement a holder actually has. An `x:` attribute stores, composes, binds and discloses exactly like a known one; it renders generically and matches only an explicit query.",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 128,
+      "pattern": "^(x:)?[a-z][a-zA-Z0-9]*(\\.[a-z][a-zA-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: 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;