@openvtc/trust-tasks 0.2.60 → 0.4.0

package/dist/vtc/relationships/request/0.1/payload.d.ts

@@ -0,0 +1,65 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vtc/relationships/request/0.1/payload.schema.json
+ */
+/**
+ * A member asks another member to issue them a Verifiable Relationship Credential. Everything here is a hint: the issuing member decides, and declines with a trust-task-error carrying `vtc/relationships/request:declined` rather than a bespoke rejection message.
+ */
+export interface VTCRelationshipsRequestPayload {
+    /**
+     * Why the requester is asking, in their own words, for the issuing member to weigh. A hint and not a term — the issuing member is under no obligation to honour it, and MUST NOT treat its absence as a defect. Free text reaching a human, so a producer SHOULD keep it to what it is willing to have quoted back.
+     */
+    reason?: string;
+    ext?: Ext;
+}
+/**
+ * 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.
+ */
+export interface Ext {
+    [k: string]: unknown | undefined;
+}
+/**
+ * The issued credential. Returned only where the issuing member agreed; a decline is a trust-task-error, not a response with an empty field.
+ */
+export interface VTCRelationshipsRequestResponsePayload {
+    /**
+     * A signed W3C Verifiable Relationship Credential (opaque here). Its issuer MUST be the issuing member — the party that signed this response — and its credentialSubject.id MUST name the requester. The same shape `vtc/relationships/publish` accepts, so a requester can lodge it with the community unchanged.
+     */
+    vrc: {};
+    /**
+     * SHA-256 of the returned VRC, for out-of-band integrity checks. Matches the digest `vtc/relationships/publish` reports once the credential is lodged, so the two can be tied together without re-hashing.
+     */
+    vrcSha256?: string;
+    ext?: Ext;
+}
+/** Trust Task type URI. */
+export declare const TYPE_URI: "https://trusttasks.org/spec/vtc/relationships/request/0.1";
+/** Stable alias for this specification's request payload shape. */
+export type Payload = VTCRelationshipsRequestPayload;
+/** Trust Task response type URI (request type URI + "#response"). */
+export declare const RESPONSE_TYPE_URI: "https://trusttasks.org/spec/vtc/relationships/request/0.1#response";
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = VTCRelationshipsRequestResponsePayload;
+/**
+ * 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.
+ */
+export declare const SPEC: {
+    readonly typeUri: "https://trusttasks.org/spec/vtc/relationships/request/0.1";
+    readonly isBearer: false;
+    readonly isProofRequired: true;
+    readonly isRecipientRequired: true;
+};
+/**
+ * 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 declare const RESPONSE_SPEC: {
+    readonly typeUri: "https://trusttasks.org/spec/vtc/relationships/request/0.1#response";
+    readonly isBearer: false;
+    readonly isProofRequired: true;
+    readonly isRecipientRequired: true;
+};
+//# sourceMappingURL=payload.d.ts.map

package/dist/vtc/relationships/request/0.1/payload.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"payload.d.ts","sourceRoot":"","sources":["../../../../../src/vtc/relationships/request/0.1/payload.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH;;GAEG;AACH,MAAM,WAAW,8BAA8B;IAC7C;;OAEG;IACH,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,GAAG,CAAC,EAAE,GAAG,CAAC;CACX;AACD;;GAEG;AACH,MAAM,WAAW,GAAG;IAClB,CAAC,CAAC,EAAE,MAAM,GAAG,OAAO,GAAG,SAAS,CAAC;CAClC;AACD;;GAEG;AACH,MAAM,WAAW,sCAAsC;IACrD;;OAEG;IACH,GAAG,EAAE,EAAE,CAAC;IACR;;OAEG;IACH,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,GAAG,CAAC,EAAE,GAAG,CAAC;CACX;AAED,2BAA2B;AAC3B,eAAO,MAAM,QAAQ,EAAG,2DAAoE,CAAC;AAE7F,mEAAmE;AACnE,MAAM,MAAM,OAAO,GAAG,8BAA8B,CAAC;AAErD,qEAAqE;AACrE,eAAO,MAAM,iBAAiB,EAAG,oEAA6E,CAAC;AAE/G,4EAA4E;AAC5E,MAAM,MAAM,QAAQ,GAAG,sCAAsC,CAAC;AAE9D;;;;GAIG;AACH,eAAO,MAAM,IAAI;;;;;CAKP,CAAC;AAEX;;;;GAIG;AACH,eAAO,MAAM,aAAa;;;;;CAKhB,CAAC"}

package/dist/vtc/relationships/request/0.1/payload.js

@@ -0,0 +1,31 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vtc/relationships/request/0.1/payload.schema.json
+ */
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/vtc/relationships/request/0.1";
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/vtc/relationships/request/0.1#response";
+/**
+ * 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.
+ */
+export const SPEC = {
+    typeUri: TYPE_URI,
+    isBearer: false,
+    isProofRequired: true,
+    isRecipientRequired: true,
+};
+/**
+ * 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,
+};
+//# sourceMappingURL=payload.js.map

package/dist/vtc/relationships/request/0.1/payload.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"payload.js","sourceRoot":"","sources":["../../../../../src/vtc/relationships/request/0.1/payload.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAiCH,2BAA2B;AAC3B,MAAM,CAAC,MAAM,QAAQ,GAAG,2DAAoE,CAAC;AAK7F,qEAAqE;AACrE,MAAM,CAAC,MAAM,iBAAiB,GAAG,oEAA6E,CAAC;AAK/G;;;;GAIG;AACH,MAAM,CAAC,MAAM,IAAI,GAAG;IAClB,OAAO,EAAE,QAAQ;IACjB,QAAQ,EAAE,KAAK;IACf,eAAe,EAAE,IAAI;IACrB,mBAAmB,EAAE,IAAI;CACjB,CAAC;AAEX;;;;GAIG;AACH,MAAM,CAAC,MAAM,aAAa,GAAG;IAC3B,OAAO,EAAE,iBAAiB;IAC1B,QAAQ,EAAE,KAAK;IACf,eAAe,EAAE,IAAI;IACrB,mBAAmB,EAAE,IAAI;CACjB,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openvtc/trust-tasks",
-  "version": "0.2.60",
+  "version": "0.4.0",
   "description": "Generated TypeScript bindings for the Trust Tasks framework registry.",
   "type": "module",
   "main": "./dist/index.js",

package/src/_framework/0.3/framework.ts

@@ -0,0 +1,13 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/_framework/0.3/framework.schema.json
+ */
+
+/**
+ * Reusable $defs cross-referenced by individual Trust Task specifications. Not itself a Trust Task specification — the `_framework` directory is skipped by the registry build (folders starting with `_` are not discovered) and by the codegen (which only triggers on payload.schema.json). See SPEC.md §4.5.1 for the normative description of `ext`.
+ *
+ * Additive over 0.2: `Ext` is carried forward unchanged, and `DigestMultibase` is new. Specifications pinned to 0.2 remain valid; a draft specification re-pinning to 0.3 does so in place, errata-style, per SPEC.md §5.2 — the re-pin does not change any payload's effective wire shape.
+ */
+export interface TrustTasksFrameworkReusableJSONSchemaDefinitions {
+  [k: string]: unknown | undefined;
+}

package/src/_runtime/document.ts

@@ -5,7 +5,7 @@
  * Hand-written. Mirrors `document.rs` in trust-tasks-rs.
  */
 
-import type { StandardCode } from "./codes.js";
+import { normalizeCode, type StandardCode } from "./codes.js";
 
 /** A W3C Data Integrity Proof object (SPEC.md §4.7). Opaque to the framework. */
 export interface Proof {
@@ -24,6 +24,17 @@ export interface TrustTaskDocument<P> {
   id: string;
   /** Correlates this document with others in the same exchange (§4.9). */
   threadId?: string;
+  /**
+   * The `threadId` of the exchange containing this one, where this exchange is
+   * conducted inside another (§4.9.2).
+   *
+   * A navigation aid. It records one level of containment and does **not**
+   * change which exchange attests an event — §4.9.1 governs that, and holds
+   * whether or not this member is present. Like `threadId` it carries no
+   * normative validation semantics: a consumer MUST NOT reject a document on
+   * the basis of `parentThreadId` alone.
+   */
+  parentThreadId?: string;
   /** The Type URI identifying specification and version (§4.4). */
   type: string;
   /** VID of the party responsible for the content (§4.8). */
@@ -43,9 +54,37 @@ export interface TrustTaskDocument<P> {
   [k: string]: unknown;
 }
 
+/** Names the Trust Task document an {@link ErrorPayload} reports on (§8.2). */
+export interface InResponseTo {
+  /**
+   * The reported-on document's `type`, including any `#request` / `#response`
+   * fragment — that fragment is what tells a consumer which variant's semantics
+   * apply.
+   */
+  typeUri: string;
+  /**
+   * The reported-on document's `id`. Globally unique and never reused (§4.3),
+   * so it names one instance where `threadId` names an exchange.
+   *
+   * Omitted under `identityMismatch`: per §8.1 the response goes to the
+   * transport-authenticated sender rather than the in-band `issuer`, and that
+   * party did not necessarily compose the document.
+   */
+  id?: string;
+}
+
 /** The `payload` of an error response (SPEC.md §8.2). */
 export interface ErrorPayload {
   code: string;
+  /**
+   * Identifies the document this error reports on (§8.2).
+   *
+   * `threadId` correlates the exchange for a party that saw the request and
+   * identifies nothing to anyone else, so without this a retained error names
+   * neither the specification the failure occurred under nor the instance. The
+   * builders below populate it.
+   */
+  inResponseTo?: InResponseTo;
   message?: string;
   retryable: boolean;
   retryAfter?: string;
@@ -81,8 +120,15 @@ export interface RejectReason {
   details?: Record<string, unknown>;
 }
 
-/** The Type URI a consumer emits error responses under. */
-export const TRUST_TASK_ERROR_TYPE_URI = "https://trusttasks.org/spec/trust-task-error/0.2";
+/**
+ * The Type URI a consumer emits error responses under.
+ *
+ * `0.3`, because this runtime populates the `inResponseTo` member of §8.2 and
+ * `0.2`'s payload schema is `additionalProperties: false` — a document carrying
+ * it would not validate as `0.2`. Per §5.2 forward-minor compatibility a `0.2`
+ * consumer SHOULD accept it.
+ */
+export const TRUST_TASK_ERROR_TYPE_URI = "https://trusttasks.org/spec/trust-task-error/0.3";
 
 /**
  * SPEC §7.2 items 4 and 5a — expiry and wrong-recipient.
@@ -194,7 +240,23 @@ export function rejectWithRecipient<P>(
   recipient: string | undefined,
   now: () => string = () => new Date().toISOString(),
 ): ErrorResponse {
-  return {
+  // §8.2 — name the document this error reports on, so it means something to a
+  // party that did not see the request. Filled here rather than left to the
+  // caller because the builder is the only place that reliably has the
+  // originating document in hand; a caller-supplied value is kept.
+  const withOrigin: ErrorPayload = { ...payload };
+  if (withOrigin.inResponseTo === undefined) {
+    const about: InResponseTo = { typeUri: request.type };
+    // §8.1/§8.2 — under identityMismatch the response is addressed to the
+    // transport-authenticated sender, not the in-band issuer. That party did
+    // not necessarily compose the document, so its id is not echoed back.
+    if (normalizeCode(payload.code) !== "identityMismatch") {
+      about.id = request.id;
+    }
+    withOrigin.inResponseTo = about;
+  }
+
+  const response: ErrorResponse = {
     id,
     // §4.9: continue the thread, falling back to the request's own id.
     threadId: request.threadId ?? request.id,
@@ -202,8 +264,15 @@ export function rejectWithRecipient<P>(
     issuer: request.recipient,
     recipient,
     issuedAt: now(),
-    payload,
+    payload: withOrigin,
   };
+  // §4.9.2 — the whole exchange shares one parent, so the error response stays
+  // inside the same enclosing exchange. Assigned conditionally so an absent
+  // parent does not become an explicit `undefined` on the wire.
+  if (request.parentThreadId !== undefined) {
+    response.parentThreadId = request.parentThreadId;
+  }
+  return response;
 }
 
 /**
@@ -247,7 +316,7 @@ export function respondWith<P, R>(
   now: () => string = () => new Date().toISOString(),
 ): TrustTaskDocument<R> {
   const bare = request.type.split("#")[0]!;
-  return {
+  const response: TrustTaskDocument<R> = {
     id,
     threadId: request.threadId ?? request.id,
     type: `${bare}#response`,
@@ -256,4 +325,9 @@ export function respondWith<P, R>(
     issuedAt: now(),
     payload,
   };
+  // §4.9.2 — the whole exchange shares one parent.
+  if (request.parentThreadId !== undefined) {
+    response.parentThreadId = request.parentThreadId;
+  }
+  return response;
 }

package/src/_runtime/index.ts

@@ -21,6 +21,7 @@ export {
   validateBasic,
   type ErrorPayload,
   type ErrorResponse,
+  type InResponseTo,
   type Proof,
   type RejectReason,
   type SpecPolicy,

package/src/audit/list/0.1/payload.ts

@@ -3,6 +3,15 @@
  * Source: specs/audit/list/0.1/payload.schema.json
  */
 
+/**
+ * Hash-chain link: the `entryHash` of the immediately-preceding entry. Present only on chained logs; its integrity is what audit/verify checks. Multibase-encoded multihash over the RFC 8785 (JCS) canonicalization of the predecessor's immutable content — the same derivation as `entryHash`, so a verifier recomputes both the same way.
+ */
+export type DigestMultibase = string;
+/**
+ * Hash-chain commitment over this entry's immutable content. The next entry's `prevHash` points here. Multibase-encoded multihash over the RFC 8785 (JCS) canonicalization of that content; the canonicalization is what makes the commitment reproducible by a verifier that did not write the entry.
+ */
+export type DigestMultibase1 = string;
+
 export interface AuditListPayload {
   /**
    * Return only entries recorded at or after this time.
@@ -95,14 +104,8 @@ export interface AuditEnvelope {
    * Envelope-shape version at the maintainer, for consumers that need to reason about wire-shape evolution.
    */
   schemaVersion?: number;
-  /**
-   * Hash-chain link: the `entryHash` of the immediately-preceding entry. Present only on chained logs; its integrity is what audit/verify checks.
-   */
-  prevHash?: string;
-  /**
-   * Hash-chain commitment over this entry's immutable content. The next entry's `prevHash` points here.
-   */
-  entryHash?: string;
+  prevHash?: DigestMultibase;
+  entryHash?: DigestMultibase1;
   /**
    * Event-specific payload, keyed by `action`. Opaque to the framework; a consumer that does not recognise the action treats it as an unstructured record.
    */
@@ -116,7 +119,7 @@ export interface AuditEnvelope {
 export const TYPE_URI = "https://trusttasks.org/spec/audit/list/0.1" as const;
 
 /** Stable alias for this specification's request payload shape. */
-export type Payload = AuditListPayload;
+export type Payload = DigestMultibase;
 
 /** Trust Task response type URI (request type URI + "#response"). */
 export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/audit/list/0.1#response" as const;

package/src/audit/verify/0.1/payload.ts

@@ -3,6 +3,11 @@
  * Source: specs/audit/verify/0.1/payload.schema.json
  */
 
+/**
+ * The `entryHash` of the newest envelope reached, in the same multibase-multihash encoding the envelope carries it. Absent when the log is empty.
+ */
+export type DigestMultibase = string;
+
 /**
  * Request to verify the integrity of a maintainer's append-only audit hash chain. The request carries no parameters — verification is store-wide.
  */
@@ -39,10 +44,7 @@ export interface AuditVerifyResponsePayload {
    * Envelopes that could not be deserialized and so could not be checked. Reported at the same prominence as a break, not swallowed.
    */
   unparseableSkipped: number;
-  /**
-   * Hex `entryHash` of the newest envelope reached. Absent when the log is empty.
-   */
-  head?: string;
+  head?: DigestMultibase;
   chainBreak?: ChainBreak;
   ext?: Ext;
 }
@@ -68,7 +70,7 @@ export interface ChainBreak {
 export const TYPE_URI = "https://trusttasks.org/spec/audit/verify/0.1" as const;
 
 /** Stable alias for this specification's request payload shape. */
-export type Payload = AuditVerifyPayload;
+export type Payload = DigestMultibase;
 
 /** Trust Task response type URI (request type URI + "#response"). */
 export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/audit/verify/0.1#response" as const;

package/src/chat/message/0.1/payload.ts

@@ -3,6 +3,15 @@
  * Source: specs/chat/message/0.1/payload.schema.json
  */
 
+/**
+ * OPTIONAL. Multibase-encoded multihash over the attachment bytes, so the reference is itself verifiable and tamper-evident. Taken over the bytes as transferred, not over any JSON wrapper.
+ */
+export type DigestMultibase = string;
+/**
+ * Multibase-encoded multihash over the RFC 8785 (JCS) canonicalization of the previous document, so a gap, reorder, or removal in the chain is detectable. The algorithm travels in the multihash rather than being fixed here.
+ */
+export type DigestMultibase1 = string;
+
 /**
  * A conversational message exchanged between an AI agent and a messaging-platform bridge. Signed by its author (via the document `proof`) and hash-linked to the previous message in the conversation (`prev`), so a third party can verify each message's author and ordering after the transport has closed — for audit and dispute resolution. Conversations and contacts are referenced by opaque, bridge-issued handles, never raw platform addresses.
  */
@@ -85,10 +94,7 @@ export interface AttachmentRef {
    * OPTIONAL. Size in bytes, if known ahead of fetch.
    */
   sizeBytes?: number;
-  /**
-   * OPTIONAL. Multihash digest of the attachment bytes, so the reference is itself verifiable and tamper-evident.
-   */
-  digest?: string;
+  digest?: DigestMultibase;
 }
 /**
  * OPTIONAL on the first message in a conversation; present on every message thereafter. Links to the previous message so the conversation forms a verifiable, ordered chain.
@@ -98,10 +104,7 @@ export interface ChainLink {
    * The `id` of the previous `chat/message` Trust Task document in this conversation.
    */
   id: string;
-  /**
-   * Multihash digest (e.g. `sha-256`) over the previous document, so a gap, reorder, or removal in the chain is detectable.
-   */
-  digest: string;
+  digest: DigestMultibase1;
 }
 /**
  * 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.
@@ -114,7 +117,7 @@ export interface Ext {
 export const TYPE_URI = "https://trusttasks.org/spec/chat/message/0.1" as const;
 
 /** Stable alias for this specification's request payload shape. */
-export type Payload = ChatMessagePayload;
+export type Payload = DigestMultibase;
 
 /**
  * SPEC.md §7.2 policy for the request variant, from this specification's

package/src/consent/request/1.0/payload.ts

@@ -3,6 +3,11 @@
  * Source: specs/consent/request/1.0/payload.schema.json
  */
 
+/**
+ * Optional multibase-encoded multihash over the rfc 8785 (jcs) canonicalization of the held first message, binding the request to concrete content.
+ */
+export type DigestMultibase = string;
+
 /**
  * A bridge asks the VTA whether an inbound conversation may reach an AI agent, prompting operator consent on first contact.
  */
@@ -20,10 +25,7 @@ export interface ConsentRequestPayload {
    * Optional operator-facing label (e.g. "Signal group 'Family'"). MUST NOT contain a raw platform address.
    */
   displayHint?: string;
-  /**
-   * Optional multihash digest of the held first message, binding the request to concrete content.
-   */
-  firstMessageDigest?: string;
+  firstMessageDigest?: DigestMultibase;
   /**
    * Optional VTA context path the bridge runs under, to scope approver resolution.
    */
@@ -80,7 +82,7 @@ export interface ConsentRequestResponsePayload {
 export const TYPE_URI = "https://trusttasks.org/spec/consent/request/1.0" as const;
 
 /** Stable alias for this specification's request payload shape. */
-export type Payload = ConsentRequestPayload;
+export type Payload = DigestMultibase;
 
 /** Trust Task response type URI (request type URI + "#response"). */
 export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/consent/request/1.0#response" as const;

package/src/credentials/_shared/0.2/credentials.ts

@@ -0,0 +1,15 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/credentials/_shared/0.2/credentials.schema.json
+ */
+
+/**
+ * The credential-minting core shared by every family that issues or revokes a Verifiable Credential (vta/credentials/*, vtc/endorsements/*, and future issuers). A family embeds these definitions rather than restating them, so the issuance receipt and the revocation receipt have one canonical shape across the registry. Families remain separate Trust Tasks because their trust semantics differ (approval plane, third-party verifiability, governance gating); only the mechanism is shared.
+ *
+ * Two levels of reuse are offered. A family whose response IS a receipt embeds `IssuedCredential` / `RevocationReceipt` whole, as vtc/endorsements does. A family whose response carries additional members alongside the receipt fields cannot do that — these definitions are `additionalProperties: false`, so composing one via `allOf` would reject the extra members — and instead references `CredentialId`, the identifier both receipts are keyed by, as vta/credentials does.
+ *
+ * `CredentialId` is hoisted and the other members are not, deliberately: it is the one field carrying a constraint worth stating once (non-empty), and the code generators mint a named type per `$def`, so hoisting a plain timestamp or the opaque credential object would wrap `expiresAt` and `credential` in newtypes for every consumer while deduplicating nothing but a description.
+ */
+export interface CredentialsSharedIssuanceAndRevocationDefinitions {
+  [k: string]: unknown | undefined;
+}

package/src/index.ts

@@ -7,6 +7,7 @@ export * from "./_runtime/index.js";
 
 export * as FrameworkShared_v0_1 from "./_framework/0.1/framework.js";
 export * as FrameworkShared_v0_2 from "./_framework/0.2/framework.js";
+export * as FrameworkShared_v0_3 from "./_framework/0.3/framework.js";
 export * as AclEntryShared_v0_1 from "./acl/_shared/0.1/acl-entry.js";
 export * as AclChangeRole_v0_1 from "./acl/change-role/0.1/payload.js";
 export * as AclGrant_v0_1 from "./acl/grant/0.1/payload.js";
@@ -70,6 +71,7 @@ export * as CredentialExchangePresent_v0_1 from "./credential-exchange/present/0
 export * as CredentialExchangeQuery_v0_1 from "./credential-exchange/query/0.1/payload.js";
 export * as CredentialExchangeRequest_v0_1 from "./credential-exchange/request/0.1/payload.js";
 export * as CredentialsShared_v0_1 from "./credentials/_shared/0.1/credentials.js";
+export * as CredentialsShared_v0_2 from "./credentials/_shared/0.2/credentials.js";
 export * as DeviceBindingShared_v0_1 from "./device/_shared/0.1/device-binding.js";
 export * as DeviceBindingShared_v0_2 from "./device/_shared/0.2/device-binding.js";
 export * as DeviceDisable_v0_1 from "./device/disable/0.1/payload.js";
@@ -204,6 +206,7 @@ export * as TaskConsentRequest_v0_1 from "./task-consent/request/0.1/payload.js"
 export * as TrustTaskDiscovery_v0_1 from "./trust-task-discovery/0.1/payload.js";
 export * as TrustTaskError_v0_1 from "./trust-task-error/0.1/payload.js";
 export * as TrustTaskError_v0_2 from "./trust-task-error/0.2/payload.js";
+export * as TrustTaskError_v0_3 from "./trust-task-error/0.3/payload.js";
 export * as ConsumerContextShared_v0_1 from "./vault/_shared/0.1/consumer-context.js";
 export * as SealedEnvelopeShared_v0_1 from "./vault/_shared/0.1/sealed-envelope.js";
 export * as SessionBlobShared_v0_1 from "./vault/_shared/0.1/session-blob.js";
@@ -240,6 +243,7 @@ export * as VtaContextsDidTemplatesList_v1_0 from "./vta/contexts/did-templates/
 export * as VtaContextsDidTemplatesRender_v1_0 from "./vta/contexts/did-templates/render/1.0/payload.js";
 export * as VtaContextsDidTemplatesUpdate_v1_0 from "./vta/contexts/did-templates/update/1.0/payload.js";
 export * as VtaCredentialsIssue_v0_1 from "./vta/credentials/issue/0.1/payload.js";
+export * as VtaCredentialsIssue_v0_2 from "./vta/credentials/issue/0.2/payload.js";
 export * as VtaCredentialsRevoke_v0_1 from "./vta/credentials/revoke/0.1/payload.js";
 export * as VtaDidTemplatesCreate_v1_0 from "./vta/did-templates/create/1.0/payload.js";
 export * as VtaDidTemplatesCreate_v2_0 from "./vta/did-templates/create/2.0/payload.js";
@@ -331,6 +335,7 @@ export * as VtcRegistryDiagnostics_v0_1 from "./vtc/registry/diagnostics/0.1/pay
 export * as VtcRelationshipsGraph_v0_1 from "./vtc/relationships/graph/0.1/payload.js";
 export * as VtcRelationshipsList_v0_1 from "./vtc/relationships/list/0.1/payload.js";
 export * as VtcRelationshipsPublish_v0_1 from "./vtc/relationships/publish/0.1/payload.js";
+export * as VtcRelationshipsRequest_v0_1 from "./vtc/relationships/request/0.1/payload.js";
 export * as VtcRelationshipsRevoke_v0_1 from "./vtc/relationships/revoke/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";

package/src/policy/evaluate/0.3/payload.ts

@@ -3,6 +3,10 @@
  * Source: specs/policy/evaluate/0.3/payload.schema.json
  */
 
+/**
+ * Multibase-encoded multihash over the RFC 8785 (JCS) canonicalization of the payload, salted with the request challenge, present when a delegated-execution consent flow must bind approval to this exact payload. Absent when no consent binding is in play.
+ */
+export type DigestMultibase = string;
 /**
  * A single binding target for a vault entry. Tagged union over the discriminator `kind`. A VaultEntry's `targets` array MAY mix any number of these.
  */
@@ -42,10 +46,7 @@ export interface PolicyInput {
      * The identifier the task acts on — the value at the spec's `subjectPath` (usually a DID). The evaluator checks the consumer's authority to act on this subject. Absent for subjectless tasks (discovery, list).
      */
     subject?: string;
-    /**
-     * Multihash of the canonicalized payload, salted with the request challenge, present when a delegated-execution consent flow must bind approval to this exact payload. Absent when no consent binding is in play.
-     */
-    payloadDigest?: string;
+    payloadDigest?: DigestMultibase;
     /**
      * Authoritative integrity class (SPEC §7.3 item 13). The evaluator MUST derive this from the compiled handler it is about to invoke, not from the wire — the registry's declared value is advisory only.
      */
@@ -176,7 +177,7 @@ export interface PolicyDecision {
 export const TYPE_URI = "https://trusttasks.org/spec/policy/evaluate/0.3" as const;
 
 /** Stable alias for this specification's request payload shape. */
-export type Payload = SiteTarget;
+export type Payload = DigestMultibase;
 
 /** Trust Task response type URI (request type URI + "#response"). */
 export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/policy/evaluate/0.3#response" as const;

package/src/task-consent/decision/0.1/payload.ts

@@ -3,10 +3,18 @@
  * Source: specs/task-consent/decision/0.1/payload.schema.json
  */
 
+/**
+ * Echoes the digest of the task being authorized, in the encoding `task-consent/request` carried it. The executor re-derives it from the payload it is about to execute and refuses on mismatch — this is what makes the approved payload the executed payload, cryptographically rather than by convention.
+ */
+export type DigestMultibase = string;
 /**
  * The approver's answer. `deny` aborts the pending request; a subsequent submit of the same task starts a fresh one.
  */
 export type Decision = "approve" | "deny";
+/**
+ * The digest this decision concerned, in the encoding `task-consent/request` carried it.
+ */
+export type DigestMultibase1 = string;
 
 /**
  * An enrolled approver authorizes (or refuses) one pending privileged task, bound to the exact payload it was shown. The proof on this document — not the transport session that carried it — is the authorization.
@@ -16,10 +24,7 @@ export interface TaskConsentDecisionPayload {
    * Echoes the task-consent/request this decision answers, binding it to that one pending request. An executor MUST consume the challenge at execution rather than on receipt of this decision: a decision authorizes exactly one execution, and consuming it earlier lets an executor's own retry legitimately replay it.
    */
   challenge: string;
-  /**
-   * Echoes the digest of the task being authorized. The executor re-derives it from the payload it is about to execute and refuses on mismatch — this is what makes the approved payload the executed payload, cryptographically rather than by convention.
-   */
-  payloadDigest: string;
+  payloadDigest: DigestMultibase;
   decision: Decision;
   /**
    * OPTIONAL human-facing note, most useful on a `deny`.
@@ -41,10 +46,7 @@ export interface TaskConsentDecisionResponsePayload {
    * `granted` = the threshold is met and the requester's re-submit will now execute. `pending` = the approval was recorded but more are needed. `denied` = the request was aborted.
    */
   status: "granted" | "pending" | "denied";
-  /**
-   * The digest this decision concerned.
-   */
-  payloadDigest: string;
+  payloadDigest: DigestMultibase1;
   /**
    * Distinct approvals recorded so far.
    */
@@ -60,7 +62,7 @@ export interface TaskConsentDecisionResponsePayload {
 export const TYPE_URI = "https://trusttasks.org/spec/task-consent/decision/0.1" as const;
 
 /** Stable alias for this specification's request payload shape. */
-export type Payload = Decision;
+export type Payload = DigestMultibase;
 
 /** Trust Task response type URI (request type URI + "#response"). */
 export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/task-consent/decision/0.1#response" as const;

package/src/task-consent/granted/0.1/payload.ts

@@ -3,6 +3,11 @@
  * Source: specs/task-consent/granted/0.1/payload.schema.json
  */
 
+/**
+ * The salted wire digest of the approved task — the same value the matching task-consent/request carried and the decision echoed. The requester already holds it; it is repeated here only so the requester can correlate the notice to the pending task it should now re-submit. It confers nothing: the executor's single-use grant lookup at re-submit is the authorization.
+ */
+export type DigestMultibase = string;
+
 /**
  * Fire-and-forget notice from the executor to the requester that its pending task has reached the approval threshold and a single-use grant is waiting, so the requester re-submits at once instead of polling. Non-load-bearing by design: the grant check at re-submit is the real gate, so a lost or spurious notice costs at most one poll cycle.
  */
@@ -11,10 +16,7 @@ export interface TaskConsentGrantedPayload {
    * Always `granted`. A denial sends no notice — the requester's re-submit discovers it, and a notice that could carry a denial would tempt a consumer into treating this advisory channel as the authoritative outcome, which it is not.
    */
   status: "granted";
-  /**
-   * The salted wire digest of the approved task — the same value the matching task-consent/request carried and the decision echoed. The requester already holds it; it is repeated here only so the requester can correlate the notice to the pending task it should now re-submit. It confers nothing: the executor's single-use grant lookup at re-submit is the authorization.
-   */
-  payloadDigest: string;
+  payloadDigest: DigestMultibase;
   /**
    * Type URI of the approved task, for correlation and display at the requester. Advisory on the same terms as the digest — the executor re-derives everything it enforces from the re-submitted payload itself.
    */
@@ -32,7 +34,7 @@ export interface Ext {
 export const TYPE_URI = "https://trusttasks.org/spec/task-consent/granted/0.1" as const;
 
 /** Stable alias for this specification's request payload shape. */
-export type Payload = TaskConsentGrantedPayload;
+export type Payload = DigestMultibase;
 
 /**
  * SPEC.md §7.2 policy for the request variant, from this specification's

package/src/task-consent/request/0.1/payload.ts

@@ -3,6 +3,11 @@
  * Source: specs/task-consent/request/0.1/payload.schema.json
  */
 
+/**
+ * The binding between what the approver sees and what executes. Multibase-encoded multihash over the RFC 8785 (JCS) canonicalization of the payload, the task type, and the `challenge` as salt. The decision echoes it; the executor re-derives it from the payload it is about to run and refuses on mismatch. Salted because an unsalted digest over a low-entropy payload is a confirmation oracle for anyone who observes it in transit.
+ */
+export type DigestMultibase = string;
+
 /**
  * The executor asks an enrolled approver device to authorize one pending privileged task, presenting the effects it computed by dry-running the real handler against its own prior state. The executor signs this document; the approver renders only what it verifies under that signature.
  */
@@ -15,10 +20,7 @@ export interface TaskConsentRequestPayload {
    * Type URI of the task awaiting approval. It is bound into `payloadDigest`: without that binding, two tasks whose payloads canonicalize identically would share a digest, and an approval for a benign task would authorize a destructive one.
    */
   taskType: string;
-  /**
-   * The binding between what the approver sees and what executes. Digest of the canonical (RFC 8785 JCS) payload, the task type, and the `challenge` as salt. The decision echoes it; the executor re-derives it from the payload it is about to run and refuses on mismatch. Salted because an unsalted digest over a low-entropy payload is a confirmation oracle for anyone who observes it in transit.
-   */
-  payloadDigest: string;
+  payloadDigest: DigestMultibase;
   /**
    * Authoritative SPEC §7.3 item 13 side-effect class of the pending task, derived by the executor from the compiled handler it is about to invoke. NEVER taken from the registry: a registry that decided this would be a consent kill-switch, downgradeable by publishing a new version with a weaker class.
    */
@@ -157,7 +159,7 @@ export interface TaskConsentRequestResponsePayload {
 export const TYPE_URI = "https://trusttasks.org/spec/task-consent/request/0.1" as const;
 
 /** Stable alias for this specification's request payload shape. */
-export type Payload = TaskConsentRequestPayload;
+export type Payload = DigestMultibase;
 
 /** Trust Task response type URI (request type URI + "#response"). */
 export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/task-consent/request/0.1#response" as const;