@openvtc/trust-tasks 0.25.0 → 0.25.2

package/src/provision/vta/claim/0.1/payload.ts

@@ -0,0 +1,88 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/provision/vta/claim/0.1/payload.schema.json
+ */
+
+import type { Ext, Handle } from "../../../../_shared/components.js";
+
+
+/**
+ * A wallet claims a VTA that a Farm has reserved behind a `vta-claim` trigger link. The document is the first request of the exchange (VTI-LNK-054): issued and signed by a fresh Ed25519 `did:key` that becomes the VTA's administrator, addressed to the Farm, and carrying the reservation's handle both here and as the envelope's `parentThreadId`. The task defines no `#response`: the Farm answers a `trust-task-next-step` expecting `provision/vta/redeem/0.1`, whose response is the hand-over. The outer document members (id, type, issuer, recipient, issuedAt, expiresAt, parentThreadId, proof) are owned by the framework — SPEC §6.3.
+ */
+export interface ProvisionVTAClaimPayload {
+  handle: Handle;
+  ext?: Ext;
+}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { Ext, Handle };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/provision/vta/claim/0.1" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = ProvisionVTAClaimPayload;
+
+/**
+ * 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/provision/vta/claim/0.1",
+  "title": "Provision — VTA Claim — payload",
+  "description": "A wallet claims a VTA that a Farm has reserved behind a `vta-claim` trigger link. The document is the first request of the exchange (VTI-LNK-054): issued and signed by a fresh Ed25519 `did:key` that becomes the VTA's administrator, addressed to the Farm, and carrying the reservation's handle both here and as the envelope's `parentThreadId`. The task defines no `#response`: the Farm answers a `trust-task-next-step` expecting `provision/vta/redeem/0.1`, whose response is the hand-over. The outer document members (id, type, issuer, recipient, issuedAt, expiresAt, parentThreadId, proof) are owned by the framework — SPEC §6.3.",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "handle"
+  ],
+  "properties": {
+    "handle": {
+      "$ref": "#/$defs/Handle"
+    },
+    "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-]+)+$"
+      }
+    },
+    "Handle": {
+      "title": "Handle",
+      "type": "string",
+      "minLength": 22,
+      "maxLength": 43,
+      "pattern": "^[A-Za-z0-9_-]{22,43}$",
+      "description": "The Farm-generated handle of one reservation: 16 to 32 bytes from a cryptographically secure random source, written as unpadded base64url (22 to 43 characters; 16 bytes, 22 characters, is what VTI-LNK-116 recommends). It is the `_id` of the trigger link (VTI-LNK-033) and is compared as a string. In a claim it MUST equal the document's `parentThreadId`. It confers no authority on its holder beyond the right to make one claim."
+    }
+  }
+} 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;

package/src/provision/vta/redeem/0.1/payload.ts

@@ -0,0 +1,255 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/provision/vta/redeem/0.1/payload.schema.json
+ */
+
+import type { Ext, Handle } from "../../../../_shared/components.js";
+
+
+/**
+ * The claimant polls the Farm, with the key that made the claim, for the outcome of its claim on a reservation. Each poll is a freshly signed document carrying the handle. The outer document members (id, type, issuer, recipient, issuedAt, expiresAt, proof) are owned by the framework — SPEC §6.3.
+ */
+export interface ProvisionVTARedeemPayload {
+  handle: Handle;
+  ext?: Ext;
+}
+/**
+ * The hand-over, signed by the Farm's assertionMethod key and sent only once the claimant's key is written into the VTA as its administrator and the VTA answers: which VTA, what the claim did, and where the VTA is reachable. Every earlier state is a `trust-task-error` (`pending`, `rejected`, or a family code), never this document.
+ */
+export interface ProvisionVTARedeemResponsePayload {
+  handle: Handle;
+  /**
+   * The DID of the VTA the claimant now administers. The Farm chooses the DID method; the VTA Farm issues `did:webvh`.
+   */
+  vtaDid: string;
+  /**
+   * What the claim did. `provisionVta`: the claimant is the first administrator of a VTA provisioned for this reservation. `grantAcl`: the claimant was added as an administrator of a VTA that already had one. The Farm derives it from the reservation; the wallet never chooses it.
+   */
+  operation: "provisionVta" | "grantAcl";
+  /**
+   * The DID of the DIDComm mediator the VTA is reachable through. A convenience: the wallet can also read it from the VTA's own DID document.
+   */
+  mediatorDid?: string;
+  /**
+   * Where the VTA's DID log is served. For `did:webvh` it is the `did.jsonl` URL the DID itself encodes. An `https` URL with no userinfo.
+   */
+  didLogUrl?: string;
+  ext?: Ext;
+}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { Ext, Handle };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/provision/vta/redeem/0.1" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = ProvisionVTARedeemPayload;
+
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/provision/vta/redeem/0.1#response" as const;
+
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = ProvisionVTARedeemResponsePayload;
+
+/**
+ * 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/provision/vta/redeem/0.1",
+  "title": "Provision — VTA Redeem — payload",
+  "description": "The claimant polls the Farm, with the key that made the claim, for the outcome of its claim on a reservation. Each poll is a freshly signed document carrying the handle. The outer document members (id, type, issuer, recipient, issuedAt, expiresAt, proof) are owned by the framework — SPEC §6.3.",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "handle"
+  ],
+  "properties": {
+    "handle": {
+      "$ref": "#/$defs/Handle"
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext"
+    }
+  },
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "Provision — VTA Redeem — response payload",
+      "description": "The hand-over, signed by the Farm's assertionMethod key and sent only once the claimant's key is written into the VTA as its administrator and the VTA answers: which VTA, what the claim did, and where the VTA is reachable. Every earlier state is a `trust-task-error` (`pending`, `rejected`, or a family code), never this document.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "handle",
+        "vtaDid",
+        "operation"
+      ],
+      "properties": {
+        "handle": {
+          "$ref": "#/$defs/Handle"
+        },
+        "vtaDid": {
+          "type": "string",
+          "minLength": 8,
+          "maxLength": 2048,
+          "pattern": "^did:[a-z0-9]+:[^\\s]+$",
+          "description": "The DID of the VTA the claimant now administers. The Farm chooses the DID method; the VTA Farm issues `did:webvh`."
+        },
+        "operation": {
+          "type": "string",
+          "enum": [
+            "provisionVta",
+            "grantAcl"
+          ],
+          "description": "What the claim did. `provisionVta`: the claimant is the first administrator of a VTA provisioned for this reservation. `grantAcl`: the claimant was added as an administrator of a VTA that already had one. The Farm derives it from the reservation; the wallet never chooses it."
+        },
+        "mediatorDid": {
+          "type": "string",
+          "minLength": 8,
+          "maxLength": 2048,
+          "pattern": "^did:[a-z0-9]+:[^\\s]+$",
+          "description": "The DID of the DIDComm mediator the VTA is reachable through. A convenience: the wallet can also read it from the VTA's own DID document."
+        },
+        "didLogUrl": {
+          "type": "string",
+          "minLength": 9,
+          "maxLength": 2048,
+          "pattern": "^https://[^@/?#\\s]+(/[^\\s]*)?$",
+          "description": "Where the VTA's DID log is served. For `did:webvh` it is the `did.jsonl` URL the DID itself encodes. An `https` URL with no userinfo."
+        },
+        "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-]+)+$"
+      }
+    },
+    "Handle": {
+      "title": "Handle",
+      "type": "string",
+      "minLength": 22,
+      "maxLength": 43,
+      "pattern": "^[A-Za-z0-9_-]{22,43}$",
+      "description": "The Farm-generated handle of one reservation: 16 to 32 bytes from a cryptographically secure random source, written as unpadded base64url (22 to 43 characters; 16 bytes, 22 characters, is what VTI-LNK-116 recommends). It is the `_id` of the trigger link (VTI-LNK-033) and is compared as a string. In a claim it MUST equal the document's `parentThreadId`. It confers no authority on its holder beyond the right to make one claim."
+    }
+  }
+} as const;
+
+/** As {@link PAYLOAD_SCHEMA}, for the success-response variant. */
+export const RESPONSE_PAYLOAD_SCHEMA = {
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$ref": "#/$defs/Response",
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "Provision — VTA Redeem — response payload",
+      "description": "The hand-over, signed by the Farm's assertionMethod key and sent only once the claimant's key is written into the VTA as its administrator and the VTA answers: which VTA, what the claim did, and where the VTA is reachable. Every earlier state is a `trust-task-error` (`pending`, `rejected`, or a family code), never this document.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "handle",
+        "vtaDid",
+        "operation"
+      ],
+      "properties": {
+        "handle": {
+          "$ref": "#/$defs/Handle"
+        },
+        "vtaDid": {
+          "type": "string",
+          "minLength": 8,
+          "maxLength": 2048,
+          "pattern": "^did:[a-z0-9]+:[^\\s]+$",
+          "description": "The DID of the VTA the claimant now administers. The Farm chooses the DID method; the VTA Farm issues `did:webvh`."
+        },
+        "operation": {
+          "type": "string",
+          "enum": [
+            "provisionVta",
+            "grantAcl"
+          ],
+          "description": "What the claim did. `provisionVta`: the claimant is the first administrator of a VTA provisioned for this reservation. `grantAcl`: the claimant was added as an administrator of a VTA that already had one. The Farm derives it from the reservation; the wallet never chooses it."
+        },
+        "mediatorDid": {
+          "type": "string",
+          "minLength": 8,
+          "maxLength": 2048,
+          "pattern": "^did:[a-z0-9]+:[^\\s]+$",
+          "description": "The DID of the DIDComm mediator the VTA is reachable through. A convenience: the wallet can also read it from the VTA's own DID document."
+        },
+        "didLogUrl": {
+          "type": "string",
+          "minLength": 9,
+          "maxLength": 2048,
+          "pattern": "^https://[^@/?#\\s]+(/[^\\s]*)?$",
+          "description": "Where the VTA's DID log is served. For `did:webvh` it is the `did.jsonl` URL the DID itself encodes. An `https` URL with no userinfo."
+        },
+        "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-]+)+$"
+      }
+    },
+    "Handle": {
+      "title": "Handle",
+      "type": "string",
+      "minLength": 22,
+      "maxLength": 43,
+      "pattern": "^[A-Za-z0-9_-]{22,43}$",
+      "description": "The Farm-generated handle of one reservation: 16 to 32 bytes from a cryptographically secure random source, written as unpadded base64url (22 to 43 characters; 16 bytes, 22 characters, is what VTI-LNK-116 recommends). It is the `_id` of the trigger link (VTI-LNK-033) and is compared as a string. In a claim it MUST equal the document's `parentThreadId`. It confers no authority on its holder beyond the right to make one claim."
+    }
+  }
+} as const;
+
+/**
+ * SPEC.md §7.2 policy for the request variant, from this specification's
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
+ * per-specification and cannot be derived from the document alone, and
+ * item 2 needs the schema this carries.
+ */
+export const SPEC = {
+  typeUri: TYPE_URI,
+  isBearer: false,
+  isProofRequired: true,
+  isRecipientRequired: true,
+  isIssuedAtRequired: true,
+  payloadSchema: PAYLOAD_SCHEMA,
+} as const;
+
+/**
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
+ * tracks the *issuer* party's requirement because a response swaps the
+ * parties (§7.3 item 5).
+ */
+export const RESPONSE_SPEC = {
+  typeUri: RESPONSE_TYPE_URI,
+  isBearer: false,
+  isProofRequired: true,
+  isRecipientRequired: true,
+  isIssuedAtRequired: true,
+  payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
+} as const;

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

@@ -0,0 +1,17 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vetting/_shared/0.1/hidden-vetting.schema.json
+ */
+
+/**
+ * Definitions used by more than one hidden-vetting task: the parameters a community stores and publishes for a criterion (vtc/vetting/hidden/publish, vtc/vetting/hidden/show, and the member-side vta/pcs engine tasks that take them as input), and the metadata of one attestation (vetting/attestation and the vta/pcs tasks that produce, hold and prove over attestations). Not itself a Trust Task specification: the `_shared` folder is skipped by the registry build and the codegen.
+ */
+export interface HiddenVettingSharedDefinitions {
+  [k: string]: unknown | undefined;
+}
+
+/**
+ * The definitions this shared schema publishes, hoisted to one declaration each.
+ * See "../../../_shared/components.js".
+ */
+export type { PublishedConfig, PublishedEvent, StatementMeta, StoredConfig, StoredEvent, TickLength, Tier } from "../../../_shared/components.js";

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

@@ -3,7 +3,7 @@
  * Source: specs/vetting/attestation/0.1/payload.schema.json
  */
 
-import type { Ext } from "../../../_shared/components.js";
+import type { Ext, StatementMeta } from "../../../_shared/components.js";
 
 
 /**
@@ -18,6 +18,9 @@ export interface VettingAttestationPayload {
    * The attestation itself, multibase base58btc: a tag, a shown class credential and a proof. It carries no identifier of the vetter — the tag is deterministic for this (vetter, applicant) pair and unlinkable across applicants.
    */
   attestation: string;
+  /**
+   * The facts the community will count. Bound into the attestation, so changing one here invalidates it.
+   */
   meta: StatementMeta;
   /**
    * The attestation token spent for this attestation. The community records the serial, which is how a vetter's rate is capped without anybody learning who they are.
@@ -38,61 +41,6 @@ export interface VettingAttestationPayload {
   };
   ext?: Ext;
 }
-/**
- * The facts the community will count. Bound into the attestation, so changing one here invalidates it.
- */
-export interface StatementMeta {
-  /**
-   * The community this attestation is for. An attestation is not portable between communities.
-   */
-  community: string;
-  /**
-   * The digest of the criterion's requirements as the vetter read them.
-   */
-  requirementsDigest: string;
-  /**
-   * How the vetter met the applicant.
-   */
-  method: "inPerson" | "video" | "priorAcquaintance";
-  /**
-   * The claim types the vetter checked.
-   *
-   * @minItems 1
-   */
-  claimsVerified: [string, ...string[]];
-  /**
-   * Whether the vetter confirmed a live person.
-   */
-  livenessConfirmed: boolean;
-  /**
-   * The relationship the vetter declared, which the community's independence rules count.
-   */
-  declaredRelationship: "none" | "family" | "sameEmployer" | "closeFriend" | "other";
-  /**
-   * The commitment on the Vetting Card the applicant showed. Consistency across attestations is what stops two applicants pooling them.
-   */
-  identityCommitment: string;
-  /**
-   * Digest of that card, as the vetter verified it.
-   */
-  cardDigestMultibase: string;
-  /**
-   * A DATE, never a timestamp: an exact time would let a community line an attestation up with a vetter's activity, which undoes the proof without touching it.
-   */
-  validFrom: string;
-  /**
-   * A date, for the same reason.
-   */
-  validUntil: string;
-  /**
-   * The token label spent, repeated inside the bound facts so it cannot be swapped in transit.
-   */
-  tokenLabel: string;
-  /**
-   * The token serial spent, likewise bound.
-   */
-  tokenSerial: string;
-}
 /**
  * The applicant's receipt. It verifies the attestation on arrival rather than at submit, so a vetter learns immediately that what it sent is usable.
  */
@@ -109,7 +57,7 @@ export interface VettingAttestationResponsePayload {
 }
 
 /** Shared definitions this specification references, re-exported under the names it used to declare them with. */
-export type { Ext };
+export type { Ext, StatementMeta };
 
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/vetting/attestation/0.1" as const;
@@ -194,6 +142,40 @@ export const PAYLOAD_SCHEMA = {
     }
   },
   "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "Vetting Attestation — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "accepted"
+      ],
+      "description": "The applicant's receipt. It verifies the attestation on arrival rather than at submit, so a vetter learns immediately that what it sent is usable.",
+      "properties": {
+        "accepted": {
+          "type": "boolean",
+          "description": "Whether the attestation verified against the community's published parameters and the card the applicant showed."
+        },
+        "heldCount": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "OPTIONAL. How many attestations the applicant now holds for this criterion — a courtesy so a vetter can tell someone they are done."
+        },
+        "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-]+)+$"
+      }
+    },
     "StatementMeta": {
       "type": "object",
       "additionalProperties": false,
@@ -288,7 +270,15 @@ export const PAYLOAD_SCHEMA = {
           "description": "The token serial spent, likewise bound."
         }
       }
-    },
+    }
+  }
+} as const;
+
+/** As {@link PAYLOAD_SCHEMA}, for the success-response variant. */
+export const RESPONSE_PAYLOAD_SCHEMA = {
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$ref": "#/$defs/Response",
+  "$defs": {
     "Response": {
       "$anchor": "response",
       "title": "Vetting Attestation — response payload",
@@ -322,15 +312,7 @@ export const PAYLOAD_SCHEMA = {
       "propertyNames": {
         "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
       }
-    }
-  }
-} as const;
-
-/** As {@link PAYLOAD_SCHEMA}, for the success-response variant. */
-export const RESPONSE_PAYLOAD_SCHEMA = {
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$ref": "#/$defs/Response",
-  "$defs": {
+    },
     "StatementMeta": {
       "type": "object",
       "additionalProperties": false,
@@ -425,40 +407,6 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
           "description": "The token serial spent, likewise bound."
         }
       }
-    },
-    "Response": {
-      "$anchor": "response",
-      "title": "Vetting Attestation — response payload",
-      "type": "object",
-      "additionalProperties": false,
-      "required": [
-        "accepted"
-      ],
-      "description": "The applicant's receipt. It verifies the attestation on arrival rather than at submit, so a vetter learns immediately that what it sent is usable.",
-      "properties": {
-        "accepted": {
-          "type": "boolean",
-          "description": "Whether the attestation verified against the community's published parameters and the card the applicant showed."
-        },
-        "heldCount": {
-          "type": "integer",
-          "minimum": 0,
-          "description": "OPTIONAL. How many attestations the applicant now holds for this criterion — a courtesy so a vetter can tell someone they are done."
-        },
-        "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-]+)+$"
-      }
     }
   }
 } as const;

package/src/vta/_shared/0.4/pcs-engine.ts

@@ -0,0 +1,17 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vta/_shared/0.4/pcs-engine.schema.json
+ */
+
+/**
+ * A VTA can act as the hidden-vetting (PCS) engine of its principal: it holds the principal's PCS secret keys, and runs every member-side PCS operation — a vetter's enrolment, token drip and attestation, and an applicant's receipt of attestations and its proof — so that the client carrying the messages never holds a PCS key. These definitions describe the inputs the engine takes and the wire forms it produces. The normative rules (custody, one key per vetter and community, authorization, audit) are in CONVENTIONS.md beside this file. Not itself a Trust Task specification: the `_shared` folder is skipped by the registry build and the codegen.
+ */
+export interface PCSEngineSharedDefinitionsForTheVtaPcsTasks {
+  [k: string]: unknown | undefined;
+}
+
+/**
+ * The definitions this shared schema publishes, hoisted to one declaration each.
+ * See "../../../_shared/components.js".
+ */
+export type { ApplicationSummary, Attestation, AttestationMeta, AttestationToken, CommunityParameters, HiddenVettingSubmission, Multibase, SubmittedStatement, TokenDraw, VetterSummary } from "../../../_shared/components.js";