@openvtc/trust-tasks 0.26.18 → 0.26.20

package/dist/vtc/join-requests/manifest/0.4/payload.js

@@ -0,0 +1,1293 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vtc/join-requests/manifest/0.4/payload.schema.json
+ */
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/vtc/join-requests/manifest/0.4";
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/vtc/join-requests/manifest/0.4#response";
+/**
+ * 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.4",
+    "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. Version 0.4 adds `directoryDisclosure`: where the community has a member directory, the statement of what it would disclose about a member and to whom, so an applicant reads it before applying.",
+    "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",
+                "admission",
+                "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."
+                },
+                "admission": {
+                    "type": "string",
+                    "enum": [
+                        "automatic",
+                        "review"
+                    ],
+                    "description": "How the community decides a submission that meets this criterion. `automatic`: it admits the applicant without a person deciding. `review`: it refers the submission to an administrator, who decides."
+                },
+                "presentationDefinition": {
+                    "type": "object",
+                    "description": "The credentials an applicant must present for this criterion (opaque here). Absent: the criterion requires no credential."
+                },
+                "credentialIssuers": {
+                    "type": "string",
+                    "enum": [
+                        "any",
+                        "community",
+                        "recognised"
+                    ],
+                    "description": "Whose credentials meet `presentationDefinition`: `community` (this community's own), `recognised` (this community's, or a community it recognises), or `any` (any issuer whose credential verifies). Present exactly when `presentationDefinition` is."
+                },
+                "invitationRequired": {
+                    "type": "boolean",
+                    "description": "True: the criterion is met only by a submission carrying a valid, unconsumed invitation this community issued to the applicant."
+                },
+                "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."
+                }
+            },
+            "dependentRequired": {
+                "presentationDefinition": [
+                    "credentialIssuers"
+                ],
+                "credentialIssuers": [
+                    "presentationDefinition"
+                ]
+            }
+        },
+        "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 predicate IRI a counted vetting statement carries in `credentialSubject.predicate` — `https://registry.trustoverip.org/dtg/vsc/vetted/1`, the DTG VSC registry's identity-vetting predicate, or a predicate in a namespace the community controls — registered as one the community accepts via vtc/endorsement-types/register. A statement under any other predicate does not count."
+                },
+                "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 a statement's issuer must hold, matched as the action `role:<role>` in a Verifiable Authority Credential (`AuthorityCredential`) the community issued to that issuer, whose `authority.scope` is the community's DID (see `vtc/vetting/vetters/grant/0.1`). A statement counts only if its issuer holds such a 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."
+                },
+                "ext": {
+                    "description": "Ecosystem-defined extension members per SPEC.md §4.5.1, for vetting parameters this version does not enumerate. A community publishing an admission mode the base members cannot express — the zero-knowledge parameters an applicant proves against, say — puts them under a namespace it controls, rather than waiting for a version that names them.\n\nThis object is already `additionalProperties: true`, so an unknown member here has always validated. That is not the same as reaching a consumer: a generated type names the members this schema declares and drops the rest, so an undeclared member is parsed and discarded, and it is discarded again on the re-serialization `requirementsDigest` is computed over. `ext` is a declared member, so it survives both.",
+                    "$ref": "#/$defs/Ext"
+                },
+                "extCritical": {
+                    "description": "Namespaces of `ext` an applicant MUST understand or refuse, per SPEC.md §4.5.1.\n\nA community marks a namespace here when applying under this criterion without understanding it would mean something other than what the community requires — an applicant that ignored a hidden-vetting namespace, for instance, would submit named statements to a criterion whose whole point was that it does not receive them. An applicant that does not recognize a marked namespace stops rather than downgrading silently.\n\nAbsent, which is the common case, every namespace under `ext` is advisory and ignorable.",
+                    "$ref": "#/$defs/ExtCritical"
+                }
+            }
+        },
+        "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"
+                    }
+                },
+                "requestedAttributes": {
+                    "type": "array",
+                    "maxItems": 32,
+                    "description": "What the community asks an applicant to tell it about themselves, as claim types — never values. Answered in persona terms: the applicant's agent discloses those attributes from the face the applicant chooses, and they arrive on vtc/join-requests/submit as `attributes`. SELF-ASSERTED: a community MUST NOT describe an answer as verified, and MUST NOT make a decision that assumes it is. Outside every criterion, so no `requirementsDigest` covers it. Absent when the community asks nothing.",
+                    "items": {
+                        "type": "object",
+                        "additionalProperties": false,
+                        "required": [
+                            "type"
+                        ],
+                        "properties": {
+                            "type": {
+                                "type": "string",
+                                "minLength": 1,
+                                "maxLength": 128,
+                                "pattern": "^(x:)?[a-z][A-Za-z0-9]*(\\.[a-z][A-Za-z0-9]*)*$",
+                                "description": "A claim-type token from the persona claim-type registry (persona/_shared/0.1/CLAIM-TYPES.md) — `name.display`, `address.country` — or an `x:` extension token."
+                            },
+                            "required": {
+                                "type": "boolean",
+                                "default": true,
+                                "description": "False for an attribute the applicant may decline. A submission missing a required one is refused with vtc/join-requests/submit:attributesMissing."
+                            },
+                            "purpose": {
+                                "type": "string",
+                                "maxLength": 256,
+                                "description": "Why the community asks, in words shown to the applicant before they disclose."
+                            }
+                        }
+                    }
+                },
+                "branding": {
+                    "$ref": "#/$defs/CommunityBranding"
+                },
+                "directoryDisclosure": {
+                    "$ref": "#/$defs/DirectoryDisclosure",
+                    "description": "Present exactly where the community offers a member directory: the statement, generated from its configuration, of what the directory would disclose about a member and to whom — the same statement vtc/directory/disclosure returns. Outside every criterion, so no `requirementsDigest` covers it; it names itself with its own `statementDigest`."
+                },
+                "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-]+)+$"
+            }
+        },
+        "DirectoryDisclosure": {
+            "title": "DirectoryDisclosure",
+            "description": "The statement itself. Every member is generated from the community's configuration when the statement is read. `statementDigest` names this exact statement, so an applicant can record which one it was shown.",
+            "type": "object",
+            "additionalProperties": false,
+            "required": [
+                "fields",
+                "newCard",
+                "membershipIdentifiers",
+                "adminNotes",
+                "externalCards",
+                "statementDigest"
+            ],
+            "properties": {
+                "fields": {
+                    "type": "array",
+                    "maxItems": 128,
+                    "items": {
+                        "$ref": "#/$defs/DisclosedField"
+                    },
+                    "description": "Every active field, base and community-defined, in display order. A base field the community has disabled is absent, which is how a reader learns it is not collected."
+                },
+                "newCard": {
+                    "$ref": "#/$defs/NewCardDefaults"
+                },
+                "membershipIdentifiers": {
+                    "$ref": "#/$defs/Audience",
+                    "description": "The widest audience a member's membership identifier — the DID they joined with — can reach through the directory: the ceiling of the base field `did`, or `admins` where that field is disabled. `members` or `public` means a member may choose to show it that widely; a new card never shows it beyond `admins` (VTI-DIR-042). Administrators always see it."
+                },
+                "adminNotes": {
+                    "type": "boolean",
+                    "description": "Whether administrators keep notes about members. Notes are never on a card and never reach another member; a member may ask for the notes about them."
+                },
+                "groups": {
+                    "$ref": "#/$defs/GroupDisclosure"
+                },
+                "externalCards": {
+                    "type": "boolean",
+                    "description": "Whether a member may publish a card beyond the community: their `public` values, signed by them, offered through the community's trust registry. Always the member's own choice, and off on a new card. False where the community cannot publish external cards."
+                },
+                "statementDigest": {
+                    "$ref": "#/$defs/DigestMultibase",
+                    "description": "Digest over the RFC 8785 (JCS) canonicalization of this statement with the `statementDigest` member removed, as a multibase-encoded multihash (SHA-256 and base58btc RECOMMENDED). Changes exactly when what the statement says changes."
+                },
+                "ext": {
+                    "$ref": "#/$defs/Ext"
+                }
+            }
+        },
+        "GroupDisclosure": {
+            "title": "GroupDisclosure",
+            "description": "Present when the community has groups. A member of a group holds a credential, issued by the group's own identifier, that evidences their membership, and can present it outside the community — which is why an applicant is told.",
+            "type": "object",
+            "additionalProperties": false,
+            "required": [
+                "credentialValidity"
+            ],
+            "properties": {
+                "credentialValidity": {
+                    "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": "How long each group membership credential is valid for, as an ISO 8601 duration in weeks, days, hours, minutes and seconds (`P30D`). It is renewed while the member stays in the group, and a credential already issued stays valid until it expires even after its holder leaves."
+                }
+            }
+        },
+        "NewCardDefaults": {
+            "title": "NewCardDefaults",
+            "description": "The discoverability a card has when the community creates it, before its member chooses. A new card is never published beyond the community (VTI-DIR-042), so there is no member for that here: `externalCards` says whether the member may turn it on.",
+            "type": "object",
+            "additionalProperties": false,
+            "required": [
+                "listing",
+                "search"
+            ],
+            "properties": {
+                "listing": {
+                    "$ref": "#/$defs/Listing",
+                    "description": "The listing a new card starts with: the community's `defaultListing` (vtc/directory/fields/list). Every member may always choose `hidden`."
+                },
+                "search": {
+                    "type": "string",
+                    "enum": [
+                        "byName",
+                        "exactNickname",
+                        "off"
+                    ],
+                    "description": "What a member's search may match, as the card's `discoverability.search`."
+                },
+                "introductions": {
+                    "$ref": "#/$defs/Introductions",
+                    "description": "From whom a new card accepts introductions. Absent where the community does not deliver introductions."
+                }
+            }
+        },
+        "Introductions": {
+            "title": "Introductions",
+            "description": "Who may ask the community to introduce them to this member. `anyone`: any active member who can find the entry. `groups`: only members who share a community group with them. `connections`: only members holding an attributed, in-force verified relationship with them. `off`: nobody. A refused introduction is never reported to its sender.",
+            "type": "string",
+            "enum": [
+                "anyone",
+                "groups",
+                "connections",
+                "off"
+            ]
+        },
+        "Listing": {
+            "title": "Listing",
+            "description": "Whether members can find the entry. `listed`: it appears when members browse. `findable`: it does not appear when browsing, but a search that matches it under `search` returns it. `hidden`: no member finds it by browsing or searching; administrators still see it, and members who share a group that shows its members see it in that group's member list.",
+            "type": "string",
+            "enum": [
+                "listed",
+                "findable",
+                "hidden"
+            ]
+        },
+        "DisclosedField": {
+            "title": "DisclosedField",
+            "description": "One active field of the community's directory, as an applicant needs to see it: what it is, who writes its value, the widest audience it may ever reach and the audience a new card gives it. Disabled and retired fields are not listed: no projection shows them.",
+            "type": "object",
+            "additionalProperties": false,
+            "required": [
+                "key",
+                "label",
+                "type",
+                "source",
+                "ceiling",
+                "defaultVisibility",
+                "searchable"
+            ],
+            "properties": {
+                "key": {
+                    "$ref": "#/$defs/FieldKey"
+                },
+                "label": {
+                    "$ref": "#/$defs/FieldLabel"
+                },
+                "description": {
+                    "$ref": "#/$defs/FieldDescription"
+                },
+                "type": {
+                    "$ref": "#/$defs/FieldType"
+                },
+                "source": {
+                    "$ref": "#/$defs/FieldSource",
+                    "description": "Who writes the value. `admin` and `credential` matter most to an applicant: an `admin` field holds what the community asserts about the member, which the member reads and cannot change."
+                },
+                "ceiling": {
+                    "$ref": "#/$defs/Audience",
+                    "description": "The widest audience the field may ever reach, whatever the member chooses."
+                },
+                "defaultVisibility": {
+                    "$ref": "#/$defs/Audience",
+                    "description": "The audience a new card gives the field until its member chooses. Never wider than `ceiling`."
+                },
+                "searchable": {
+                    "type": "boolean",
+                    "description": "Whether a member's search may match the field, within what the searcher may see."
+                },
+                "facet": {
+                    "type": "boolean",
+                    "description": "Whether members may filter on the field and see counts by its values. Absent: false."
+                }
+            }
+        },
+        "Audience": {
+            "title": "Audience",
+            "description": "Who may see a directory field, ordered from narrowest to widest. `admins`: holders of `vtc.directory.admin` (and, for derived fields, `vtc.members.manage`). `groups`: members who share at least one community group with the subject (narrowed to the groups the subject names in `groupAudience`, where it names any). `connections`: members holding an attributed, in-force verified relationship with the subject at the community. `members`: every active member. `public`: anyone, and what the member's signed public card carries outside the community.\n\n`groups` and `connections` are not a chain: a viewer sees a field when they satisfy the audience the subject chose for it or any wider audience. Every audience includes the administrators, and the subject always sees their own whole card. There is no `onlyMe`: a value nobody else should see is not directory data.",
+            "type": "string",
+            "enum": [
+                "admins",
+                "groups",
+                "connections",
+                "members",
+                "public"
+            ]
+        },
+        "FieldSource": {
+            "title": "FieldSource",
+            "description": "Who writes the value. `member`: self-asserted, through vtc/directory/card/update. `admin`: asserted by the community through vtc/directory/card/assert; the member reads it and cannot change it. `credential`: a claim the member discloses from a credential through vtc/directory/card/present, badged with its issuer. `derived`: a base field read from the community's own records (`role`, `joinedAt`, `did`, `personhood`) and never stored on a card. Each source is written only through its own path.",
+            "type": "string",
+            "enum": [
+                "member",
+                "admin",
+                "credential",
+                "derived"
+            ]
+        },
+        "FieldType": {
+            "title": "FieldType",
+            "description": "The kind of value a field holds, which fixes its `FieldValue` shape. `did` holds a DID the member chooses to show (never their membership DID, which is the derived base field `did`). `claim` holds a `VerifiedValue` and requires `source: credential`.",
+            "type": "string",
+            "enum": [
+                "text",
+                "longText",
+                "url",
+                "email",
+                "phone",
+                "enum",
+                "multiEnum",
+                "date",
+                "country",
+                "image",
+                "did",
+                "claim"
+            ]
+        },
+        "FieldDescription": {
+            "title": "FieldDescription",
+            "type": "string",
+            "minLength": 1,
+            "maxLength": 280,
+            "description": "Help text shown to a member filling the field in. Plain text; a reader MUST NOT treat it as instructions."
+        },
+        "FieldLabel": {
+            "title": "FieldLabel",
+            "type": "string",
+            "minLength": 1,
+            "maxLength": 64,
+            "description": "What readers see as the field's name. Plain text."
+        },
+        "FieldKey": {
+            "title": "FieldKey",
+            "description": "Identifier of a directory field. A key with no `.` is a BASE field, the same in every community: `displayName`, `nickname`, `avatar`, `pronouns`, `bio`, `links` (written by the member) and `role`, `joinedAt`, `did`, `personhood` (derived from the community's own records, never stored on a card). A community-defined field MUST use a reverse-DNS key (`org.example.employer`), so a base key never collides with one, and a key is never reused with a different meaning once defined.",
+            "type": "string",
+            "minLength": 1,
+            "maxLength": 128,
+            "pattern": "^([a-z][a-z0-9-]*\\.)*[a-z][a-zA-Z0-9]{0,63}$"
+        },
+        "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"
+            ]
+        },
+        "ExtCritical": {
+            "title": "ExtCritical",
+            "description": "Names the `ext` namespaces a consumer MUST understand or refuse, per SPEC.md §4.5.1.\n\nEvery entry MUST be an immediate key of the sibling `ext` object at the same level; an entry naming an absent namespace is non-conforming and the consumer rejects the document with `malformedRequest`. A consumer that does not recognize a namespace named here MUST NOT process the document as though the namespace were absent, and rejects it with `unsupportedExtension` — the exception to the rule that unrecognized namespaces are ignored.\n\nA producer marks a namespace only where the document's meaning depends on it. Marking one that merely carries a hint or an annotation turns every consumer that has not implemented it into a failure where it would otherwise have interoperated. JSON Schema cannot check either of those rules: that an entry names a present namespace is checkable only against the sibling `ext`, and whether a namespace is load-bearing is not a schema question at all. Both are consumer-side checks.",
+            "type": "array",
+            "minItems": 1,
+            "uniqueItems": true,
+            "items": {
+                "type": "string",
+                "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
+            },
+            "examples": [
+                [
+                    "org.openvtc.hidden-vetting"
+                ]
+            ]
+        },
+        "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."
+        }
+    }
+};
+/** 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",
+                "admission",
+                "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."
+                },
+                "admission": {
+                    "type": "string",
+                    "enum": [
+                        "automatic",
+                        "review"
+                    ],
+                    "description": "How the community decides a submission that meets this criterion. `automatic`: it admits the applicant without a person deciding. `review`: it refers the submission to an administrator, who decides."
+                },
+                "presentationDefinition": {
+                    "type": "object",
+                    "description": "The credentials an applicant must present for this criterion (opaque here). Absent: the criterion requires no credential."
+                },
+                "credentialIssuers": {
+                    "type": "string",
+                    "enum": [
+                        "any",
+                        "community",
+                        "recognised"
+                    ],
+                    "description": "Whose credentials meet `presentationDefinition`: `community` (this community's own), `recognised` (this community's, or a community it recognises), or `any` (any issuer whose credential verifies). Present exactly when `presentationDefinition` is."
+                },
+                "invitationRequired": {
+                    "type": "boolean",
+                    "description": "True: the criterion is met only by a submission carrying a valid, unconsumed invitation this community issued to the applicant."
+                },
+                "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."
+                }
+            },
+            "dependentRequired": {
+                "presentationDefinition": [
+                    "credentialIssuers"
+                ],
+                "credentialIssuers": [
+                    "presentationDefinition"
+                ]
+            }
+        },
+        "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 predicate IRI a counted vetting statement carries in `credentialSubject.predicate` — `https://registry.trustoverip.org/dtg/vsc/vetted/1`, the DTG VSC registry's identity-vetting predicate, or a predicate in a namespace the community controls — registered as one the community accepts via vtc/endorsement-types/register. A statement under any other predicate does not count."
+                },
+                "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 a statement's issuer must hold, matched as the action `role:<role>` in a Verifiable Authority Credential (`AuthorityCredential`) the community issued to that issuer, whose `authority.scope` is the community's DID (see `vtc/vetting/vetters/grant/0.1`). A statement counts only if its issuer holds such a 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."
+                },
+                "ext": {
+                    "description": "Ecosystem-defined extension members per SPEC.md §4.5.1, for vetting parameters this version does not enumerate. A community publishing an admission mode the base members cannot express — the zero-knowledge parameters an applicant proves against, say — puts them under a namespace it controls, rather than waiting for a version that names them.\n\nThis object is already `additionalProperties: true`, so an unknown member here has always validated. That is not the same as reaching a consumer: a generated type names the members this schema declares and drops the rest, so an undeclared member is parsed and discarded, and it is discarded again on the re-serialization `requirementsDigest` is computed over. `ext` is a declared member, so it survives both.",
+                    "$ref": "#/$defs/Ext"
+                },
+                "extCritical": {
+                    "description": "Namespaces of `ext` an applicant MUST understand or refuse, per SPEC.md §4.5.1.\n\nA community marks a namespace here when applying under this criterion without understanding it would mean something other than what the community requires — an applicant that ignored a hidden-vetting namespace, for instance, would submit named statements to a criterion whose whole point was that it does not receive them. An applicant that does not recognize a marked namespace stops rather than downgrading silently.\n\nAbsent, which is the common case, every namespace under `ext` is advisory and ignorable.",
+                    "$ref": "#/$defs/ExtCritical"
+                }
+            }
+        },
+        "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"
+                    }
+                },
+                "requestedAttributes": {
+                    "type": "array",
+                    "maxItems": 32,
+                    "description": "What the community asks an applicant to tell it about themselves, as claim types — never values. Answered in persona terms: the applicant's agent discloses those attributes from the face the applicant chooses, and they arrive on vtc/join-requests/submit as `attributes`. SELF-ASSERTED: a community MUST NOT describe an answer as verified, and MUST NOT make a decision that assumes it is. Outside every criterion, so no `requirementsDigest` covers it. Absent when the community asks nothing.",
+                    "items": {
+                        "type": "object",
+                        "additionalProperties": false,
+                        "required": [
+                            "type"
+                        ],
+                        "properties": {
+                            "type": {
+                                "type": "string",
+                                "minLength": 1,
+                                "maxLength": 128,
+                                "pattern": "^(x:)?[a-z][A-Za-z0-9]*(\\.[a-z][A-Za-z0-9]*)*$",
+                                "description": "A claim-type token from the persona claim-type registry (persona/_shared/0.1/CLAIM-TYPES.md) — `name.display`, `address.country` — or an `x:` extension token."
+                            },
+                            "required": {
+                                "type": "boolean",
+                                "default": true,
+                                "description": "False for an attribute the applicant may decline. A submission missing a required one is refused with vtc/join-requests/submit:attributesMissing."
+                            },
+                            "purpose": {
+                                "type": "string",
+                                "maxLength": 256,
+                                "description": "Why the community asks, in words shown to the applicant before they disclose."
+                            }
+                        }
+                    }
+                },
+                "branding": {
+                    "$ref": "#/$defs/CommunityBranding"
+                },
+                "directoryDisclosure": {
+                    "$ref": "#/$defs/DirectoryDisclosure",
+                    "description": "Present exactly where the community offers a member directory: the statement, generated from its configuration, of what the directory would disclose about a member and to whom — the same statement vtc/directory/disclosure returns. Outside every criterion, so no `requirementsDigest` covers it; it names itself with its own `statementDigest`."
+                },
+                "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-]+)+$"
+            }
+        },
+        "DirectoryDisclosure": {
+            "title": "DirectoryDisclosure",
+            "description": "The statement itself. Every member is generated from the community's configuration when the statement is read. `statementDigest` names this exact statement, so an applicant can record which one it was shown.",
+            "type": "object",
+            "additionalProperties": false,
+            "required": [
+                "fields",
+                "newCard",
+                "membershipIdentifiers",
+                "adminNotes",
+                "externalCards",
+                "statementDigest"
+            ],
+            "properties": {
+                "fields": {
+                    "type": "array",
+                    "maxItems": 128,
+                    "items": {
+                        "$ref": "#/$defs/DisclosedField"
+                    },
+                    "description": "Every active field, base and community-defined, in display order. A base field the community has disabled is absent, which is how a reader learns it is not collected."
+                },
+                "newCard": {
+                    "$ref": "#/$defs/NewCardDefaults"
+                },
+                "membershipIdentifiers": {
+                    "$ref": "#/$defs/Audience",
+                    "description": "The widest audience a member's membership identifier — the DID they joined with — can reach through the directory: the ceiling of the base field `did`, or `admins` where that field is disabled. `members` or `public` means a member may choose to show it that widely; a new card never shows it beyond `admins` (VTI-DIR-042). Administrators always see it."
+                },
+                "adminNotes": {
+                    "type": "boolean",
+                    "description": "Whether administrators keep notes about members. Notes are never on a card and never reach another member; a member may ask for the notes about them."
+                },
+                "groups": {
+                    "$ref": "#/$defs/GroupDisclosure"
+                },
+                "externalCards": {
+                    "type": "boolean",
+                    "description": "Whether a member may publish a card beyond the community: their `public` values, signed by them, offered through the community's trust registry. Always the member's own choice, and off on a new card. False where the community cannot publish external cards."
+                },
+                "statementDigest": {
+                    "$ref": "#/$defs/DigestMultibase",
+                    "description": "Digest over the RFC 8785 (JCS) canonicalization of this statement with the `statementDigest` member removed, as a multibase-encoded multihash (SHA-256 and base58btc RECOMMENDED). Changes exactly when what the statement says changes."
+                },
+                "ext": {
+                    "$ref": "#/$defs/Ext"
+                }
+            }
+        },
+        "GroupDisclosure": {
+            "title": "GroupDisclosure",
+            "description": "Present when the community has groups. A member of a group holds a credential, issued by the group's own identifier, that evidences their membership, and can present it outside the community — which is why an applicant is told.",
+            "type": "object",
+            "additionalProperties": false,
+            "required": [
+                "credentialValidity"
+            ],
+            "properties": {
+                "credentialValidity": {
+                    "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": "How long each group membership credential is valid for, as an ISO 8601 duration in weeks, days, hours, minutes and seconds (`P30D`). It is renewed while the member stays in the group, and a credential already issued stays valid until it expires even after its holder leaves."
+                }
+            }
+        },
+        "NewCardDefaults": {
+            "title": "NewCardDefaults",
+            "description": "The discoverability a card has when the community creates it, before its member chooses. A new card is never published beyond the community (VTI-DIR-042), so there is no member for that here: `externalCards` says whether the member may turn it on.",
+            "type": "object",
+            "additionalProperties": false,
+            "required": [
+                "listing",
+                "search"
+            ],
+            "properties": {
+                "listing": {
+                    "$ref": "#/$defs/Listing",
+                    "description": "The listing a new card starts with: the community's `defaultListing` (vtc/directory/fields/list). Every member may always choose `hidden`."
+                },
+                "search": {
+                    "type": "string",
+                    "enum": [
+                        "byName",
+                        "exactNickname",
+                        "off"
+                    ],
+                    "description": "What a member's search may match, as the card's `discoverability.search`."
+                },
+                "introductions": {
+                    "$ref": "#/$defs/Introductions",
+                    "description": "From whom a new card accepts introductions. Absent where the community does not deliver introductions."
+                }
+            }
+        },
+        "Introductions": {
+            "title": "Introductions",
+            "description": "Who may ask the community to introduce them to this member. `anyone`: any active member who can find the entry. `groups`: only members who share a community group with them. `connections`: only members holding an attributed, in-force verified relationship with them. `off`: nobody. A refused introduction is never reported to its sender.",
+            "type": "string",
+            "enum": [
+                "anyone",
+                "groups",
+                "connections",
+                "off"
+            ]
+        },
+        "Listing": {
+            "title": "Listing",
+            "description": "Whether members can find the entry. `listed`: it appears when members browse. `findable`: it does not appear when browsing, but a search that matches it under `search` returns it. `hidden`: no member finds it by browsing or searching; administrators still see it, and members who share a group that shows its members see it in that group's member list.",
+            "type": "string",
+            "enum": [
+                "listed",
+                "findable",
+                "hidden"
+            ]
+        },
+        "DisclosedField": {
+            "title": "DisclosedField",
+            "description": "One active field of the community's directory, as an applicant needs to see it: what it is, who writes its value, the widest audience it may ever reach and the audience a new card gives it. Disabled and retired fields are not listed: no projection shows them.",
+            "type": "object",
+            "additionalProperties": false,
+            "required": [
+                "key",
+                "label",
+                "type",
+                "source",
+                "ceiling",
+                "defaultVisibility",
+                "searchable"
+            ],
+            "properties": {
+                "key": {
+                    "$ref": "#/$defs/FieldKey"
+                },
+                "label": {
+                    "$ref": "#/$defs/FieldLabel"
+                },
+                "description": {
+                    "$ref": "#/$defs/FieldDescription"
+                },
+                "type": {
+                    "$ref": "#/$defs/FieldType"
+                },
+                "source": {
+                    "$ref": "#/$defs/FieldSource",
+                    "description": "Who writes the value. `admin` and `credential` matter most to an applicant: an `admin` field holds what the community asserts about the member, which the member reads and cannot change."
+                },
+                "ceiling": {
+                    "$ref": "#/$defs/Audience",
+                    "description": "The widest audience the field may ever reach, whatever the member chooses."
+                },
+                "defaultVisibility": {
+                    "$ref": "#/$defs/Audience",
+                    "description": "The audience a new card gives the field until its member chooses. Never wider than `ceiling`."
+                },
+                "searchable": {
+                    "type": "boolean",
+                    "description": "Whether a member's search may match the field, within what the searcher may see."
+                },
+                "facet": {
+                    "type": "boolean",
+                    "description": "Whether members may filter on the field and see counts by its values. Absent: false."
+                }
+            }
+        },
+        "Audience": {
+            "title": "Audience",
+            "description": "Who may see a directory field, ordered from narrowest to widest. `admins`: holders of `vtc.directory.admin` (and, for derived fields, `vtc.members.manage`). `groups`: members who share at least one community group with the subject (narrowed to the groups the subject names in `groupAudience`, where it names any). `connections`: members holding an attributed, in-force verified relationship with the subject at the community. `members`: every active member. `public`: anyone, and what the member's signed public card carries outside the community.\n\n`groups` and `connections` are not a chain: a viewer sees a field when they satisfy the audience the subject chose for it or any wider audience. Every audience includes the administrators, and the subject always sees their own whole card. There is no `onlyMe`: a value nobody else should see is not directory data.",
+            "type": "string",
+            "enum": [
+                "admins",
+                "groups",
+                "connections",
+                "members",
+                "public"
+            ]
+        },
+        "FieldSource": {
+            "title": "FieldSource",
+            "description": "Who writes the value. `member`: self-asserted, through vtc/directory/card/update. `admin`: asserted by the community through vtc/directory/card/assert; the member reads it and cannot change it. `credential`: a claim the member discloses from a credential through vtc/directory/card/present, badged with its issuer. `derived`: a base field read from the community's own records (`role`, `joinedAt`, `did`, `personhood`) and never stored on a card. Each source is written only through its own path.",
+            "type": "string",
+            "enum": [
+                "member",
+                "admin",
+                "credential",
+                "derived"
+            ]
+        },
+        "FieldType": {
+            "title": "FieldType",
+            "description": "The kind of value a field holds, which fixes its `FieldValue` shape. `did` holds a DID the member chooses to show (never their membership DID, which is the derived base field `did`). `claim` holds a `VerifiedValue` and requires `source: credential`.",
+            "type": "string",
+            "enum": [
+                "text",
+                "longText",
+                "url",
+                "email",
+                "phone",
+                "enum",
+                "multiEnum",
+                "date",
+                "country",
+                "image",
+                "did",
+                "claim"
+            ]
+        },
+        "FieldDescription": {
+            "title": "FieldDescription",
+            "type": "string",
+            "minLength": 1,
+            "maxLength": 280,
+            "description": "Help text shown to a member filling the field in. Plain text; a reader MUST NOT treat it as instructions."
+        },
+        "FieldLabel": {
+            "title": "FieldLabel",
+            "type": "string",
+            "minLength": 1,
+            "maxLength": 64,
+            "description": "What readers see as the field's name. Plain text."
+        },
+        "FieldKey": {
+            "title": "FieldKey",
+            "description": "Identifier of a directory field. A key with no `.` is a BASE field, the same in every community: `displayName`, `nickname`, `avatar`, `pronouns`, `bio`, `links` (written by the member) and `role`, `joinedAt`, `did`, `personhood` (derived from the community's own records, never stored on a card). A community-defined field MUST use a reverse-DNS key (`org.example.employer`), so a base key never collides with one, and a key is never reused with a different meaning once defined.",
+            "type": "string",
+            "minLength": 1,
+            "maxLength": 128,
+            "pattern": "^([a-z][a-z0-9-]*\\.)*[a-z][a-zA-Z0-9]{0,63}$"
+        },
+        "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"
+            ]
+        },
+        "ExtCritical": {
+            "title": "ExtCritical",
+            "description": "Names the `ext` namespaces a consumer MUST understand or refuse, per SPEC.md §4.5.1.\n\nEvery entry MUST be an immediate key of the sibling `ext` object at the same level; an entry naming an absent namespace is non-conforming and the consumer rejects the document with `malformedRequest`. A consumer that does not recognize a namespace named here MUST NOT process the document as though the namespace were absent, and rejects it with `unsupportedExtension` — the exception to the rule that unrecognized namespaces are ignored.\n\nA producer marks a namespace only where the document's meaning depends on it. Marking one that merely carries a hint or an annotation turns every consumer that has not implemented it into a failure where it would otherwise have interoperated. JSON Schema cannot check either of those rules: that an entry names a present namespace is checkable only against the sibling `ext`, and whether a namespace is load-bearing is not a schema question at all. Both are consumer-side checks.",
+            "type": "array",
+            "minItems": 1,
+            "uniqueItems": true,
+            "items": {
+                "type": "string",
+                "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
+            },
+            "examples": [
+                [
+                    "org.openvtc.hidden-vetting"
+                ]
+            ]
+        },
+        "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."
+        }
+    }
+};
+/**
+ * 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,
+};
+/**
+ * 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,
+};
+//# sourceMappingURL=payload.js.map