@openvtc/trust-tasks 0.14.2 → 0.15.0

package/src/auth/step-up/policy/0.2/payload.ts

@@ -3,6 +3,9 @@
  * Source: specs/auth/step-up/policy/0.2/payload.schema.json
  */
 
+import type { Ext } from "../../../../_shared/components.js";
+
+
 /**
  * The relying party's (ACL maintainer's) system-wide step-up policy: the per-operation-class floor that decides whether — and how — a step-up to a higher assurance level is required before a gated operation proceeds. Set by an administrator; resolved per request against per-entry overrides (see acl/_shared AclEntry.stepUp).
  */
@@ -15,6 +18,9 @@ export interface AuthStepUpPolicyPayload {
    * The system-wide minimum step-up requirement per operation-class — the maintainer-owned floor. Per-entry `stepUp` settings on an AclEntry MAY raise the requirement for a given subject but MUST NOT lower it (additive-only). The effective requirement for a request is the strictest of (matching floor, caller's per-entry setting).
    */
   floors: StepUpFloor[];
+  /**
+   * Ecosystem-defined extension members per SPEC.md §4.5.1.
+   */
   ext?: Ext;
 }
 export interface StepUpFloor {
@@ -31,12 +37,6 @@ export interface StepUpFloor {
    */
   allowAal1IfNonEscalating?: boolean;
 }
-/**
- * Ecosystem-defined extension members per SPEC.md §4.5.1.
- */
-export interface Ext {
-  [k: string]: unknown | undefined;
-}
 /**
  * The policy the maintainer now holds after applying the request. Carried in a Trust Task document whose type is https://trusttasks.org/spec/auth/step-up/policy/0.1#response.
  */
@@ -49,15 +49,12 @@ export interface AuthStepUpPolicyResponsePayload {
    * The effective floors the maintainer now holds (canonicalized: deduplicated by `operation`, defaults materialized).
    */
   floors: StepUpFloor[];
-  ext?: Ext1;
-}
-/**
- * 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 Ext1 {
-  [k: string]: unknown | undefined;
+  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/auth/step-up/policy/0.2" as const;
 

package/src/auth/whoami/0.1/payload.ts

@@ -3,22 +3,25 @@
  * Source: specs/auth/whoami/0.1/payload.schema.json
  */
 
+import type { Ext, Session } from "../../../_shared/components.js";
+
+
 /**
  * Introspect the current session. The proof on the document identifies the subject; the response carries what the auth service knows about them.
  */
 export interface AuthWhoami {
+  /**
+   * Ecosystem-defined extension members per SPEC.md §4.5.1.
+   */
   ext?: Ext;
 }
-/**
- * Ecosystem-defined extension members per SPEC.md §4.5.1.
- */
-export interface Ext {
-  [k: string]: unknown | undefined;
-}
 /**
  * The auth service's view of the producer. Carried in a Trust Task document whose type is https://trusttasks.org/spec/auth/whoami/0.1#response.
  */
 export interface AuthWhoamiResponsePayload {
+  /**
+   * Current session state for the producer.
+   */
   session: Session;
   /**
    * Role assignments the auth service holds for the producer. Ecosystem-defined vocabulary.
@@ -28,53 +31,15 @@ export interface AuthWhoamiResponsePayload {
    * Capability tags effective on the producer's current session. Mirrors the issued TokenBundle.scope; included here so a producer can reconcile after policy edits without re-issuing tokens.
    */
   scopes?: string[];
-  ext?: Ext2;
-}
-/**
- * Current session state for the producer.
- */
-export interface Session {
-  /**
-   * Opaque, server-chosen session identifier. Stable for the lifetime of the session. Consumers MUST treat the value as opaque; no structure is implied.
-   */
-  id: string;
-  /**
-   * The authenticated party's VID (typically a DID URL).
-   */
-  subject: string;
-  /**
-   * ISO-8601 timestamp when the session was created.
-   */
-  issuedAt: string;
-  /**
-   * ISO-8601 timestamp when the session ceases to be valid. Producers SHOULD refresh before this time; consumers MUST reject after.
-   */
-  expiresAt: string;
-  /**
-   * Authentication Methods References per [RFC 8176]. Typical values: "did" (challenge-response), "passkey" (WebAuthn), "vta" (verifiable-trust agent approval). Multi-factor sessions list every method used.
-   *
-   * @minItems 1
-   */
-  amr?: [string, ...string[]];
   /**
-   * Authentication Context Class Reference per [OIDC Core §2]. Profiles define their own values; the recommended set is "aal1" (single-factor DID auth), "aal2" (a second possession-or-biometric factor confirmed), and "aal3" (hardware-bound second factor).
+   * Ecosystem-defined extension members per SPEC.md §4.5.1.
    */
-  acr?: string;
-  ext?: Ext1;
-}
-/**
- * Ecosystem-defined extension members per SPEC.md §4.5.1.
- */
-export interface Ext1 {
-  [k: string]: unknown | undefined;
-}
-/**
- * Ecosystem-defined extension members per SPEC.md §4.5.1.
- */
-export interface Ext2 {
-  [k: string]: unknown | undefined;
+  ext?: Ext;
 }
 
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { Ext, Session };
+
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/auth/whoami/0.1" as const;
 

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

@@ -3,14 +3,8 @@
  * 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;
+import type { DigestMultibase, Ext } from "../../../_shared/components.js";
+
 
 /**
  * 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.
@@ -94,6 +88,9 @@ export interface AttachmentRef {
    * OPTIONAL. Size in bytes, if known ahead of fetch.
    */
   sizeBytes?: number;
+  /**
+   * 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.
+   */
   digest?: DigestMultibase;
 }
 /**
@@ -104,15 +101,15 @@ export interface ChainLink {
    * The `id` of the previous `chat/message` Trust Task document in this conversation.
    */
   id: 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.
- */
-export interface Ext {
-  [k: string]: unknown | undefined;
+  /**
+   * 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.
+   */
+  digest: DigestMultibase;
 }
 
+/** 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/chat/message/0.1" as const;
 

package/src/config/_shared/0.1/config.ts

@@ -9,3 +9,9 @@
 export interface ConfigSharedDefinitions {
   [k: string]: unknown | undefined;
 }
+
+/**
+ * The definitions this shared schema publishes, hoisted to one declaration each.
+ * See "../../../_shared/components.js".
+ */
+export type { ConfigField, RejectedKey } from "../../../_shared/components.js";

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

@@ -3,6 +3,9 @@
  * Source: specs/config/patch/0.1/payload.schema.json
  */
 
+import type { Ext, RejectedKey } from "../../../_shared/components.js";
+
+
 export interface ConfigPatchPayload {
   /**
    * A key -> value map of overrides to write. Keys are configuration keys; values are the desired new values. Wrapped in an object (rather than being the top-level payload) so the payload keeps a fixed, additionalProperties:false envelope. Each entry is validated independently — an invalid or unknown key is reported under `rejected` and does not block the rest.
@@ -12,12 +15,6 @@ export interface ConfigPatchPayload {
   };
   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 ConfigPatchResponsePayload {
   /**
    * Keys whose new value is now in effect.
@@ -33,16 +30,9 @@ export interface ConfigPatchResponsePayload {
   rejected: RejectedKey[];
   ext?: Ext;
 }
-/**
- * A key a patch declined to apply, with the reason.
- */
-export interface RejectedKey {
-  key: string;
-  /**
-   * Why the key was rejected — unknown key, wrong type, out-of-range, allowlist mismatch, etc.
-   */
-  reason: string;
-}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { Ext, RejectedKey };
 
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/config/patch/0.1" as const;

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

@@ -3,18 +3,15 @@
  * Source: specs/config/reload/0.1/payload.schema.json
  */
 
+import type { Ext } from "../../../_shared/components.js";
+
+
 /**
  * Re-apply hot-reloadable configuration to the running maintainer without a restart. Takes no parameters.
  */
 export interface ConfigReloadPayload {
   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 ConfigReloadResponsePayload {
   /**
    * Keys whose live value was updated by the reload — the hot-reloadable keys whose stored value differed from what was running. A no-op reload returns an empty array. Restart-gated keys are never included; they need config/restart.
@@ -23,6 +20,9 @@ export interface ConfigReloadResponsePayload {
   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/config/reload/0.1" as const;
 

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

@@ -3,18 +3,15 @@
  * Source: specs/config/restart/0.1/payload.schema.json
  */
 
+import type { Ext } from "../../../_shared/components.js";
+
+
 /**
  * Request a graceful restart so a process supervisor brings the maintainer back up with restart-gated configuration applied. Takes no parameters.
  */
 export interface ConfigRestartPayload {
   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 ConfigRestartResponsePayload {
   /**
    * The process supervisor that will bring the maintainer back up, detected by the maintainer. An opaque maintainer-defined label — the framework does not enumerate it (e.g. `systemd`, `kubernetes`, or an explicit operator opt-in). A maintainer that detects no supervisor MUST refuse (see errorCodes) rather than exit unsupervised.
@@ -27,6 +24,9 @@ export interface ConfigRestartResponsePayload {
   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/config/restart/0.1" as const;
 

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;

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;
 

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;
 

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;

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;
 

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;