@openvtc/trust-tasks 0.14.2 → 0.16.0

package/src/did-management/did/register/0.1/payload.ts

@@ -3,6 +3,9 @@
  * Source: specs/did-management/did/register/0.1/payload.schema.json
  */
 
+import type { DidRecord, Ext } from "../../../../_shared/components.js";
+
+
 export interface DIDManagementRegisterPayload {
   /**
    * Local path under which the DID is to be hosted (e.g. `alice`, `tenant/staff/alice`). `.well-known` reserves the root slot — restricted to admin callers.
@@ -26,12 +29,6 @@ export interface DIDManagementRegisterPayload {
   force?: boolean;
   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 success response carries the canonical DidRecord the hosting service now holds for the slot.
  */
@@ -39,59 +36,9 @@ export interface DIDManagementRegisterResponsePayload {
   record: DidRecord;
   ext?: Ext;
 }
-export interface DidRecord {
-  /**
-   * Local path under which the DID is hosted (e.g. `alice`, `tenant/staff/alice`, `.well-known`). Compared by exact string equality (SPEC.md §4.8); producers SHOULD emit canonical form.
-   */
-  mnemonic: string;
-  /**
-   * VID of the party that currently owns the record. Authorization to mutate the record is anchored on this field.
-   */
-  owner: string;
-  /**
-   * RFC3339 timestamp of initial reservation.
-   */
-  createdAt: string;
-  /**
-   * RFC3339 timestamp of the most recent record mutation.
-   */
-  updatedAt: string;
-  /**
-   * Number of log entries the host currently holds for the DID. `0` indicates a reservation with no published log yet.
-   */
-  versionCount: number;
-  /**
-   * Fully-qualified DID identifier resolved from the most recent log entry (e.g. `did:webvh:<scid>:host:path`). Absent when `versionCount === 0`.
-   */
-  didId?: string;
-  /**
-   * Resolvable URL of the DID's log document (e.g. `https://did.example.com/alice/did.jsonl`). Stable across the record's lifetime: present from the initial reservation (`versionCount === 0`), it tells the owner where to publish the signed log and where resolvers fetch it. Distinct from `didId`, which only exists once a log entry has been published.
-   */
-  didUrl?: string;
-  /**
-   * DID method this record was registered under (e.g. `webvh`, `web`). When omitted, consumers MAY treat the record as legacy; SHOULD default to `webvh` only if their host predates the multi-method era.
-   */
-  method?: string;
-  /**
-   * Hosting domain (hostname) under which the DID resolves. Matches the host segment of the embedded DID identifier.
-   */
-  domain?: string;
-  /**
-   * When `true`, the DID is administratively disabled — the host serves a deactivation marker but retains content for recovery within the host's retention policy.
-   */
-  disabled?: boolean;
-  /**
-   * Lifetime resolve counter, when the host exposes per-DID statistics.
-   */
-  totalResolves?: number;
-  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;
-}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { DidRecord, Ext };
 
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/did-management/did/register/0.1" as const;
@@ -374,6 +321,7 @@ export const SPEC = {
   isBearer: false,
   isProofRequired: false,
   isRecipientRequired: true,
+  isIssuedAtRequired: true,
   payloadSchema: PAYLOAD_SCHEMA,
 } as const;
 
@@ -387,5 +335,6 @@ export const RESPONSE_SPEC = {
   isBearer: false,
   isProofRequired: false,
   isRecipientRequired: true,
+  isIssuedAtRequired: true,
   payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
 } as const;

package/src/did-management/did/rollback/0.1/payload.ts

@@ -3,76 +3,23 @@
  * Source: specs/did-management/did/rollback/0.1/payload.schema.json
  */
 
+import type { DidRecord, Ext } from "../../../../_shared/components.js";
+
+
 export interface DIDManagementRollbackPayload {
   mnemonic: string;
   targetVersion: number;
   domain?: 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 DIDManagementRollbackResponsePayload {
   record: DidRecord;
   removedVersions: number;
   ext?: Ext;
 }
-export interface DidRecord {
-  /**
-   * Local path under which the DID is hosted (e.g. `alice`, `tenant/staff/alice`, `.well-known`). Compared by exact string equality (SPEC.md §4.8); producers SHOULD emit canonical form.
-   */
-  mnemonic: string;
-  /**
-   * VID of the party that currently owns the record. Authorization to mutate the record is anchored on this field.
-   */
-  owner: string;
-  /**
-   * RFC3339 timestamp of initial reservation.
-   */
-  createdAt: string;
-  /**
-   * RFC3339 timestamp of the most recent record mutation.
-   */
-  updatedAt: string;
-  /**
-   * Number of log entries the host currently holds for the DID. `0` indicates a reservation with no published log yet.
-   */
-  versionCount: number;
-  /**
-   * Fully-qualified DID identifier resolved from the most recent log entry (e.g. `did:webvh:<scid>:host:path`). Absent when `versionCount === 0`.
-   */
-  didId?: string;
-  /**
-   * Resolvable URL of the DID's log document (e.g. `https://did.example.com/alice/did.jsonl`). Stable across the record's lifetime: present from the initial reservation (`versionCount === 0`), it tells the owner where to publish the signed log and where resolvers fetch it. Distinct from `didId`, which only exists once a log entry has been published.
-   */
-  didUrl?: string;
-  /**
-   * DID method this record was registered under (e.g. `webvh`, `web`). When omitted, consumers MAY treat the record as legacy; SHOULD default to `webvh` only if their host predates the multi-method era.
-   */
-  method?: string;
-  /**
-   * Hosting domain (hostname) under which the DID resolves. Matches the host segment of the embedded DID identifier.
-   */
-  domain?: string;
-  /**
-   * When `true`, the DID is administratively disabled — the host serves a deactivation marker but retains content for recovery within the host's retention policy.
-   */
-  disabled?: boolean;
-  /**
-   * Lifetime resolve counter, when the host exposes per-DID statistics.
-   */
-  totalResolves?: number;
-  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;
-}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { DidRecord, Ext };
 
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/did-management/did/rollback/0.1" as const;
@@ -342,6 +289,7 @@ export const SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: true,
   payloadSchema: PAYLOAD_SCHEMA,
 } as const;
 
@@ -355,5 +303,6 @@ export const RESPONSE_SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: true,
   payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
 } as const;

package/src/did-management/did/set-state/0.1/payload.ts

@@ -3,6 +3,9 @@
  * Source: specs/did-management/did/set-state/0.1/payload.schema.json
  */
 
+import type { DidRecord, Ext } from "../../../../_shared/components.js";
+
+
 export interface DIDManagementSetStatePayload {
   /**
    * The hosted DID slot whose hosting state is being set.
@@ -18,69 +21,13 @@ export interface DIDManagementSetStatePayload {
   domain?: 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 DIDManagementSetStateResponsePayload {
   record: DidRecord;
   ext?: Ext;
 }
-export interface DidRecord {
-  /**
-   * Local path under which the DID is hosted (e.g. `alice`, `tenant/staff/alice`, `.well-known`). Compared by exact string equality (SPEC.md §4.8); producers SHOULD emit canonical form.
-   */
-  mnemonic: string;
-  /**
-   * VID of the party that currently owns the record. Authorization to mutate the record is anchored on this field.
-   */
-  owner: string;
-  /**
-   * RFC3339 timestamp of initial reservation.
-   */
-  createdAt: string;
-  /**
-   * RFC3339 timestamp of the most recent record mutation.
-   */
-  updatedAt: string;
-  /**
-   * Number of log entries the host currently holds for the DID. `0` indicates a reservation with no published log yet.
-   */
-  versionCount: number;
-  /**
-   * Fully-qualified DID identifier resolved from the most recent log entry (e.g. `did:webvh:<scid>:host:path`). Absent when `versionCount === 0`.
-   */
-  didId?: string;
-  /**
-   * Resolvable URL of the DID's log document (e.g. `https://did.example.com/alice/did.jsonl`). Stable across the record's lifetime: present from the initial reservation (`versionCount === 0`), it tells the owner where to publish the signed log and where resolvers fetch it. Distinct from `didId`, which only exists once a log entry has been published.
-   */
-  didUrl?: string;
-  /**
-   * DID method this record was registered under (e.g. `webvh`, `web`). When omitted, consumers MAY treat the record as legacy; SHOULD default to `webvh` only if their host predates the multi-method era.
-   */
-  method?: string;
-  /**
-   * Hosting domain (hostname) under which the DID resolves. Matches the host segment of the embedded DID identifier.
-   */
-  domain?: string;
-  /**
-   * When `true`, the DID is administratively disabled — the host serves a deactivation marker but retains content for recovery within the host's retention policy.
-   */
-  disabled?: boolean;
-  /**
-   * Lifetime resolve counter, when the host exposes per-DID statistics.
-   */
-  totalResolves?: number;
-  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;
-}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { DidRecord, Ext };
 
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/did-management/did/set-state/0.1" as const;
@@ -346,6 +293,7 @@ export const SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: true,
   payloadSchema: PAYLOAD_SCHEMA,
 } as const;
 
@@ -359,5 +307,6 @@ export const RESPONSE_SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: true,
   payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
 } as const;

package/src/did-management/domain/assign/0.1/payload.ts

@@ -3,17 +3,14 @@
  * Source: specs/did-management/domain/assign/0.1/payload.schema.json
  */
 
+import type { Ext } from "../../../../_shared/components.js";
+
+
 export interface DomainAssignPayload {
   instanceId: string;
   domain: 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 DomainAssignResponsePayload {
   instanceId: string;
   domain: string;
@@ -21,6 +18,9 @@ export interface DomainAssignResponsePayload {
   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/did-management/domain/assign/0.1" as const;
 
@@ -164,6 +164,7 @@ export const SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: true,
   payloadSchema: PAYLOAD_SCHEMA,
 } as const;
 
@@ -177,5 +178,6 @@ export const RESPONSE_SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: true,
   payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
 } as const;

package/src/did-management/domain/create/0.1/payload.ts

@@ -3,56 +3,22 @@
  * Source: specs/did-management/domain/create/0.1/payload.schema.json
  */
 
+import type { DomainEntry, Ext } from "../../../../_shared/components.js";
+
+
 export interface DomainCreatePayload {
   name: string;
   label?: string;
   setAsDefault?: boolean;
   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 DomainCreateResponsePayload {
   entry: DomainEntry;
   ext?: Ext;
 }
-export interface DomainEntry {
-  /**
-   * Hosting domain name (e.g. `did.example.com`). Compared case-insensitively; producers SHOULD emit lowercase canonical form.
-   */
-  name: string;
-  /**
-   * Optional human-readable label.
-   */
-  label?: string;
-  /**
-   * Domain lifecycle state. A `disabled` domain still serves existing DIDs in read-only mode for the host's configured grace period before purge becomes eligible.
-   */
-  status: "active" | "disabled";
-  /**
-   * When `true`, this domain is the host's default — new DIDs created without an explicit domain are hosted here. Exactly one entry SHOULD carry `defaultDomain: true`.
-   */
-  defaultDomain?: boolean;
-  createdAt: string;
-  /**
-   * Present iff `status === "disabled"`.
-   */
-  disabledAt?: string;
-  /**
-   * Earliest RFC3339 timestamp at which the host's background sweep is allowed to purge content for a disabled domain. Operators with administrative authority MAY override the wait via `domain/purge`.
-   */
-  purgeAt?: string;
-  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;
-}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { DomainEntry, Ext };
 
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/did-management/domain/create/0.1" as const;
@@ -90,7 +56,8 @@ export const PAYLOAD_SCHEMA = {
       "minLength": 1
     },
     "label": {
-      "type": "string"
+      "type": "string",
+      "maxLength": 256
     },
     "setAsDefault": {
       "type": "boolean",
@@ -277,6 +244,7 @@ export const SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: true,
   payloadSchema: PAYLOAD_SCHEMA,
 } as const;
 
@@ -290,5 +258,6 @@ export const RESPONSE_SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: true,
   payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
 } as const;

package/src/did-management/domain/disable/0.1/payload.ts

@@ -3,54 +3,20 @@
  * Source: specs/did-management/domain/disable/0.1/payload.schema.json
  */
 
+import type { DomainEntry, Ext } from "../../../../_shared/components.js";
+
+
 export interface DomainDisablePayload {
   name: 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 DomainDisableResponsePayload {
   entry: DomainEntry;
   ext?: Ext;
 }
-export interface DomainEntry {
-  /**
-   * Hosting domain name (e.g. `did.example.com`). Compared case-insensitively; producers SHOULD emit lowercase canonical form.
-   */
-  name: string;
-  /**
-   * Optional human-readable label.
-   */
-  label?: string;
-  /**
-   * Domain lifecycle state. A `disabled` domain still serves existing DIDs in read-only mode for the host's configured grace period before purge becomes eligible.
-   */
-  status: "active" | "disabled";
-  /**
-   * When `true`, this domain is the host's default — new DIDs created without an explicit domain are hosted here. Exactly one entry SHOULD carry `defaultDomain: true`.
-   */
-  defaultDomain?: boolean;
-  createdAt: string;
-  /**
-   * Present iff `status === "disabled"`.
-   */
-  disabledAt?: string;
-  /**
-   * Earliest RFC3339 timestamp at which the host's background sweep is allowed to purge content for a disabled domain. Operators with administrative authority MAY override the wait via `domain/purge`.
-   */
-  purgeAt?: string;
-  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;
-}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { DomainEntry, Ext };
 
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/did-management/domain/disable/0.1" as const;
@@ -268,6 +234,7 @@ export const SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: false,
   payloadSchema: PAYLOAD_SCHEMA,
 } as const;
 
@@ -281,5 +248,6 @@ export const RESPONSE_SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: false,
   payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
 } as const;

package/src/did-management/domain/enable/0.1/payload.ts

@@ -3,54 +3,20 @@
  * Source: specs/did-management/domain/enable/0.1/payload.schema.json
  */
 
+import type { DomainEntry, Ext } from "../../../../_shared/components.js";
+
+
 export interface DomainEnablePayload {
   name: 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 DomainEnableResponsePayload {
   entry: DomainEntry;
   ext?: Ext;
 }
-export interface DomainEntry {
-  /**
-   * Hosting domain name (e.g. `did.example.com`). Compared case-insensitively; producers SHOULD emit lowercase canonical form.
-   */
-  name: string;
-  /**
-   * Optional human-readable label.
-   */
-  label?: string;
-  /**
-   * Domain lifecycle state. A `disabled` domain still serves existing DIDs in read-only mode for the host's configured grace period before purge becomes eligible.
-   */
-  status: "active" | "disabled";
-  /**
-   * When `true`, this domain is the host's default — new DIDs created without an explicit domain are hosted here. Exactly one entry SHOULD carry `defaultDomain: true`.
-   */
-  defaultDomain?: boolean;
-  createdAt: string;
-  /**
-   * Present iff `status === "disabled"`.
-   */
-  disabledAt?: string;
-  /**
-   * Earliest RFC3339 timestamp at which the host's background sweep is allowed to purge content for a disabled domain. Operators with administrative authority MAY override the wait via `domain/purge`.
-   */
-  purgeAt?: string;
-  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;
-}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { DomainEntry, Ext };
 
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/did-management/domain/enable/0.1" as const;
@@ -268,6 +234,7 @@ export const SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: false,
   payloadSchema: PAYLOAD_SCHEMA,
 } as const;
 
@@ -281,5 +248,6 @@ export const RESPONSE_SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: false,
   payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
 } as const;

package/src/did-management/domain/purge/0.1/payload.ts

@@ -3,17 +3,14 @@
  * Source: specs/did-management/domain/purge/0.1/payload.schema.json
  */
 
+import type { Ext } from "../../../../_shared/components.js";
+
+
 export interface DomainPurgePayload {
   name: string;
   purgeServers?: boolean;
   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 DomainPurgeResponsePayload {
   name: string;
   purgedAt: string;
@@ -24,6 +21,9 @@ export interface DomainPurgeResponsePayload {
   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/did-management/domain/purge/0.1" as const;
 
@@ -200,6 +200,7 @@ export const SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: true,
   payloadSchema: PAYLOAD_SCHEMA,
 } as const;
 
@@ -213,5 +214,6 @@ export const RESPONSE_SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: true,
   payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
 } as const;