@openvtc/trust-tasks 0.28.12 → 0.28.14

package/src/index.ts

@@ -1938,6 +1938,7 @@ export * as TrustTaskControl_v0_1 from "./trust-task-control/0.1/payload.js";
 export * as TrustTaskDiscovery_v0_1 from "./trust-task-discovery/0.1/payload.js";
 export * as TrustTaskDiscovery_v0_2 from "./trust-task-discovery/0.2/payload.js";
 export * as TrustTaskDiscovery_v0_3 from "./trust-task-discovery/0.3/payload.js";
+export * as TrustTaskDiscovery_v0_4 from "./trust-task-discovery/0.4/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";
@@ -3146,6 +3147,48 @@ export import VtcBackupExport_v0_1 = _VtcBackupExport_v0_1;
 import * as _VtcBackupImport_v0_1 from "./vtc/backup/import/0.1/payload.js";
 /** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
 export import VtcBackupImport_v0_1 = _VtcBackupImport_v0_1;
+import * as _BoardShared_v0_1 from "./vtc/boards/_shared/0.1/board.js";
+/** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
+export import BoardShared_v0_1 = _BoardShared_v0_1;
+import * as _VtcBoardsCreate_v0_1 from "./vtc/boards/create/0.1/payload.js";
+/** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
+export import VtcBoardsCreate_v0_1 = _VtcBoardsCreate_v0_1;
+import * as _VtcBoardsIdeasDecide_v0_1 from "./vtc/boards/ideas/decide/0.1/payload.js";
+/** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
+export import VtcBoardsIdeasDecide_v0_1 = _VtcBoardsIdeasDecide_v0_1;
+import * as _VtcBoardsIdeasPropose_v0_1 from "./vtc/boards/ideas/propose/0.1/payload.js";
+/** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
+export import VtcBoardsIdeasPropose_v0_1 = _VtcBoardsIdeasPropose_v0_1;
+import * as _VtcBoardsIdeasSelect_v0_1 from "./vtc/boards/ideas/select/0.1/payload.js";
+/** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
+export import VtcBoardsIdeasSelect_v0_1 = _VtcBoardsIdeasSelect_v0_1;
+import * as _VtcBoardsIdeasUpdate_v0_1 from "./vtc/boards/ideas/update/0.1/payload.js";
+/** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
+export import VtcBoardsIdeasUpdate_v0_1 = _VtcBoardsIdeasUpdate_v0_1;
+import * as _VtcBoardsIdeasWithdraw_v0_1 from "./vtc/boards/ideas/withdraw/0.1/payload.js";
+/** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
+export import VtcBoardsIdeasWithdraw_v0_1 = _VtcBoardsIdeasWithdraw_v0_1;
+import * as _VtcBoardsList_v0_1 from "./vtc/boards/list/0.1/payload.js";
+/** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
+export import VtcBoardsList_v0_1 = _VtcBoardsList_v0_1;
+import * as _VtcBoardsNotesAdd_v0_1 from "./vtc/boards/notes/add/0.1/payload.js";
+/** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
+export import VtcBoardsNotesAdd_v0_1 = _VtcBoardsNotesAdd_v0_1;
+import * as _VtcBoardsNotesHide_v0_1 from "./vtc/boards/notes/hide/0.1/payload.js";
+/** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
+export import VtcBoardsNotesHide_v0_1 = _VtcBoardsNotesHide_v0_1;
+import * as _VtcBoardsNotesList_v0_1 from "./vtc/boards/notes/list/0.1/payload.js";
+/** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
+export import VtcBoardsNotesList_v0_1 = _VtcBoardsNotesList_v0_1;
+import * as _VtcBoardsNotesWithdraw_v0_1 from "./vtc/boards/notes/withdraw/0.1/payload.js";
+/** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
+export import VtcBoardsNotesWithdraw_v0_1 = _VtcBoardsNotesWithdraw_v0_1;
+import * as _VtcBoardsShow_v0_1 from "./vtc/boards/show/0.1/payload.js";
+/** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
+export import VtcBoardsShow_v0_1 = _VtcBoardsShow_v0_1;
+import * as _VtcBoardsUpdate_v0_1 from "./vtc/boards/update/0.1/payload.js";
+/** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
+export import VtcBoardsUpdate_v0_1 = _VtcBoardsUpdate_v0_1;
 import * as _VtcCeremoniesList_v0_1 from "./vtc/ceremonies/list/0.1/payload.js";
 /** @deprecated The prebuilt specification modules will be removed: pin the tasks you use with the `trust-tasks` CLI, generate them with `@openvtc/trust-tasks-gen`, and import the runtime from `@openvtc/trust-tasks/runtime` (GETTING-STARTED.md). */
 export import VtcCeremoniesList_v0_1 = _VtcCeremoniesList_v0_1;

package/src/process-attestation/0.1/payload.ts

@@ -3,7 +3,7 @@
  * Source: specs/process-attestation/0.1/payload.schema.json
  */
 
-import type { Ext } from "../../_shared/components.js";
+import type { DigestMultibase, Ext } from "../../_shared/components.js";
 
 
 /**
@@ -22,6 +22,10 @@ export type ReceiptReference =
       type: "uri";
       uri: string;
       mediaType?: string;
+      /**
+       * Digest of the exact receipt bytes the URI serves. The response's proof covers the URI and not what it serves, so this is what lets a retained response show which receipt it referred to; a Verifier that dereferences the URI compares before relying on the bytes (Verifier rule 6).
+       */
+      digestMultibase?: DigestMultibase;
     }
   | {
       type: "inline";
@@ -102,13 +106,19 @@ export interface Disclosed {
     endedAt?: string;
     checkpointCount?: number;
   };
+  /**
+   * The Holder's own report of its receipt's state. It is not verification: a Verifier relies on its own verification of the receipt (Verifier rules 4 and 7).
+   */
   integrity?: {
     chainValid?: boolean;
     signatureValid?: boolean;
     keyCustody?: "software" | "tpm" | "secureEnclave";
   };
   anchors?: {
-    kind: "rfc3161" | "opentimestamps" | "roughtime";
+    /**
+     * The anchoring mechanism. `rfc3161` is a timestamp-authority response, `opentimestamps` an OpenTimestamps proof, `roughtime` a Roughtime sample, `blockchain` a direct chain anchor. Appended values are additive; a reader passes an unrecognised one through.
+     */
+    kind: "rfc3161" | "opentimestamps" | "roughtime" | "blockchain";
     anchoredAt?: string;
   }[];
 }
@@ -123,7 +133,7 @@ export interface Unavailable {
 }
 
 /** Shared definitions this specification references, re-exported under the names it used to declare them with. */
-export type { Ext };
+export type { DigestMultibase, Ext };
 
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/process-attestation/0.1" as const;
@@ -350,6 +360,10 @@ export const PAYLOAD_SCHEMA = {
             "mediaType": {
               "type": "string",
               "maxLength": 255
+            },
+            "digestMultibase": {
+              "$ref": "#/$defs/DigestMultibase",
+              "description": "Digest of the exact receipt bytes the URI serves. The response's proof covers the URI and not what it serves, so this is what lets a retained response show which receipt it referred to; a Verifier that dereferences the URI compares before relying on the bytes (Verifier rule 6)."
             }
           }
         },
@@ -440,7 +454,8 @@ export const PAYLOAD_SCHEMA = {
                 "secureEnclave"
               ]
             }
-          }
+          },
+          "description": "The Holder's own report of its receipt's state. It is not verification: a Verifier relies on its own verification of the receipt (Verifier rules 4 and 7)."
         },
         "anchors": {
           "type": "array",
@@ -456,8 +471,10 @@ export const PAYLOAD_SCHEMA = {
                 "enum": [
                   "rfc3161",
                   "opentimestamps",
-                  "roughtime"
-                ]
+                  "roughtime",
+                  "blockchain"
+                ],
+                "description": "The anchoring mechanism. `rfc3161` is a timestamp-authority response, `opentimestamps` an OpenTimestamps proof, `roughtime` a Roughtime sample, `blockchain` a direct chain anchor. Appended values are additive; a reader passes an unrecognised one through."
               },
               "anchoredAt": {
                 "type": "string",
@@ -468,6 +485,16 @@ export const PAYLOAD_SCHEMA = {
         }
       }
     },
+    "DigestMultibase": {
+      "title": "DigestMultibase",
+      "description": "A cryptographic digest as a multibase-encoded multihash — the encoding the W3C Verifiable Credentials Data Model 2.0 defines for `digestMultibase`, and the one `did:webvh` uses for its SCID and entry hashes.\n\nMultihash carries the hash algorithm in-band, so the value is self-describing and the wire format survives an algorithm change without a schema revision; multibase does the same for the base encoding, so a verifier never infers base58 from base64url by context. A bare hex string or a `sha-256:`-style prefix hard-codes one algorithm into the wire contract and is non-conforming here.\n\nThis definition constrains the *encoding only*. What the digest is computed over is stated by each referencing field, because it differs legitimately: a digest over a JSON document is taken over its RFC 8785 (JCS) canonicalization, while a digest over an opaque artifact is taken over its bytes. A field whose input is a JSON document and which does not name a canonicalization is not reproducible.\n\nRestricted to the two multibase headers W3C Controlled Identifiers 1.0 §2.4 normatively requires — `z` (base58btc) and `u` (base64url-no-pad). CID permits others but states that \"interoperability is not guaranteed between implementations using such values\", and a registry whose purpose is interoperability should not mint digests a conforming verifier may be unable to read. The alphabets are enforced rather than assumed: base58btc excludes 0, O, I and l, and an earlier permissive pattern let three published examples carry digests that were not valid base58 at all. base58btc is RECOMMENDED, for consistency with `did:key` and `did:webvh`.",
+      "type": "string",
+      "minLength": 16,
+      "pattern": "^(z[1-9A-HJ-NP-Za-km-z]+|u[A-Za-z0-9_-]+)$",
+      "examples": [
+        "zQmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR"
+      ]
+    },
     "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.",
@@ -640,6 +667,10 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
             "mediaType": {
               "type": "string",
               "maxLength": 255
+            },
+            "digestMultibase": {
+              "$ref": "#/$defs/DigestMultibase",
+              "description": "Digest of the exact receipt bytes the URI serves. The response's proof covers the URI and not what it serves, so this is what lets a retained response show which receipt it referred to; a Verifier that dereferences the URI compares before relying on the bytes (Verifier rule 6)."
             }
           }
         },
@@ -730,7 +761,8 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
                 "secureEnclave"
               ]
             }
-          }
+          },
+          "description": "The Holder's own report of its receipt's state. It is not verification: a Verifier relies on its own verification of the receipt (Verifier rules 4 and 7)."
         },
         "anchors": {
           "type": "array",
@@ -746,8 +778,10 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
                 "enum": [
                   "rfc3161",
                   "opentimestamps",
-                  "roughtime"
-                ]
+                  "roughtime",
+                  "blockchain"
+                ],
+                "description": "The anchoring mechanism. `rfc3161` is a timestamp-authority response, `opentimestamps` an OpenTimestamps proof, `roughtime` a Roughtime sample, `blockchain` a direct chain anchor. Appended values are additive; a reader passes an unrecognised one through."
               },
               "anchoredAt": {
                 "type": "string",
@@ -758,6 +792,16 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
         }
       }
     },
+    "DigestMultibase": {
+      "title": "DigestMultibase",
+      "description": "A cryptographic digest as a multibase-encoded multihash — the encoding the W3C Verifiable Credentials Data Model 2.0 defines for `digestMultibase`, and the one `did:webvh` uses for its SCID and entry hashes.\n\nMultihash carries the hash algorithm in-band, so the value is self-describing and the wire format survives an algorithm change without a schema revision; multibase does the same for the base encoding, so a verifier never infers base58 from base64url by context. A bare hex string or a `sha-256:`-style prefix hard-codes one algorithm into the wire contract and is non-conforming here.\n\nThis definition constrains the *encoding only*. What the digest is computed over is stated by each referencing field, because it differs legitimately: a digest over a JSON document is taken over its RFC 8785 (JCS) canonicalization, while a digest over an opaque artifact is taken over its bytes. A field whose input is a JSON document and which does not name a canonicalization is not reproducible.\n\nRestricted to the two multibase headers W3C Controlled Identifiers 1.0 §2.4 normatively requires — `z` (base58btc) and `u` (base64url-no-pad). CID permits others but states that \"interoperability is not guaranteed between implementations using such values\", and a registry whose purpose is interoperability should not mint digests a conforming verifier may be unable to read. The alphabets are enforced rather than assumed: base58btc excludes 0, O, I and l, and an earlier permissive pattern let three published examples carry digests that were not valid base58 at all. base58btc is RECOMMENDED, for consistency with `did:key` and `did:webvh`.",
+      "type": "string",
+      "minLength": 16,
+      "pattern": "^(z[1-9A-HJ-NP-Za-km-z]+|u[A-Za-z0-9_-]+)$",
+      "examples": [
+        "zQmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR"
+      ]
+    },
     "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.",

package/src/trust-task-discovery/0.1/payload.ts

@@ -6,7 +6,7 @@
 /**
  * Request payload for the framework-defined trust-task-discovery exchange. Carries zero or more slug-glob patterns the discoverer wants the responder to filter against. The response payload schema is reachable via $anchor: 'response'.
  *
- * @deprecated superseded by trust-task-discovery/0.3
+ * @deprecated superseded by trust-task-discovery/0.4
  */
 export interface TrustTaskDiscoveryPayload {
   /**
@@ -69,7 +69,7 @@ export interface TrustTaskDiscoveryPayload {
 /**
  * List of bare Type URIs the responding party supports. Carried in a Trust Task document whose type is https://trusttasks.org/spec/trust-task-discovery/0.1#response.
  *
- * @deprecated superseded by trust-task-discovery/0.3
+ * @deprecated superseded by trust-task-discovery/0.4
  */
 export interface TrustTaskDiscoveryResponsePayload {
   /**
@@ -113,12 +113,12 @@ export const EXTENDS: string | null = null;
  * this package in a later scheduled batch (SPEC "Superseded and Withdrawn
  * Versions").
  */
-export const DEPRECATION: string | null = "superseded by trust-task-discovery/0.3";
+export const DEPRECATION: string | null = "superseded by trust-task-discovery/0.4";
 
 /**
  * Stable alias for this specification's request payload shape.
  *
- * @deprecated superseded by trust-task-discovery/0.3
+ * @deprecated superseded by trust-task-discovery/0.4
  */
 export type Payload = TrustTaskDiscoveryPayload;
 
@@ -128,7 +128,7 @@ export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/trust-task-discove
 /**
  * Stable alias for this specification's success-response payload shape.
  *
- * @deprecated superseded by trust-task-discovery/0.3
+ * @deprecated superseded by trust-task-discovery/0.4
  */
 export type Response = TrustTaskDiscoveryResponsePayload;
 

package/src/trust-task-discovery/0.2/payload.ts

@@ -6,7 +6,7 @@
 /**
  * Request payload for the framework-defined trust-task-discovery exchange. Carries zero or more slug-glob patterns the discoverer wants the responder to filter against. The response payload schema is reachable via $anchor: 'response'.
  *
- * @deprecated superseded by trust-task-discovery/0.3
+ * @deprecated superseded by trust-task-discovery/0.4
  */
 export interface TrustTaskDiscoveryPayload {
   /**
@@ -69,7 +69,7 @@ export interface TrustTaskDiscoveryPayload {
 /**
  * List of bare Type URIs the responding party supports. Carried in a Trust Task document whose type is https://trusttasks.org/spec/trust-task-discovery/0.2#response.
  *
- * @deprecated superseded by trust-task-discovery/0.3
+ * @deprecated superseded by trust-task-discovery/0.4
  */
 export interface TrustTaskDiscoveryResponsePayload {
   /**
@@ -113,12 +113,12 @@ export const EXTENDS: string | null = null;
  * this package in a later scheduled batch (SPEC "Superseded and Withdrawn
  * Versions").
  */
-export const DEPRECATION: string | null = "superseded by trust-task-discovery/0.3";
+export const DEPRECATION: string | null = "superseded by trust-task-discovery/0.4";
 
 /**
  * Stable alias for this specification's request payload shape.
  *
- * @deprecated superseded by trust-task-discovery/0.3
+ * @deprecated superseded by trust-task-discovery/0.4
  */
 export type Payload = TrustTaskDiscoveryPayload;
 
@@ -128,7 +128,7 @@ export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/trust-task-discove
 /**
  * Stable alias for this specification's success-response payload shape.
  *
- * @deprecated superseded by trust-task-discovery/0.3
+ * @deprecated superseded by trust-task-discovery/0.4
  */
 export type Response = TrustTaskDiscoveryResponsePayload;
 

package/src/trust-task-discovery/0.3/payload.ts

@@ -5,6 +5,8 @@
 
 /**
  * Request payload for the framework-defined trust-task-discovery exchange. Carries zero or more slug-glob patterns the discoverer wants the responder to filter against. The response payload schema is reachable via $anchor: 'response'.
+ *
+ * @deprecated superseded by trust-task-discovery/0.4
  */
 export interface TrustTaskDiscoveryPayload {
   /**
@@ -66,6 +68,8 @@ export interface TrustTaskDiscoveryPayload {
 }
 /**
  * List of bare Type URIs the responding party supports. Carried in a Trust Task document whose type is https://trusttasks.org/spec/trust-task-discovery/0.3#response. A response-level `acceptanceWindow` is the window the responder applies to every listed Type URI whose entry carries none of its own. Where neither is present for an entry, the discoverer has learnt nothing about that entry's window and MUST NOT read the absence as the absence of a window.
+ *
+ * @deprecated superseded by trust-task-discovery/0.4
  */
 export interface TrustTaskDiscoveryResponsePayload {
   /**
@@ -124,15 +128,23 @@ export const EXTENDS: string | null = null;
  * this package in a later scheduled batch (SPEC "Superseded and Withdrawn
  * Versions").
  */
-export const DEPRECATION: string | null = null;
+export const DEPRECATION: string | null = "superseded by trust-task-discovery/0.4";
 
-/** Stable alias for this specification's request payload shape. */
+/**
+ * Stable alias for this specification's request payload shape.
+ *
+ * @deprecated superseded by trust-task-discovery/0.4
+ */
 export type Payload = TrustTaskDiscoveryPayload;
 
 /** Trust Task response type URI (request type URI + "#response"). */
 export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/trust-task-discovery/0.3#response" as const;
 
-/** Stable alias for this specification's success-response payload shape. */
+/**
+ * Stable alias for this specification's success-response payload shape.
+ *
+ * @deprecated superseded by trust-task-discovery/0.4
+ */
 export type Response = TrustTaskDiscoveryResponsePayload;
 
 /**