@openvtc/trust-tasks 0.19.3 → 0.19.5

package/src/_shared/components.ts

@@ -42,6 +42,10 @@ export type AuditAction =
   | "accountChangeQueueLimits"
   | "adminAdd"
   | "adminStrip";
+/**
+ * A calendar date, `YYYY-MM-DD` (RFC 3339 full-date), with no time or zone. Compared as a UTC date.
+ */
+export type CalendarDate = string;
 /**
  * Fine-grained capability flag scoped to the device's allowed contexts. See SPEC.md for the full semantics of each. Capability values are additive: a consumer MUST ignore a value it does not recognise rather than reject the binding, and MUST NOT treat an unrecognised value as conferring anything.
  */
@@ -94,6 +98,10 @@ export type ConsumerKind_DeviceV0_1 = Companion_DeviceV0_1 | Service_DeviceV0_1;
  * Discriminator: is this consumer a user-driven Companion or a headless Service?
  */
 export type ConsumerKind_DeviceV0_2 = Companion_DeviceV0_2 | Service_DeviceV0_2;
+/**
+ * An ISO 3166-1 alpha-2 country code, upper case, e.g. `DE`.
+ */
+export type CountryCode = string;
 /**
  * Stable identifier for an issued credential — the handle for revocation and audit. Opaque to the holder: it MUST be echoed verbatim when revoking and MUST NOT be parsed.
  */
@@ -209,10 +217,18 @@ export type KeyType = "ed25519" | "x25519" | "p256";
  * The interaction kind: a 1:1 direct message, a multi-party group, or a broadcast channel.
  */
 export type Kind = "dm" | "group" | "channel";
+/**
+ * A BCP 47 language tag, e.g. `en`, `de-AT`. Compared case-insensitively.
+ */
+export type LanguageTag = string;
 /**
  * Scopes one application's records within a context, so several tools can share a context without colliding — `openvtc`, `cnm`, an agent runtime. The maintainer MUST NOT interpret the value; it is an opaque partition name. Namespaces are first-come and unreserved, so an application SHOULD pick a stable, specific one: a future per-namespace ACL would grant on this exact string, which makes renaming a namespace a migration rather than an edit.
  */
 export type Namespace = string;
+/**
+ * A region or city name as the vetter writes it. Compared case-insensitively and otherwise exactly.
+ */
+export type PlaceName = string;
 /**
  * One line of a profile, in exactly one of four forms. Together they are the whole of a profile's flexibility, and each exists for a case the others handle badly.
  *
@@ -488,6 +504,195 @@ export type Version_PersonaV0_1 = number;
  * A value of the namespace's monotonic write counter (see this schema's description). Server-assigned; a producer never chooses one.
  */
 export type Version_VtaV0_1 = number;
+/**
+ * What documentation the vetter relies on, in the same tokens as vetting/request's `acceptsDocumentation` — `passport`, `nationalId`, `driverLicence`, `none`, or another lowerCamelCase class. The vetter's own choice; empty says nothing either way.
+ *
+ * @maxItems 16
+ */
+export type VetterAcceptsDocumentation =
+  | []
+  | [VettingDocumentation]
+  | [VettingDocumentation, VettingDocumentation]
+  | [VettingDocumentation, VettingDocumentation, VettingDocumentation]
+  | [VettingDocumentation, VettingDocumentation, VettingDocumentation, VettingDocumentation]
+  | [VettingDocumentation, VettingDocumentation, VettingDocumentation, VettingDocumentation, VettingDocumentation]
+  | [
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation
+    ]
+  | [
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation
+    ]
+  | [
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation
+    ]
+  | [
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation
+    ]
+  | [
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation
+    ]
+  | [
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation
+    ]
+  | [
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation
+    ]
+  | [
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation
+    ]
+  | [
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation
+    ]
+  | [
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation
+    ]
+  | [
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation,
+      VettingDocumentation
+    ];
+/**
+ * Vetter-authored free text on when they are available to vet. Attributed to the vetter.
+ */
+export type VetterAvailability = string;
+/**
+ * Vetter-authored free text on how to obtain a ticket from them, e.g. `Find me at the OpenVTC booth`. A hint, not an address a request can be sent to: vetting/request still needs a ticket or an introduction the vetter accepts.
+ */
+export type VetterContactHint = string;
+/**
+ * The name the vetter chooses to be listed under. Self-asserted and unverified: it is not the name on any document, and a client MUST attribute it to the vetter.
+ */
+export type VetterDisplayName = string;
+/**
+ * The methods the vetter offers, from `inPerson`, `video`, `priorAcquaintance`.
+ *
+ * @minItems 1
+ * @maxItems 3
+ */
+export type VetterMethods =
+  | [VettingMethod]
+  | [VettingMethod, VettingMethod]
+  | [VettingMethod, VettingMethod, VettingMethod];
+/**
+ * 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.
+ */
+export type VettingDocumentation = string;
+/**
+ * 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.
+ */
+export type VettingMethod = "inPerson" | "video" | "priorAcquaintance";
+/**
+ * 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.
+ */
+export type VettingRelationship = "none" | "communityColleague" | "sameEmployer" | "family" | "otherPersonal";
 /**
  * A Verifiable Identifier (SPEC §4.8). For a mediator-served account this is the account's controlling DID, carried verbatim and compared by exact string equality. For privacy — and because some mediators key accounts by a one-way hash and never hold the full DID — a stable hash of the DID (e.g. its SHA-256 digest) is an equally valid value here: producer and consumer simply agree on the same opaque identifier and compare by exact string equality. The field carries whichever form the issuing mediator uses.
  */
@@ -1390,6 +1595,23 @@ export interface CredentialReference {
    */
   expiresAt?: string | null;
 }
+/**
+ * A W3C Data Integrity proof by the card's publisher. Additional Data Integrity members (e.g. `created`) are permitted and are covered as the cryptosuite defines.
+ */
+export interface DataIntegrityProof {
+  type: "DataIntegrityProof";
+  /**
+   * e.g. `eddsa-jcs-2022`.
+   */
+  cryptosuite: string;
+  /**
+   * A verification method of `publisher`, authorized for `assertionMethod`.
+   */
+  verificationMethod: string;
+  proofPurpose: "assertionMethod";
+  proofValue: string;
+  [k: string]: unknown | undefined;
+}
 /**
  * One presentation request awaiting the holder's decision, as the approver sees it.
  *
@@ -3645,6 +3867,102 @@ export interface VerdictWith {
    */
   presentationDefinition?: {};
 }
+/**
+ * An event the vetter will attend and vet at. `endDate` is on or after `startDate` and no more than 31 days after it; JSON Schema cannot compare two members, so the community checks both and refuses a violation with `malformedRequest`.
+ */
+export interface VetterEvent {
+  /**
+   * The event's name, e.g. `Linux Plumbers Conference 2026`.
+   */
+  name: string;
+  startDate: CalendarDate;
+  endDate: CalendarDate;
+  location?: VetterLocation;
+  /**
+   * OPTIONAL. The event's own https page.
+   */
+  url?: string;
+}
+/**
+ * Where a vetter can meet people, as coarse as the vetter chooses: a country, optionally a region, optionally a city. Never a street address.
+ */
+export interface VetterLocation {
+  country: CountryCode;
+  region?: PlaceName;
+  city?: PlaceName;
+}
+export interface VettingCard {
+  /**
+   * Exactly `VerifiableDataStructure`, `RelationshipCard` and `VettingCard`, in any order.
+   *
+   * @minItems 3
+   * @maxItems 3
+   */
+  type: [
+    "VerifiableDataStructure" | "RelationshipCard" | "VettingCard",
+    "VerifiableDataStructure" | "RelationshipCard" | "VettingCard",
+    "VerifiableDataStructure" | "RelationshipCard" | "VettingCard"
+  ];
+  /**
+   * Fresh per card. A card is never re-sent to a second session under the same id.
+   */
+  id: string;
+  /**
+   * The applicant's DID — the issuer of the vetting request and the subject every resulting statement names. The card is signed with this DID's assertion key.
+   */
+  publisher: string;
+  cardVersion: number;
+  /**
+   * The vetter's DID — the issuer of the vetting session. A card addressed to anyone else is refused.
+   */
+  audience: string;
+  /**
+   * The community the applicant is being vetted for.
+   */
+  community: string;
+  /**
+   * The session's challenge, copied verbatim.
+   */
+  challenge: string;
+  /**
+   * The session's domain, copied verbatim.
+   */
+  domain: string;
+  issuedAt: string;
+  /**
+   * No later than the session's `expiresAt`.
+   */
+  expiresAt: string;
+  /**
+   * @minItems 1
+   */
+  claims: [VettingCardClaim, ...VettingCardClaim[]];
+  /**
+   * digestMultibase over the RFC 8785 canonicalization of `{ "salt": commitmentSalt, "claims": R }`, where R is `{ "type", "value" }` for every card claim whose type the session lists in `requiredClaims`, ordered by `type` then `value` (code-point order). SHA-256 RECOMMENDED. Because the applicant uses one salt per application, every vetter of that application sees the same value.
+   */
+  identityCommitment: DigestMultibase;
+  /**
+   * 32 random bytes, base64url without padding, generated once per application. Goes to vetters inside the card and to nobody else: a party holding the commitment without the salt cannot test guesses at the claimed name.
+   */
+  commitmentSalt: string;
+  proof: DataIntegrityProof;
+}
+export interface VettingCardClaim {
+  /**
+   * The claim type. `person.portrait` is refused: identity vetting works by a vetter looking at the person, not by transmitting their image.
+   */
+  type: ClaimType;
+  /**
+   * The claimed value, exactly as rendered from the applicant's persona — a string for most claim types, structured JSON for some (e.g. a postal address). Authored by the applicant and asserted under their signature; the vetter's check is what gives it any assurance.
+   */
+  value: {
+    [k: string]: unknown | undefined;
+  };
+  /**
+   * Where the value's assurance comes from. `selfAsserted` — the applicant says so, and the vetter's human check is the only assurance added — is the only value this version defines; a verifier MUST NOT treat any other value as adding assurance it does not understand.
+   */
+  provenance: string;
+}
 /**
  * An opaque, gateway-issued reference to a device's push channel (push wake-up binding, https://trusttasks.org/binding/push/0.1). The push gateway returns it to the device at registration; the device conveys it to its VTA (device/set-wake), and the VTA provisions it to authorized triggers (its mediator and/or itself). The raw platform push token (APNs/FCM/WebPush) is held ONLY by the gateway and is never represented here — the handle abstracts the platform, so adding new push methods (e.g. PWA Web Push) needs no change to triggers or VTA config. A handle is a bearer capability to *request* a wake (subject to the gateway's allowlist), never to read the channel.
  */

package/src/index.ts

@@ -326,6 +326,12 @@ export * as VaultUpsert_v0_2 from "./vault/upsert/0.2/payload.js";
 export * as VaultUpsert_v0_3 from "./vault/upsert/0.3/payload.js";
 export * as VaultUsage_v0_1 from "./vault/usage/0.1/payload.js";
 export * as VaultUsage_v0_2 from "./vault/usage/0.2/payload.js";
+export * as IdentityVettingShared_v0_1 from "./vetting/_shared/0.1/identity-vetting.js";
+export * as VettingCardShared_v0_1 from "./vetting/_shared/0.1/vetting-card.js";
+export * as VettingShared_v0_1 from "./vetting/_shared/0.1/vetting.js";
+export * as VettingDecline_v0_1 from "./vetting/decline/0.1/payload.js";
+export * as VettingRequest_v0_1 from "./vetting/request/0.1/payload.js";
+export * as VettingSession_v0_1 from "./vetting/session/0.1/payload.js";
 export * as VrcRelationshipsIssue_v0_1 from "./vrc/relationships/issue/0.1/payload.js";
 export * as VrcRelationshipsPropose_v0_1 from "./vrc/relationships/propose/0.1/payload.js";
 export * as AppStateRecordShared_v0_1 from "./vta/_shared/0.1/app-state-record.js";
@@ -401,6 +407,7 @@ export * as VtaWebvhDidsCreate_v1_0 from "./vta/webvh/dids/create/1.0/payload.js
 export * as VtaWebvhDidsDelete_v1_0 from "./vta/webvh/dids/delete/1.0/payload.js";
 export * as VtaWebvhDidsGet_v1_0 from "./vta/webvh/dids/get/1.0/payload.js";
 export * as VtaWebvhDidsList_v1_0 from "./vta/webvh/dids/list/1.0/payload.js";
+export * as VtaWebvhDidsRealignKeys_v1_0 from "./vta/webvh/dids/realign-keys/1.0/payload.js";
 export * as VtaWebvhDidsRegisterWithServer_v1_0 from "./vta/webvh/dids/register-with-server/1.0/payload.js";
 export * as VtaWebvhDidsRotateKeys_v1_0 from "./vta/webvh/dids/rotate-keys/1.0/payload.js";
 export * as VtaWebvhDidsUpdate_v1_0 from "./vta/webvh/dids/update/1.0/payload.js";
@@ -420,6 +427,7 @@ export * as InvitationShared_v0_1 from "./vtc/_shared/0.1/invitation.js";
 export * as InviteShared_v0_1 from "./vtc/_shared/0.1/invite.js";
 export * as JoinRequestShared_v0_1 from "./vtc/_shared/0.1/join-request.js";
 export * as MemberShared_v0_1 from "./vtc/_shared/0.1/member.js";
+export * as VetterProfileShared_v0_1 from "./vtc/_shared/0.1/vetter-profile.js";
 export * as VtcAdminBootstrap_v0_1 from "./vtc/admin/bootstrap/0.1/payload.js";
 export * as VtcAdminInvitesCreate_v0_1 from "./vtc/admin/invites/create/0.1/payload.js";
 export * as VtcAdminInvitesList_v0_1 from "./vtc/admin/invites/list/0.1/payload.js";
@@ -455,6 +463,7 @@ export * as VtcJoinRequestsApprove_v0_1 from "./vtc/join-requests/approve/0.1/pa
 export * as VtcJoinRequestsDecide_v0_1 from "./vtc/join-requests/decide/0.1/payload.js";
 export * as VtcJoinRequestsList_v0_1 from "./vtc/join-requests/list/0.1/payload.js";
 export * as VtcJoinRequestsManifest_v0_1 from "./vtc/join-requests/manifest/0.1/payload.js";
+export * as VtcJoinRequestsManifest_v0_2 from "./vtc/join-requests/manifest/0.2/payload.js";
 export * as VtcJoinRequestsReject_v0_1 from "./vtc/join-requests/reject/0.1/payload.js";
 export * as VtcJoinRequestsShow_v0_1 from "./vtc/join-requests/show/0.1/payload.js";
 export * as VtcJoinRequestsStatus_v0_1 from "./vtc/join-requests/status/0.1/payload.js";
@@ -492,6 +501,11 @@ export * as VtcRelationshipsPublish_v0_2 from "./vtc/relationships/publish/0.2/p
 export * as VtcRelationshipsRequest_v0_1 from "./vtc/relationships/request/0.1/payload.js";
 export * as VtcRelationshipsRequest_v0_2 from "./vtc/relationships/request/0.2/payload.js";
 export * as VtcRelationshipsRevoke_v0_1 from "./vtc/relationships/revoke/0.1/payload.js";
+export * as VtcVettingRevokeStatement_v0_1 from "./vtc/vetting/revoke-statement/0.1/payload.js";
+export * as VtcVettingVettersGrant_v0_1 from "./vtc/vetting/vetters/grant/0.1/payload.js";
+export * as VtcVettingVettersList_v0_1 from "./vtc/vetting/vetters/list/0.1/payload.js";
+export * as VtcVettingVettersProfile_v0_1 from "./vtc/vetting/vetters/profile/0.1/payload.js";
+export * as VtcVettingVettersResend_v0_1 from "./vtc/vetting/vetters/resend/0.1/payload.js";
 export * as VtcWebsiteFilesDelete_v0_1 from "./vtc/website/files/delete/0.1/payload.js";
 export * as VtcWebsiteFilesList_v0_1 from "./vtc/website/files/list/0.1/payload.js";
 export * as VtcWebsiteGenerationsList_v0_1 from "./vtc/website/generations/list/0.1/payload.js";

package/src/vetting/_shared/0.1/identity-vetting.ts

@@ -0,0 +1,11 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vetting/_shared/0.1/identity-vetting.schema.json
+ */
+
+/**
+ * The `credentialSubject.endorsement` body of a Vetting Statement: a Verifiable Endorsement Credential issued by a vetter's member DID about an applicant's DID, attesting that the vetter checked the applicant's claimed identity in a vetting session. A community registers this shape as the `claimSchema` of its identity-vetting endorsement type (vtc/endorsement-types/register), and names that type in its manifest as `vetting.statementType`. The credential envelope — issuer, validity, `taskContext`, proof — belongs to DTG credentials; only the body is defined here. It records what the vetter did and relied on, never what they saw: no document number, no image, no claimed name. Not itself a Trust Task specification (the `_shared` folder is skipped by the registry build and the codegen).
+ */
+export interface IdentityVettingEndorsementSharedDefinition {
+  [k: string]: unknown | undefined;
+}

package/src/vetting/_shared/0.1/vetting-card.ts

@@ -0,0 +1,17 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vetting/_shared/0.1/vetting-card.schema.json
+ */
+
+/**
+ * The Vetting Card: a signed, audience-bound profile of the relationship card (r-card) an applicant presents to one vetter in one vetting session. A Verifiable Data Structure — its publisher signs it so the recipient can verify it — bound by `audience`, `challenge` and `domain` to exactly one vetter and one session, and valid for minutes. It carries the identity claims the vetter checks against the person and their documentation, and a salted `identityCommitment` over the required claims so a community can later confirm every vetter checked the same claimed identity without ever seeing it. It never carries a document number, a document image, or a portrait. Returned by vetting/session#response; its digest is carried in the identity-vetting endorsement. Not itself a Trust Task specification (the `_shared` folder is skipped by the registry build and the codegen).
+ */
+export interface VettingCardSharedDefinition {
+  [k: string]: unknown | undefined;
+}
+
+/**
+ * The definitions this shared schema publishes, hoisted to one declaration each.
+ * See "../../../_shared/components.js".
+ */
+export type { DataIntegrityProof, VettingCard, VettingCardClaim } from "../../../_shared/components.js";

package/src/vetting/_shared/0.1/vetting.ts

@@ -0,0 +1,17 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vetting/_shared/0.1/vetting.schema.json
+ */
+
+/**
+ * The vocabularies every identity-vetting artifact is written in: how a vetter established who an applicant is (VettingMethod), what documentation is accepted or was relied on (VettingDocumentation), and how the vetter knows the applicant (VettingRelationship). Used by vtc/join-requests/manifest (what a community requires), the vetting/* peer tasks (what a vetter offers and does), and the identity-vetting endorsement body (what a vetter attested). One definition, so a community's requirement and a vetter's statement are compared value-for-value rather than by translation. Claim types are not redefined here: they are the persona family's ClaimType (persona/_shared/0.1/persona-record), because a Vetting Card is rendered from a persona. Not itself a Trust Task specification (the `_shared` folder is skipped by the registry build and the codegen).
+ */
+export interface VettingSharedVocabulary {
+  [k: string]: unknown | undefined;
+}
+
+/**
+ * The definitions this shared schema publishes, hoisted to one declaration each.
+ * See "../../../_shared/components.js".
+ */
+export type { VettingDocumentation, VettingMethod, VettingRelationship } from "../../../_shared/components.js";

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

@@ -0,0 +1,111 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vetting/decline/0.1/payload.schema.json
+ */
+
+import type { Ext } from "../../../_shared/components.js";
+
+
+/**
+ * A vetter tells an applicant it will not issue a Vetting Statement for an accepted request. The reason code is optional: a vetter never has to justify declining. Sent to the applicant only — never to the community.
+ */
+export interface VettingDeclinePayload {
+  /**
+   * The `requestId` from the vetter's acceptance of the applicant's vetting request.
+   */
+  requestId: string;
+  /**
+   * OPTIONAL. `couldNotVerify` — the vetter could not establish the claimed identity. `documentMismatch` — the documentation did not match the card or the person. `livenessFailed` — the match code could not be confirmed with the person. `notComfortable` — the vetter prefers not to attest. `other` — none of these.
+   */
+  code?: "couldNotVerify" | "documentMismatch" | "livenessFailed" | "notComfortable" | "other";
+  /**
+   * OPTIONAL vetter-authored text for the applicant. Attributed to the vetter on every surface that renders it; read by the applicant only.
+   */
+  message?: string;
+  ext?: Ext;
+}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { Ext };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/vetting/decline/0.1" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = VettingDeclinePayload;
+
+/**
+ * This specification's payload schema, as a value.
+ *
+ * SPEC.md §7.2 item 2 is performed against this. It is shipped as data
+ * rather than only as a `.json` file because TypeScript types are erased
+ * at runtime: without a schema a consumer has nothing to validate, and
+ * every REQUIRED payload member is optional in practice. Cross-file
+ * `$ref`s are already inlined, so it needs no resolver.
+ */
+export const PAYLOAD_SCHEMA = {
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://trusttasks.org/spec/vetting/decline/0.1",
+  "title": "Vetting Decline — payload",
+  "description": "A vetter tells an applicant it will not issue a Vetting Statement for an accepted request. The reason code is optional: a vetter never has to justify declining. Sent to the applicant only — never to the community.",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "requestId"
+  ],
+  "properties": {
+    "requestId": {
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 128,
+      "description": "The `requestId` from the vetter's acceptance of the applicant's vetting request."
+    },
+    "code": {
+      "type": "string",
+      "enum": [
+        "couldNotVerify",
+        "documentMismatch",
+        "livenessFailed",
+        "notComfortable",
+        "other"
+      ],
+      "description": "OPTIONAL. `couldNotVerify` — the vetter could not establish the claimed identity. `documentMismatch` — the documentation did not match the card or the person. `livenessFailed` — the match code could not be confirmed with the person. `notComfortable` — the vetter prefers not to attest. `other` — none of these."
+    },
+    "message": {
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 500,
+      "description": "OPTIONAL vetter-authored text for the applicant. Attributed to the vetter on every surface that renders it; read by the applicant only."
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext"
+    }
+  },
+  "$defs": {
+    "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-]+)+$"
+      }
+    }
+  }
+} as const;
+
+/**
+ * SPEC.md §7.2 policy for the request variant, from this specification's
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
+ * per-specification and cannot be derived from the document alone, and
+ * item 2 needs the schema this carries.
+ */
+export const SPEC = {
+  typeUri: TYPE_URI,
+  isBearer: false,
+  isProofRequired: true,
+  isRecipientRequired: true,
+  isIssuedAtRequired: true,
+  payloadSchema: PAYLOAD_SCHEMA,
+} as const;