@openvtc/trust-tasks 0.19.2 → 0.19.4

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;