@openvtc/trust-tasks 0.14.2 → 0.16.0

package/src/config/show/0.1/payload.ts

@@ -3,6 +3,9 @@
  * Source: specs/config/show/0.1/payload.schema.json
  */
 
+import type { ConfigField, Ext } from "../../../_shared/components.js";
+
+
 export interface ConfigShowPayload {
   /**
    * Return only these keys. Omitted = return every registered key.
@@ -12,12 +15,6 @@ export interface ConfigShowPayload {
   keys?: [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;
-}
 export interface ConfigShowResponsePayload {
   /**
    * The effective value of each requested (or every) configuration key.
@@ -25,29 +22,9 @@ export interface ConfigShowResponsePayload {
   fields: ConfigField[];
   ext?: Ext;
 }
-/**
- * One runtime configuration key as the maintainer currently sees it, after resolving whatever layered overlay it uses.
- */
-export interface ConfigField {
-  /**
-   * The configuration key, e.g. `server.port` or `log.level`.
-   */
-  key: string;
-  /**
-   * The effective value. Any JSON scalar the key holds (string, number, boolean, or null). A maintainer MUST redact the value of a secret-bearing key (see the spec) rather than return it here.
-   */
-  value: {
-    [k: string]: unknown | undefined;
-  };
-  /**
-   * Which layer supplied the effective value. An opaque maintainer-defined label — the framework does not enumerate it. A maintainer with a layered overlay reports the winning layer (e.g. `env`, `db`, `toml`, `default`); one without layers reports its single source.
-   */
-  source: string;
-  /**
-   * True when a change to this key takes effect only after a restart, rather than on the next read.
-   */
-  requiresRestart: boolean;
-}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { ConfigField, Ext };
 
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/config/show/0.1" as const;
@@ -240,6 +217,7 @@ export const SPEC = {
   isBearer: false,
   isProofRequired: false,
   isRecipientRequired: true,
+  isIssuedAtRequired: false,
   payloadSchema: PAYLOAD_SCHEMA,
 } as const;
 
@@ -253,5 +231,6 @@ export const RESPONSE_SPEC = {
   isBearer: false,
   isProofRequired: false,
   isRecipientRequired: true,
+  isIssuedAtRequired: false,
   payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
 } as const;

package/src/confirm/request/0.1/payload.ts

@@ -3,6 +3,9 @@
  * Source: specs/confirm/request/0.1/payload.schema.json
  */
 
+import type { Ext } from "../../../_shared/components.js";
+
+
 /**
  * A relying party asks a wallet (or other approval agent) to obtain user confirmation for an action. The wallet surfaces the reason to the user and returns a signed confirm/response.
  */
@@ -33,12 +36,6 @@ export interface ConfirmRequest {
   ttl?: 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;
-}
 /**
  * Synchronous acknowledgement that the wallet received the request and will (or will not) deliver a confirm/response. The actual signed confirmation arrives via confirm/response out-of-band. Carried in a Trust Task document whose type is https://trusttasks.org/spec/confirm/request/0.1#response.
  */
@@ -51,6 +48,9 @@ export interface ConfirmRequestSynchronousAck {
   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/confirm/request/0.1" as const;
 
@@ -212,6 +212,7 @@ export const SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: false,
   payloadSchema: PAYLOAD_SCHEMA,
 } as const;
 
@@ -225,5 +226,6 @@ export const RESPONSE_SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: false,
   payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
 } as const;

package/src/confirm/response/0.1/payload.ts

@@ -3,6 +3,9 @@
  * Source: specs/confirm/response/0.1/payload.schema.json
  */
 
+import type { Ext } from "../../../_shared/components.js";
+
+
 /**
  * The approver's signed user-decision: subject + challenge are echoed, decision is `approved` or `denied`, and the document's proof is what the relying party verifies.
  */
@@ -22,12 +25,6 @@ export interface ConfirmResponse {
   deniedReason?: 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;
-}
 /**
  * Acknowledgement the relying party returns after processing the user decision. Carried in a Trust Task document whose type is https://trusttasks.org/spec/confirm/response/0.1#response.
  */
@@ -40,6 +37,9 @@ export interface ConfirmResponseRelyingPartyAck {
   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/confirm/response/0.1" as const;
 
@@ -194,6 +194,7 @@ export const SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: false,
   payloadSchema: PAYLOAD_SCHEMA,
 } as const;
 
@@ -207,5 +208,6 @@ export const RESPONSE_SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: false,
   payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
 } as const;

package/src/consent/_shared/0.1/consent.ts

@@ -9,3 +9,9 @@
 export interface ConsentSharedDefinitions {
   [k: string]: unknown | undefined;
 }
+
+/**
+ * The definitions this shared schema publishes, hoisted to one declaration each.
+ * See "../../../_shared/components.js".
+ */
+export type { ApproverBinding, ConsentGrant, ConsentSubject, Effect_ConsentV0_1 as Effect, Kind, Route, Scope_ConsentV0_1 as Scope } from "../../../_shared/components.js";

package/src/consent/approver-list/1.0/payload.ts

@@ -3,6 +3,9 @@
  * Source: specs/consent/approver-list/1.0/payload.schema.json
  */
 
+import type { ApproverBinding, Ext, Route } from "../../../_shared/components.js";
+
+
 /**
  * Fetch approver bindings, optionally filtered by platform or context.
  */
@@ -17,12 +20,6 @@ export interface ConsentListApproversPayload {
   context?: 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 ConsentListApproversResponsePayload {
   /**
    * Matching approver bindings.
@@ -30,31 +27,9 @@ export interface ConsentListApproversResponsePayload {
   approvers: ApproverBinding[];
   ext?: Ext;
 }
-/**
- * Who approves inbound-messaging consent for a given platform within a VTA context, and how the prompt reaches them.
- */
-export interface ApproverBinding {
-  /**
-   * Messaging-platform tag, e.g. "signal", "whatsapp", "slack".
-   */
-  platform: string;
-  /**
-   * The VTA context path this binding applies to.
-   */
-  context: string;
-  /**
-   * VID (DID) of the operator authorized to decide consent for this platform/context.
-   */
-  approver: string;
-  /**
-   * Optional. How to deliver the prompt; defaults to bridge-relay when omitted.
-   */
-  route?: "wake" | "bridge-relay";
-  /**
-   * Optional routing detail — e.g. the operator's opaque conversationRef for `bridge-relay`.
-   */
-  routeHint?: string;
-}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { ApproverBinding, Ext, Route };
 
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/consent/approver-list/1.0" as const;
@@ -270,6 +245,7 @@ export const SPEC = {
   isBearer: false,
   isProofRequired: false,
   isRecipientRequired: true,
+  isIssuedAtRequired: false,
   payloadSchema: PAYLOAD_SCHEMA,
 } as const;
 
@@ -283,5 +259,6 @@ export const RESPONSE_SPEC = {
   isBearer: false,
   isProofRequired: false,
   isRecipientRequired: true,
+  isIssuedAtRequired: false,
   payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
 } as const;

package/src/consent/approver-set/1.0/payload.ts

@@ -3,6 +3,9 @@
  * Source: specs/consent/approver-set/1.0/payload.schema.json
  */
 
+import type { Ext, Route } from "../../../_shared/components.js";
+
+
 /**
  * An admin binds the operator who approves inbound-messaging consent for a platform within a context.
  */
@@ -22,19 +25,13 @@ export interface ConsentSetApproverPayload {
   /**
    * How the prompt reaches the approver; defaults to bridge-relay.
    */
-  route?: "wake" | "bridge-relay";
+  route?: Route;
   /**
    * Optional routing detail (e.g. the operator's opaque conversationRef).
    */
   routeHint?: 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 ConsentSetApproverResponsePayload {
   /**
    * The binding was upserted.
@@ -43,6 +40,9 @@ export interface ConsentSetApproverResponsePayload {
   ext?: Ext;
 }
 
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { Ext, Route };
+
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/consent/approver-set/1.0" as const;
 
@@ -205,6 +205,7 @@ export const SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: true,
   payloadSchema: PAYLOAD_SCHEMA,
 } as const;
 
@@ -218,5 +219,6 @@ export const RESPONSE_SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: true,
   payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
 } as const;

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

@@ -3,19 +3,19 @@
  * Source: specs/consent/decision/1.0/payload.schema.json
  */
 
+import type { ConsentSubject, Effect_ConsentV0_1 as Effect, Ext, Kind, Scope_ConsentV0_1 as Scope } from "../../../_shared/components.js";
+
+
 /**
  * An approver allows or denies an AI agent's access to a messaging conversation.
  */
 export interface ConsentDecisionPayload {
   subject: ConsentSubject;
-  /**
-   * Whether the subject is permitted. The ABSENCE of any grant is treated as `deny` (default-deny).
-   */
-  effect: "allow" | "deny";
+  effect: Effect;
   /**
    * Granted scope. REQUIRED when `effect` is `allow`.
    */
-  scope?: "receive" | "converse";
+  scope?: Scope;
   /**
    * Echoes the consent/request challenge this decision answers. Omit only for an operator-initiated pre-authorization.
    */
@@ -26,33 +26,6 @@ export interface ConsentDecisionPayload {
   expiresAt?: string;
   ext?: Ext;
 }
-/**
- * The platform-agnostic identifier of WHAT is being consented to: one conversation, for one agent.
- */
-export interface ConsentSubject {
-  /**
-   * Messaging-platform tag, e.g. "signal", "whatsapp", "slack".
-   */
-  platform: string;
-  /**
-   * The bridge's OPAQUE conversation handle (e.g. "sig-1a2b3c4d"). NEVER the raw platform address — the VTA never learns the phone number / chat id.
-   */
-  conversationRef: string;
-  /**
-   * The interaction kind: a 1:1 direct message, a multi-party group, or a broadcast channel.
-   */
-  kind: "dm" | "group" | "channel";
-  /**
-   * VID (DID) of the AI agent the conversation would reach.
-   */
-  agent: string;
-}
-/**
- * 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;
-}
 /**
  * Acknowledgement that the decision was recorded (or rejected).
  */
@@ -72,6 +45,9 @@ export interface ConsentDecisionResponsePayload {
   ext?: Ext;
 }
 
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { ConsentSubject, Effect, Ext, Kind, Scope };
+
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/consent/decision/1.0" as const;
 
@@ -154,6 +130,7 @@ export const PAYLOAD_SCHEMA = {
         },
         "reason": {
           "type": "string",
+          "maxLength": 1024,
           "description": "Required when status is `rejected`."
         },
         "ext": {
@@ -259,6 +236,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
         },
         "reason": {
           "type": "string",
+          "maxLength": 1024,
           "description": "Required when status is `rejected`."
         },
         "ext": {
@@ -346,6 +324,7 @@ export const SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: true,
   payloadSchema: PAYLOAD_SCHEMA,
 } as const;
 
@@ -359,5 +338,6 @@ export const RESPONSE_SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: true,
   payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
 } as const;

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

@@ -3,6 +3,9 @@
  * Source: specs/consent/list/1.0/payload.schema.json
  */
 
+import type { ConsentGrant, ConsentSubject, Effect_ConsentV0_1 as Effect, Ext, Kind, Scope_ConsentV0_1 as Scope } from "../../../_shared/components.js";
+
+
 /**
  * A bridge fetches the consent grants it should enforce.
  */
@@ -15,6 +18,9 @@ export interface ConsentListPayload {
    * Optional. Restrict to this platform tag.
    */
   platform?: string;
+  /**
+   * Optional. A full subject, to point-check a single conversation.
+   */
   subject?: ConsentSubject;
   /**
    * Optional opaque cursor; return only grants changed after it.
@@ -22,33 +28,6 @@ export interface ConsentListPayload {
   since?: string;
   ext?: Ext;
 }
-/**
- * Optional. A full subject, to point-check a single conversation.
- */
-export interface ConsentSubject {
-  /**
-   * Messaging-platform tag, e.g. "signal", "whatsapp", "slack".
-   */
-  platform: string;
-  /**
-   * The bridge's OPAQUE conversation handle (e.g. "sig-1a2b3c4d"). NEVER the raw platform address — the VTA never learns the phone number / chat id.
-   */
-  conversationRef: string;
-  /**
-   * The interaction kind: a 1:1 direct message, a multi-party group, or a broadcast channel.
-   */
-  kind: "dm" | "group" | "channel";
-  /**
-   * VID (DID) of the AI agent the conversation would reach.
-   */
-  agent: string;
-}
-/**
- * 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 grants the requesting bridge is authorized to enforce.
  */
@@ -63,57 +42,9 @@ export interface ConsentListResponsePayload {
   cursor?: string;
   ext?: Ext;
 }
-/**
- * A recorded consent decision over a ConsentSubject.
- */
-export interface ConsentGrant {
-  subject: ConsentSubject1;
-  /**
-   * Whether the subject is permitted. The ABSENCE of any grant is treated as `deny` (default-deny).
-   */
-  effect: "allow" | "deny";
-  /**
-   * Granted scope. REQUIRED when `effect` is `allow`; absent for `deny`.
-   */
-  scope?: "receive" | "converse";
-  /**
-   * VID of the approver who made the decision.
-   */
-  grantedBy: string;
-  /**
-   * RFC 3339 time the decision was recorded.
-   */
-  grantedAt: string;
-  /**
-   * Optional. After this time the grant lapses and the subject must be re-consented.
-   */
-  expiresAt?: string;
-  /**
-   * How the decision was authorized — e.g. "did-signed" (approver's DID signed the consent/decision) or "bridge-attested" (an enrolled bridge relayed the operator's out-of-band choice).
-   */
-  evidence?: string;
-}
-/**
- * The platform-agnostic identifier of WHAT is being consented to: one conversation, for one agent.
- */
-export interface ConsentSubject1 {
-  /**
-   * Messaging-platform tag, e.g. "signal", "whatsapp", "slack".
-   */
-  platform: string;
-  /**
-   * The bridge's OPAQUE conversation handle (e.g. "sig-1a2b3c4d"). NEVER the raw platform address — the VTA never learns the phone number / chat id.
-   */
-  conversationRef: string;
-  /**
-   * The interaction kind: a 1:1 direct message, a multi-party group, or a broadcast channel.
-   */
-  kind: "dm" | "group" | "channel";
-  /**
-   * VID (DID) of the AI agent the conversation would reach.
-   */
-  agent: string;
-}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { ConsentGrant, ConsentSubject, Effect, Ext, Kind, Scope };
 
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/consent/list/1.0" as const;
@@ -457,6 +388,7 @@ export const SPEC = {
   isBearer: false,
   isProofRequired: false,
   isRecipientRequired: true,
+  isIssuedAtRequired: false,
   payloadSchema: PAYLOAD_SCHEMA,
 } as const;
 
@@ -470,5 +402,6 @@ export const RESPONSE_SPEC = {
   isBearer: false,
   isProofRequired: false,
   isRecipientRequired: true,
+  isIssuedAtRequired: false,
   payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
 } as const;

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

@@ -3,10 +3,8 @@
  * 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;
+import type { ConsentSubject, DigestMultibase, Ext, Kind, Scope_ConsentV0_1 as Scope } from "../../../_shared/components.js";
+
 
 /**
  * A bridge asks the VTA whether an inbound conversation may reach an AI agent, prompting operator consent on first contact.
@@ -16,7 +14,7 @@ export interface ConsentRequestPayload {
   /**
    * The access the bridge seeks for the agent on this conversation.
    */
-  scope: "receive" | "converse";
+  scope: Scope;
   /**
    * base64url-encoded nonce (≥128 bits entropy) echoed by the matching consent/decision, so the bridge can correlate the decision to this request.
    */
@@ -25,6 +23,9 @@ export interface ConsentRequestPayload {
    * Optional operator-facing label (e.g. "Signal group 'Family'"). MUST NOT contain a raw platform address.
    */
   displayHint?: string;
+  /**
+   * Optional multibase-encoded multihash over the rfc 8785 (jcs) canonicalization of the held first message, binding the request to concrete content.
+   */
   firstMessageDigest?: DigestMultibase;
   /**
    * Optional VTA context path the bridge runs under, to scope approver resolution.
@@ -32,33 +33,6 @@ export interface ConsentRequestPayload {
   contextHint?: string;
   ext?: Ext;
 }
-/**
- * The platform-agnostic identifier of WHAT is being consented to: one conversation, for one agent.
- */
-export interface ConsentSubject {
-  /**
-   * Messaging-platform tag, e.g. "signal", "whatsapp", "slack".
-   */
-  platform: string;
-  /**
-   * The bridge's OPAQUE conversation handle (e.g. "sig-1a2b3c4d"). NEVER the raw platform address — the VTA never learns the phone number / chat id.
-   */
-  conversationRef: string;
-  /**
-   * The interaction kind: a 1:1 direct message, a multi-party group, or a broadcast channel.
-   */
-  kind: "dm" | "group" | "channel";
-  /**
-   * VID (DID) of the AI agent the conversation would reach.
-   */
-  agent: string;
-}
-/**
- * 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;
-}
 /**
  * Synchronous ack from the VTA: a prompt was routed (accepted) or the request was refused. The actual decision arrives out-of-band as a consent/decision.
  */
@@ -78,6 +52,9 @@ export interface ConsentRequestResponsePayload {
   ext?: Ext;
 }
 
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { ConsentSubject, DigestMultibase, Ext, Kind, Scope };
+
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/consent/request/1.0" as const;
 
@@ -126,6 +103,7 @@ export const PAYLOAD_SCHEMA = {
     },
     "displayHint": {
       "type": "string",
+      "maxLength": 256,
       "description": "Optional operator-facing label (e.g. \"Signal group 'Family'\"). MUST NOT contain a raw platform address."
     },
     "firstMessageDigest": {
@@ -165,6 +143,7 @@ export const PAYLOAD_SCHEMA = {
         },
         "reason": {
           "type": "string",
+          "maxLength": 1024,
           "description": "Required when status is `refused`."
         },
         "ext": {
@@ -272,6 +251,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
         },
         "reason": {
           "type": "string",
+          "maxLength": 1024,
           "description": "Required when status is `refused`."
         },
         "ext": {
@@ -361,6 +341,7 @@ export const SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: false,
   payloadSchema: PAYLOAD_SCHEMA,
 } as const;
 
@@ -374,5 +355,6 @@ export const RESPONSE_SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: false,
   payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
 } as const;