@openvtc/trust-tasks 0.14.2 → 0.15.0

package/src/vtc/relationships/publish/0.2/payload.ts

@@ -3,14 +3,8 @@
  * Source: specs/vtc/relationships/publish/0.2/payload.schema.json
  */
 
-/**
- * Digest over the RFC 8785 canonicalization of the VRC this authorizes. Binds the authorization to one credential, so it cannot be moved to another.
- */
-export type DigestMultibase = string;
-/**
- * Digest over the RFC 8785 canonicalization of the stored VRC, for out-of-band integrity checks. The same value vtc/relationships/request reports on issuance and vtc/relationships/list reports per entry, so a member can tie the three together without re-hashing.
- */
-export type DigestMultibase1 = string;
+import type { DigestMultibase, Ext } from "../../../../_shared/components.js";
+
 
 export interface VTCRelationshipsPublishPayload {
   /**
@@ -33,6 +27,9 @@ export interface VTCRelationshipsPublishPayload {
      * The `id` of the Trust Task document carrying this authorization. Binds the authorization to one document, so a captured one cannot be replayed in another — including by a different member. Every document carries a unique `id` (SPEC §4.3), which is why the binding needs no transport-specific notion of a session.
      */
     documentId: string;
+    /**
+     * Digest over the RFC 8785 canonicalization of the VRC this authorizes. Binds the authorization to one credential, so it cannot be moved to another.
+     */
     vrcDigestMultibase: DigestMultibase;
     /**
      * Data-integrity proof over this object, by a verification method the VRC's `issuer` controls. This is the proof of possession; the members above only bound what it authorizes.
@@ -41,12 +38,6 @@ export interface VTCRelationshipsPublishPayload {
   };
   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;
-}
 export interface VTCRelationshipsPublishResponsePayload {
   /**
    * Id assigned to the stored relationship (a UUID).
@@ -54,10 +45,16 @@ export interface VTCRelationshipsPublishResponsePayload {
   id: string;
   issuerDid: string;
   subjectDid: string;
-  vrcDigestMultibase: DigestMultibase1;
+  /**
+   * Digest over the RFC 8785 canonicalization of the stored VRC, for out-of-band integrity checks. The same value vtc/relationships/request reports on issuance and vtc/relationships/list reports per entry, so a member can tie the three together without re-hashing.
+   */
+  vrcDigestMultibase: DigestMultibase;
   ext?: Ext;
 }
 
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { DigestMultibase, Ext };
+
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/vtc/relationships/publish/0.2" as const;
 

package/src/vtc/relationships/request/0.1/payload.ts

@@ -3,6 +3,9 @@
  * Source: specs/vtc/relationships/request/0.1/payload.schema.json
  */
 
+import type { Ext } from "../../../../_shared/components.js";
+
+
 /**
  * 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.
  */
@@ -13,12 +16,6 @@ export interface VTCRelationshipsRequestPayload {
   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.
  */
@@ -34,6 +31,9 @@ export interface VTCRelationshipsRequestResponsePayload {
   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/vtc/relationships/request/0.1" as const;
 

package/src/vtc/relationships/request/0.2/payload.ts

@@ -3,10 +3,8 @@
  * Source: specs/vtc/relationships/request/0.2/payload.schema.json
  */
 
-/**
- * Digest over the RFC 8785 canonicalization 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 — which requires both ends to canonicalize the same way, and is why the canonicalization is named here rather than assumed.
- */
-export type DigestMultibase = string;
+import type { DigestMultibase, Ext } from "../../../../_shared/components.js";
+
 
 /**
  * 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.
@@ -18,12 +16,6 @@ export interface VTCRelationshipsRequestPayload {
   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.
  */
@@ -32,10 +24,16 @@ 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: {};
+  /**
+   * Digest over the RFC 8785 canonicalization 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 — which requires both ends to canonicalize the same way, and is why the canonicalization is named here rather than assumed.
+   */
   vrcDigestMultibase?: DigestMultibase;
   ext?: Ext;
 }
 
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { DigestMultibase, Ext };
+
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/vtc/relationships/request/0.2" as const;
 

package/src/vtc/relationships/revoke/0.1/payload.ts

@@ -3,6 +3,9 @@
  * Source: specs/vtc/relationships/revoke/0.1/payload.schema.json
  */
 
+import type { Ext } from "../../../../_shared/components.js";
+
+
 export interface VTCRelationshipsRevokePayload {
   /**
    * The relationship to revoke.
@@ -10,17 +13,14 @@ export interface VTCRelationshipsRevokePayload {
   id: 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;
-}
 export interface VTCRelationshipsRevokeResponsePayload {
   id: 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/vtc/relationships/revoke/0.1" as const;
 

package/src/vtc/website/files/delete/0.1/payload.ts

@@ -3,6 +3,9 @@
  * Source: specs/vtc/website/files/delete/0.1/payload.schema.json
  */
 
+import type { Ext } from "../../../../../_shared/components.js";
+
+
 export interface VTCWebsiteFilesDeletePayload {
   /**
    * Path of the file to delete, relative to the site root.
@@ -10,18 +13,15 @@ export interface VTCWebsiteFilesDeletePayload {
   path: 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;
-}
 export interface VTCWebsiteFilesDeleteResponsePayload {
   path: string;
   deleted: boolean;
   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/vtc/website/files/delete/0.1" as const;
 

package/src/vtc/website/files/list/0.1/payload.ts

@@ -3,6 +3,9 @@
  * Source: specs/vtc/website/files/list/0.1/payload.schema.json
  */
 
+import type { Ext } from "../../../../../_shared/components.js";
+
+
 export interface VTCWebsiteFilesListPayload {
   /**
    * Opaque continuation token from a prior page.
@@ -14,12 +17,6 @@ export interface VTCWebsiteFilesListPayload {
   limit?: number;
   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;
-}
 export interface VTCWebsiteFilesListResponsePayload {
   /**
    * Files under the site root, excluding hidden files and blocklisted extensions.
@@ -43,6 +40,9 @@ export interface VTCWebsiteFilesListResponsePayload {
   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/vtc/website/files/list/0.1" as const;
 

package/src/vtc/website/generations/list/0.1/payload.ts

@@ -3,15 +3,12 @@
  * Source: specs/vtc/website/generations/list/0.1/payload.schema.json
  */
 
+import type { Ext } from "../../../../../_shared/components.js";
+
+
 export interface VTCWebsiteGenerationsListPayload {
   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;
-}
 export interface VTCWebsiteGenerationsListResponsePayload {
   generations: {
     /**
@@ -34,6 +31,9 @@ export interface VTCWebsiteGenerationsListResponsePayload {
   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/vtc/website/generations/list/0.1" as const;
 

package/src/vtc/website/rollback/0.1/payload.ts

@@ -3,6 +3,9 @@
  * Source: specs/vtc/website/rollback/0.1/payload.schema.json
  */
 
+import type { Ext } from "../../../../_shared/components.js";
+
+
 export interface VTCWebsiteRollbackPayload {
   /**
    * The past generation to make current (e.g. gen-3).
@@ -10,12 +13,6 @@ export interface VTCWebsiteRollbackPayload {
   generation: 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;
-}
 export interface VTCWebsiteRollbackResponsePayload {
   generation: string;
   /**
@@ -29,6 +26,9 @@ export interface VTCWebsiteRollbackResponsePayload {
   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/vtc/website/rollback/0.1" as const;
 

package/src/webvh/sync/delete/0.1/payload.ts

@@ -3,22 +3,22 @@
  * Source: specs/webvh/sync/delete/0.1/payload.schema.json
  */
 
+import type { Ext } from "../../../../_shared/components.js";
+
+
 export interface WebVHSyncDeletePayload {
   mnemonic: 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;
-}
 export interface WebVHSyncDeleteResponsePayload {
   mnemonic: string;
   status: "deleted";
   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/webvh/sync/delete/0.1" as const;
 

package/src/webvh/sync/update/0.1/payload.ts

@@ -3,6 +3,9 @@
  * Source: specs/webvh/sync/update/0.1/payload.schema.json
  */
 
+import type { Ext } from "../../../../_shared/components.js";
+
+
 export interface WebVHSyncUpdatePayload {
   mnemonic: string;
   didId: string;
@@ -11,18 +14,15 @@ export interface WebVHSyncUpdatePayload {
   versionCount: number;
   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;
-}
 export interface WebVHSyncUpdateResponsePayload {
   mnemonic: string;
   status: "applied";
   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/webvh/sync/update/0.1" as const;
 

package/src/webvh/witness/publish/0.1/payload.ts

@@ -3,6 +3,9 @@
  * Source: specs/webvh/witness/publish/0.1/payload.schema.json
  */
 
+import type { Ext } from "../../../../_shared/components.js";
+
+
 export interface WebVHWitnessPublishPayload {
   mnemonic: string;
   /**
@@ -11,18 +14,15 @@ export interface WebVHWitnessPublishPayload {
   witness: {};
   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;
-}
 export interface WebVHWitnessPublishResponsePayload {
   mnemonic: string;
   witnessUrl: 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/webvh/witness/publish/0.1" as const;
 

package/src/witness/session/0.1/payload.ts

@@ -3,6 +3,9 @@
  * Source: specs/witness/session/0.1/payload.schema.json
  */
 
+import type { Ext } from "../../../_shared/components.js";
+
+
 /**
  * Opens one participating party's witness session as its own exchange, nested in a relationship exchange via parentThreadId. A session is bilateral — a witnessed exchange between two parties runs two sessions with the same witness, each naming the same parties pair. The response issues the session challenge; the request document's id is the value that party's VWC later carries as taskContext.
  */
@@ -16,12 +19,6 @@ export interface WitnessSessionPayload {
   parties: [string, 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 session challenge, issued under the REQUIRED proof. The presentation under witness/session/submit binds to {challenge, domain}. It reaches only the party that opened this session — which is why each party opens its own.
  */
@@ -37,6 +34,9 @@ export interface WitnessSessionResponsePayload {
   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/witness/session/0.1" as const;
 

package/src/witness/session/submit/0.1/payload.ts

@@ -3,10 +3,8 @@
  * Source: specs/witness/session/submit/0.1/payload.schema.json
  */
 
-/**
- * Digest over the RFC 8785 canonicalization of the delivered credential, computed by the witness. It binds this evidence to one specific credential rather than to the session alone, so a verifier pairing a presented VWC with this response can check it is the credential this session issued and not another the same witness signed. This covers the credential whole, proof included — unlike the task digest of SPEC.md §4.9.3, which excludes the top-level proof of the Trust Task document it names. The inputs differ because the questions do: this value identifies one delivered artifact, a task digest identifies what a document says whether or not it was signed.
- */
-export type DigestMultibase = string;
+import type { DigestMultibase, Ext } from "../../../../_shared/components.js";
+
 
 /**
  * A participating party submits its presentation bound to its session challenge; the witness's mandatory response delivers the Verifiable Witness Credential and its digest. The response is the outcome evidence a VWC presentation must ship.
@@ -18,12 +16,6 @@ export interface WitnessSessionSubmitPayload {
   vp: {};
   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 Verifiable Witness Credential and its digest, delivered under the REQUIRED proof. This document is the session's terminal success form and the outcome evidence a VWC presentation must ship.
  */
@@ -32,10 +24,16 @@ export interface WitnessSessionSubmitResponsePayload {
    * A signed Verifiable Witness Credential (opaque here; its schema belongs to DTG Core Credentials). Its taskContext MUST equal the id of the witness/session document that opened this session — the innermost exchange that attests the witnessing (SPEC.md §4.9.1) — and its taskDigestMultibase MUST be that document's task digest (SPEC.md §4.9.3). The id locates the session document; the digest binds it, because an id is a name anyone can reuse on a counterfeit.
    */
   vwc: {};
+  /**
+   * Digest over the RFC 8785 canonicalization of the delivered credential, computed by the witness. It binds this evidence to one specific credential rather than to the session alone, so a verifier pairing a presented VWC with this response can check it is the credential this session issued and not another the same witness signed. This covers the credential whole, proof included — unlike the task digest of SPEC.md §4.9.3, which excludes the top-level proof of the Trust Task document it names. The inputs differ because the questions do: this value identifies one delivered artifact, a task digest identifies what a document says whether or not it was signed.
+   */
   vwcDigestMultibase: DigestMultibase;
   ext?: Ext;
 }
 
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { DigestMultibase, Ext };
+
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/witness/session/submit/0.1" as const;