@openvtc/trust-tasks 0.14.2 → 0.15.0

package/src/vta/app-state/get/1.0/payload.ts

@@ -3,18 +3,8 @@
  * Source: specs/vta/app-state/get/1.0/payload.schema.json
  */
 
-/**
- * Scopes one application's records within a context, so several tools can share a context without colliding — `openvtc`, `cnm`, an agent runtime. The maintainer MUST NOT interpret the value; it is an opaque partition name. Namespaces are first-come and unreserved, so an application SHOULD pick a stable, specific one: a future per-namespace ACL would grant on this exact string, which makes renaming a namespace a migration rather than an edit.
- */
-export type Namespace = string;
-/**
- * Application-chosen identifier for a record within a namespace. Opaque to the maintainer: it MUST NOT be parsed, normalized, or case-folded, and prefix matching in `list` is a byte-prefix comparison over the UTF-8 encoding. Applications SHOULD use `/`-delimited hierarchical keys (`community/acme`, `contact/z6Mk…`) so that `prefix` can address a record family, but the delimiter is a convention between an application and itself — the maintainer attaches no meaning to it.
- */
-export type Key = string;
-/**
- * The namespace counter value this record's most recent write took. Supply it as `expectedVersion` on the next write to make that write conditional on nothing having changed in between.
- */
-export type Version = number;
+import type { AppStateRecord, Ext, Key, Namespace, Version } from "../../../../_shared/components.js";
+
 
 /**
  * Read one application-state record by its `(contextId, namespace, key)` address. Returns the record with its value and its version; the version is what a subsequent conditional write supplies as `expectedVersion`.
@@ -30,66 +20,28 @@ export interface VTAApplicationStateGetPayload {
    * Defaults to false. When true, a tombstone at this address is returned as a record with `deleted: true` instead of being reported as absent. Lets a consumer distinguish "deleted, and here is the version that deleted it" from "never existed, or deleted so long ago the tombstone was reaped" — a distinction a repair path needs and a normal read does not.
    */
   includeDeleted?: boolean;
+  /**
+   * 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;
-}
 /**
  * Success response to vta/app-state/get. Type https://trusttasks.org/spec/vta/app-state/get/1.0#response. An absent record is not a success: it is reported as a trust-task-error carrying vta/app-state/get:notFound.
  */
 export interface VTAApplicationStateGetResponsePayload {
-  record: AppStateRecord;
-  ext?: Ext1;
-}
-/**
- * The record at the requested address, with its `value` populated (unless it is a tombstone returned under `includeDeleted`).
- */
-export interface AppStateRecord {
-  /**
-   * The VTA context the record is scoped to; the isolation boundary.
-   */
-  contextId: string;
-  namespace: Namespace;
-  key: Key;
-  version: Version;
-  /**
-   * The stored JSON, in whatever shape the owning application chose. Any JSON value, including `null`. The maintainer neither validates nor interprets it. Absent when this is a tombstone or a metadata-only view — see this definition's description for why that is not the same as a null value.
-   */
-  value?: {
-    [k: string]: unknown | undefined;
-  };
-  /**
-   * Size of the stored value in bytes, measured as the maintainer measures it for the per-record cap (see `vta/app-state/put`). Present in metadata-only views so a consumer can decide what to fetch without fetching it; absent on a tombstone.
-   */
-  valueBytes?: number;
-  /**
-   * True when this is a tombstone: the record was deleted, and this entry exists so that a consumer syncing incrementally learns of the deletion. Tombstones are reaped after the maintainer's retention window; see `vta/app-state/list`.
-   */
-  deleted: boolean;
-  /**
-   * When the record was first created at this address. MAY be absent on a tombstone whose body has been discarded.
-   */
-  createdAt?: string;
   /**
-   * When the write that produced this `version` was applied. For a tombstone, when the delete was applied.
+   * The record at the requested address, with its `value` populated (unless it is a tombstone returned under `includeDeleted`).
    */
-  updatedAt: string;
+  record: AppStateRecord;
   /**
-   * When the record was deleted. Present only when `deleted` is true; equal to `updatedAt` for a tombstone the maintainer has not since rewritten.
+   * Ecosystem-defined extension members per SPEC.md §4.5.1.
    */
-  deletedAt?: string;
-}
-/**
- * Ecosystem-defined extension members per SPEC.md §4.5.1.
- */
-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 { AppStateRecord, Ext, Key, Namespace, Version };
+
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/vta/app-state/get/1.0" as const;
 

package/src/vta/app-state/get-many/1.0/payload.ts

@@ -3,22 +3,8 @@
  * Source: specs/vta/app-state/get-many/1.0/payload.schema.json
  */
 
-/**
- * Required, unlike in list: a batch read addresses records by key, and a key is only unique within a namespace.
- */
-export type Namespace = string;
-/**
- * Application-chosen identifier for a record within a namespace. Opaque to the maintainer: it MUST NOT be parsed, normalized, or case-folded, and prefix matching in `list` is a byte-prefix comparison over the UTF-8 encoding. Applications SHOULD use `/`-delimited hierarchical keys (`community/acme`, `contact/z6Mk…`) so that `prefix` can address a record family, but the delimiter is a convention between an application and itself — the maintainer attaches no meaning to it.
- */
-export type Key = string;
-/**
- * Scopes one application's records within a context, so several tools can share a context without colliding — `openvtc`, `cnm`, an agent runtime. The maintainer MUST NOT interpret the value; it is an opaque partition name. Namespaces are first-come and unreserved, so an application SHOULD pick a stable, specific one: a future per-namespace ACL would grant on this exact string, which makes renaming a namespace a migration rather than an edit.
- */
-export type Namespace1 = string;
-/**
- * The namespace counter value this record's most recent write took. Supply it as `expectedVersion` on the next write to make that write conditional on nothing having changed in between.
- */
-export type Version = number;
+import type { AppStateRecord, Ext, Key, Namespace, Version } from "../../../../_shared/components.js";
+
 
 /**
  * Read up to 256 application-state records from one namespace in a single round trip. A rebuild or a reconnect is N records, and round-tripping each one separately is the difference between a usable reconnect and an unusable one.
@@ -28,6 +14,9 @@ export interface VTAApplicationStateGetManyPayload {
    * The VTA context the records are scoped to; the isolation boundary.
    */
   contextId: string;
+  /**
+   * Required, unlike in list: a batch read addresses records by key, and a key is only unique within a namespace.
+   */
   namespace: Namespace;
   /**
    * The keys to read. Duplicates are refused rather than deduplicated, because a caller that sent one did not mean to and would otherwise never find out.
@@ -40,14 +29,11 @@ export interface VTAApplicationStateGetManyPayload {
    * Defaults to false. When true, an address holding a tombstone yields a record with `deleted: true` rather than appearing in `missing`.
    */
   includeDeleted?: boolean;
+  /**
+   * 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;
-}
 /**
  * Success response to vta/app-state/get-many. Type https://trusttasks.org/spec/vta/app-state/get-many/1.0#response. Every requested key appears in exactly one of `records`, `missing` or `deferred`, so a caller can account for all of them without comparing sets itself.
  */
@@ -64,53 +50,15 @@ export interface VTAApplicationStateGetManyResponsePayload {
    * Requested keys the maintainer did not evaluate because the response had reached its size budget. The caller re-requests exactly these. This exists because the per-record cap multiplied by the key ceiling exceeds any sane response limit, and the alternative — refusing the whole batch — would make a caller guess at a batch size instead of being told one.
    */
   deferred?: Key[];
-  ext?: Ext1;
-}
-/**
- * A record as the maintainer holds it. `value` is absent in three distinct situations and a consumer MUST NOT conflate them: the record is a tombstone (`deleted` is true); the caller asked for a metadata-only view (`list` without `includeValues`); or the value genuinely is the JSON literal `null`, in which case `value` is PRESENT and null. This is why `deleted` is required rather than defaulted — a consumer that has to infer deletion from an absent value gets the tombstone case wrong exactly when convergence depends on it.
- */
-export interface AppStateRecord {
   /**
-   * The VTA context the record is scoped to; the isolation boundary.
+   * Ecosystem-defined extension members per SPEC.md §4.5.1.
    */
-  contextId: string;
-  namespace: Namespace1;
-  key: Key;
-  version: Version;
-  /**
-   * The stored JSON, in whatever shape the owning application chose. Any JSON value, including `null`. The maintainer neither validates nor interprets it. Absent when this is a tombstone or a metadata-only view — see this definition's description for why that is not the same as a null value.
-   */
-  value?: {
-    [k: string]: unknown | undefined;
-  };
-  /**
-   * Size of the stored value in bytes, measured as the maintainer measures it for the per-record cap (see `vta/app-state/put`). Present in metadata-only views so a consumer can decide what to fetch without fetching it; absent on a tombstone.
-   */
-  valueBytes?: number;
-  /**
-   * True when this is a tombstone: the record was deleted, and this entry exists so that a consumer syncing incrementally learns of the deletion. Tombstones are reaped after the maintainer's retention window; see `vta/app-state/list`.
-   */
-  deleted: boolean;
-  /**
-   * When the record was first created at this address. MAY be absent on a tombstone whose body has been discarded.
-   */
-  createdAt?: string;
-  /**
-   * When the write that produced this `version` was applied. For a tombstone, when the delete was applied.
-   */
-  updatedAt: string;
-  /**
-   * When the record was deleted. Present only when `deleted` is true; equal to `updatedAt` for a tombstone the maintainer has not since rewritten.
-   */
-  deletedAt?: string;
-}
-/**
- * Ecosystem-defined extension members per SPEC.md §4.5.1.
- */
-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 { AppStateRecord, Ext, Key, Namespace, Version };
+
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/vta/app-state/get-many/1.0" as const;
 

package/src/vta/app-state/list/1.0/payload.ts

@@ -3,26 +3,8 @@
  * Source: specs/vta/app-state/list/1.0/payload.schema.json
  */
 
-/**
- * Restrict to one namespace. Optional in snapshot mode, where omitting it enumerates every namespace the caller can read in the context. REQUIRED in change-feed mode, because the version counter `sinceVersion` is compared against is maintained per (contextId, namespace) and a watermark spanning namespaces would name no single point in time.
- */
-export type Namespace = string;
-/**
- * Scopes one application's records within a context, so several tools can share a context without colliding — `openvtc`, `cnm`, an agent runtime. The maintainer MUST NOT interpret the value; it is an opaque partition name. Namespaces are first-come and unreserved, so an application SHOULD pick a stable, specific one: a future per-namespace ACL would grant on this exact string, which makes renaming a namespace a migration rather than an edit.
- */
-export type Namespace1 = string;
-/**
- * Application-chosen identifier for a record within a namespace. Opaque to the maintainer: it MUST NOT be parsed, normalized, or case-folded, and prefix matching in `list` is a byte-prefix comparison over the UTF-8 encoding. Applications SHOULD use `/`-delimited hierarchical keys (`community/acme`, `contact/z6Mk…`) so that `prefix` can address a record family, but the delimiter is a convention between an application and itself — the maintainer attaches no meaning to it.
- */
-export type Key = string;
-/**
- * The namespace counter value this record's most recent write took. Supply it as `expectedVersion` on the next write to make that write conditional on nothing having changed in between.
- */
-export type Version = number;
-/**
- * The namespace's current counter value. Present whenever `namespace` was supplied. This is what a consumer stores as its next `sinceVersion` — NOT the maximum version among `records`, which is wrong whenever a `prefix` filtered a later change out, and undefined when the page is empty. A paginating consumer MUST NOT advance its stored watermark until it has drained the final page, because the pages of one feed share this value and adopting it early would skip the records still to come.
- */
-export type Version1 = number;
+import type { AppStateRecord, Ext, Key, Namespace, Version } from "../../../../_shared/components.js";
+
 
 /**
  * Enumerate application-state records in a context. Two modes, distinguished by whether `sinceVersion` is supplied. Without it this is a SNAPSHOT of live records, optionally narrowed by `prefix`. With it this is a CHANGE FEED: every record in the namespace whose version exceeds the watermark, tombstones included, which is what lets an incremental consumer converge. Pagination is opaque-cursor based.
@@ -32,6 +14,9 @@ export interface VTAApplicationStateListPayload {
    * The VTA context to enumerate; the isolation boundary.
    */
   contextId: string;
+  /**
+   * Restrict to one namespace. Optional in snapshot mode, where omitting it enumerates every namespace the caller can read in the context. REQUIRED in change-feed mode, because the version counter `sinceVersion` is compared against is maintained per (contextId, namespace) and a watermark spanning namespaces would name no single point in time.
+   */
   namespace?: Namespace;
   /**
    * Restrict to records whose `key` begins with this byte prefix, compared over the UTF-8 encoding. Lets a consumer read one record family — `community/`, `contact/` — without dragging every record in the namespace through the response.
@@ -57,14 +42,11 @@ export interface VTAApplicationStateListPayload {
    * Opaque continuation token from a previous response. Consumers MUST treat it as opaque: never construct, decode, mutate, or infer meaning from one.
    */
   cursor?: string;
+  /**
+   * 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;
-}
 /**
  * Success response to vta/app-state/list. Type https://trusttasks.org/spec/vta/app-state/list/1.0#response.
  */
@@ -81,58 +63,23 @@ export interface VTAApplicationStateListResponsePayload {
    * Opaque continuation token for the next page. Present only when `truncated` is true.
    */
   cursor?: string;
-  highWatermark?: Version1;
   /**
-   * How long this maintainer retains tombstones before reaping them. Advisory, and present at the maintainer's discretion, so a consumer can schedule its syncs to stay inside the window rather than discovering it has fallen out of it via vta/app-state/list:watermarkTooOld.
+   * The namespace's current counter value. Present whenever `namespace` was supplied. This is what a consumer stores as its next `sinceVersion` — NOT the maximum version among `records`, which is wrong whenever a `prefix` filtered a later change out, and undefined when the page is empty. A paginating consumer MUST NOT advance its stored watermark until it has drained the final page, because the pages of one feed share this value and adopting it early would skip the records still to come.
    */
-  tombstoneRetentionSeconds?: number;
-  ext?: Ext1;
-}
-/**
- * A record as the maintainer holds it. `value` is absent in three distinct situations and a consumer MUST NOT conflate them: the record is a tombstone (`deleted` is true); the caller asked for a metadata-only view (`list` without `includeValues`); or the value genuinely is the JSON literal `null`, in which case `value` is PRESENT and null. This is why `deleted` is required rather than defaulted — a consumer that has to infer deletion from an absent value gets the tombstone case wrong exactly when convergence depends on it.
- */
-export interface AppStateRecord {
-  /**
-   * The VTA context the record is scoped to; the isolation boundary.
-   */
-  contextId: string;
-  namespace: Namespace1;
-  key: Key;
-  version: Version;
-  /**
-   * The stored JSON, in whatever shape the owning application chose. Any JSON value, including `null`. The maintainer neither validates nor interprets it. Absent when this is a tombstone or a metadata-only view — see this definition's description for why that is not the same as a null value.
-   */
-  value?: {
-    [k: string]: unknown | undefined;
-  };
-  /**
-   * Size of the stored value in bytes, measured as the maintainer measures it for the per-record cap (see `vta/app-state/put`). Present in metadata-only views so a consumer can decide what to fetch without fetching it; absent on a tombstone.
-   */
-  valueBytes?: number;
-  /**
-   * True when this is a tombstone: the record was deleted, and this entry exists so that a consumer syncing incrementally learns of the deletion. Tombstones are reaped after the maintainer's retention window; see `vta/app-state/list`.
-   */
-  deleted: boolean;
-  /**
-   * When the record was first created at this address. MAY be absent on a tombstone whose body has been discarded.
-   */
-  createdAt?: string;
+  highWatermark?: Version;
   /**
-   * When the write that produced this `version` was applied. For a tombstone, when the delete was applied.
+   * How long this maintainer retains tombstones before reaping them. Advisory, and present at the maintainer's discretion, so a consumer can schedule its syncs to stay inside the window rather than discovering it has fallen out of it via vta/app-state/list:watermarkTooOld.
    */
-  updatedAt: string;
+  tombstoneRetentionSeconds?: number;
   /**
-   * When the record was deleted. Present only when `deleted` is true; equal to `updatedAt` for a tombstone the maintainer has not since rewritten.
+   * Ecosystem-defined extension members per SPEC.md §4.5.1.
    */
-  deletedAt?: string;
-}
-/**
- * Ecosystem-defined extension members per SPEC.md §4.5.1.
- */
-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 { AppStateRecord, Ext, Key, Namespace, Version };
+
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/vta/app-state/list/1.0" as const;
 

package/src/vta/app-state/put/1.0/payload.ts

@@ -3,6 +3,9 @@
  * Source: specs/vta/app-state/put/1.0/payload.schema.json
  */
 
+import type { ExpectedVersion, Ext, Key, Namespace, Version } from "../../../../_shared/components.js";
+
+
 /**
  * Write one application-state record at its `(contextId, namespace, key)` address. Exactly one of `value` (whole-record replacement) or `mergePatch` (RFC 7386 partial update) is supplied. `expectedVersion` makes the write conditional: a positive value requires the record to be at exactly that version, and zero requires that no live record exists.
  */
@@ -23,34 +26,18 @@ export type VTAApplicationStatePutPayload = {
    * An RFC 7386 JSON Merge Patch applied to the record's current value. Cuts payload, and more usefully cuts conflicts: two instances editing different members of one record stop colliding entirely rather than serialising behind `expectedVersion`. Requires a live record at the address. Note RFC 7386's one sharp edge — a member set to `null` in the patch DELETES that member from the value, and there is no way to set a member to the JSON literal null through a patch; a writer that needs to do so must send a whole `value`. Mutually exclusive with `value`.
    */
   mergePatch?: {};
+  /**
+   * Optional precondition. Omit for a last-writer-wins upsert. Supply the version a prior read returned to make the write conditional; supply 0 to create only.
+   */
   expectedVersion?: ExpectedVersion;
+  /**
+   * Ecosystem-defined extension members per SPEC.md §4.5.1.
+   */
   ext?: Ext;
 } & {
   [k: string]: unknown | undefined;
 };
-/**
- * Scopes one application's records within a context, so several tools can share a context without colliding — `openvtc`, `cnm`, an agent runtime. The maintainer MUST NOT interpret the value; it is an opaque partition name. Namespaces are first-come and unreserved, so an application SHOULD pick a stable, specific one: a future per-namespace ACL would grant on this exact string, which makes renaming a namespace a migration rather than an edit.
- */
-export type Namespace = string;
-/**
- * Application-chosen identifier for a record within a namespace. Opaque to the maintainer: it MUST NOT be parsed, normalized, or case-folded, and prefix matching in `list` is a byte-prefix comparison over the UTF-8 encoding. Applications SHOULD use `/`-delimited hierarchical keys (`community/acme`, `contact/z6Mk…`) so that `prefix` can address a record family, but the delimiter is a convention between an application and itself — the maintainer attaches no meaning to it.
- */
-export type Key = string;
-/**
- * Optional precondition. Omit for a last-writer-wins upsert. Supply the version a prior read returned to make the write conditional; supply 0 to create only.
- */
-export type ExpectedVersion = number;
-/**
- * The version this write took. Supply it as `expectedVersion` on the next write to chain conditional updates without an intervening read.
- */
-export type Version = number;
 
-/**
- * Ecosystem-defined extension members per SPEC.md §4.5.1.
- */
-export interface Ext {
-  [k: string]: unknown | undefined;
-}
 /**
  * Success response to vta/app-state/put. Type https://trusttasks.org/spec/vta/app-state/put/1.0#response. A failed precondition is not a success: it is a trust-task-error carrying vta/app-state/put:versionConflict, whose details carry the maintainer's current version and value.
  */
@@ -61,6 +48,9 @@ export interface VTAApplicationStatePutResponsePayload {
   contextId: string;
   namespace: Namespace;
   key: Key;
+  /**
+   * The version this write took. Supply it as `expectedVersion` on the next write to chain conditional updates without an intervening read.
+   */
   version: Version;
   /**
    * True when no live record existed at the address beforehand — including when the address held a tombstone, since a tombstone is not a live record.
@@ -74,15 +64,15 @@ export interface VTAApplicationStatePutResponsePayload {
    * Size of the stored value in bytes as the maintainer measured it against its per-record cap. Lets a writer see how close it is to the limit before it hits it.
    */
   valueBytes?: number;
-  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.
+   */
+  ext?: Ext;
 }
 
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { ExpectedVersion, Ext, Key, Namespace, Version };
+
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/vta/app-state/put/1.0" as const;
 

package/src/vta/app-state/put-many/1.0/payload.ts

@@ -3,10 +3,9 @@
  * Source: specs/vta/app-state/put-many/1.0/payload.schema.json
  */
 
-/**
- * One namespace per batch. Atomicity is only meaningful within the counter the writes take their versions from, and that counter is per (contextId, namespace).
- */
-export type Namespace = string;
+import type { Ext, Key, Namespace, Version, WriteResult } from "../../../../_shared/components.js";
+
+
 /**
  * One write within the batch. Shaped exactly like a vta/app-state/put payload minus the context and namespace, which the batch supplies.
  */
@@ -17,22 +16,6 @@ export type Write =
   | {
       [k: string]: unknown | undefined;
     };
-/**
- * Application-chosen identifier for a record within a namespace. Opaque to the maintainer: it MUST NOT be parsed, normalized, or case-folded, and prefix matching in `list` is a byte-prefix comparison over the UTF-8 encoding. Applications SHOULD use `/`-delimited hierarchical keys (`community/acme`, `contact/z6Mk…`) so that `prefix` can address a record family, but the delimiter is a convention between an application and itself — the maintainer attaches no meaning to it.
- */
-export type Key = string;
-/**
- * The new version, on `written`.
- */
-export type Version = number;
-/**
- * On `conflict`: the version the maintainer actually holds. Absent when the conflict is that no record exists (`expectedVersion` was positive and the address is empty).
- */
-export type Version1 = number;
-/**
- * The namespace's counter value after the batch. A writer that is also a sync consumer can adopt this instead of issuing a list call to discover where its own writes landed.
- */
-export type Version2 = number;
 
 /**
  * Write up to 64 application-state records in one round trip, each carrying its own optimistic-concurrency precondition. The batch `mode` decides what a single failure costs: `independent` (the default) applies each write on its own merits, `atomic` applies all or none.
@@ -42,6 +25,9 @@ export interface VTAApplicationStatePutManyPayload {
    * The VTA context the records are scoped to; the isolation boundary.
    */
   contextId: string;
+  /**
+   * One namespace per batch. Atomicity is only meaningful within the counter the writes take their versions from, and that counter is per (contextId, namespace).
+   */
   namespace: Namespace;
   /**
    * `independent` applies each write on its own merits, so one conflicted record does not block the other nine — what a flush of unrelated edits wants, and why it is the default. `atomic` applies all or none, for records carrying a joint invariant. An atomic DEFAULT would let one stale record silently wedge an entire flush, and a caller could not tell a wedged flush from a slow one.
@@ -54,14 +40,11 @@ export interface VTAApplicationStatePutManyPayload {
    * @maxItems 64
    */
   writes: [Write, ...Write[]];
+  /**
+   * 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;
-}
 /**
  * Success response to vta/app-state/put-many in `independent` mode. Type https://trusttasks.org/spec/vta/app-state/put-many/1.0#response. A response is returned even when some writes conflicted, because the task did what it promised — applied each write on its own merits — and the per-record outcomes are the answer rather than the failure. An `atomic` batch that does not apply is a trust-task-error carrying vta/app-state/put-many:atomicBatchRejected, whose details carry the same per-record outcomes.
  */
@@ -77,50 +60,19 @@ export interface VTAApplicationStatePutManyResponsePayload {
    * @maxItems 64
    */
   results: [WriteResult, ...WriteResult[]];
-  highWatermark?: Version2;
-  ext?: Ext1;
-}
-/**
- * The outcome of one write within a `vta/app-state/put-many` batch. Per-record rather than per-batch, because the default batch mode applies each write on its own merits: a caller flushing ten unrelated edits needs to know which one conflicted, not merely that something did.
- */
-export interface WriteResult {
-  key: Key;
   /**
-   * `written`: applied, and `version` carries the new value. `conflict`: `expectedVersion` did not match; `currentVersion`, `currentValue` and `currentDeleted` carry the maintainer's view so the caller can resolve without a re-read. `tooLarge`: the value exceeded the per-record cap; `limitBytes` and `actualBytes` say by how much. `notFound`: a `mergePatch` write named an address with no live record. `skipped`: atomic mode only — this write was not attempted because another in the batch failed.
+   * The namespace's counter value after the batch. A writer that is also a sync consumer can adopt this instead of issuing a list call to discover where its own writes landed.
    */
-  outcome: "written" | "conflict" | "tooLarge" | "notFound" | "skipped";
-  version?: Version;
+  highWatermark?: Version;
   /**
-   * On `written`: true when no live record existed at the address beforehand.
+   * Ecosystem-defined extension members per SPEC.md §4.5.1.
    */
-  created?: boolean;
-  currentVersion?: Version1;
-  /**
-   * On `conflict`: the value the maintainer actually holds, returned WITH the rejection rather than left for the caller to re-read. A bare rejection has no fixed point under contention — between the rejection and the re-read the record can change again — so returning the winner's view removes the race rather than narrowing it. Absent when `currentDeleted` is true or no record exists.
-   */
-  currentValue?: {
-    [k: string]: unknown | undefined;
-  };
-  /**
-   * On `conflict`: true when the address holds a tombstone rather than a live record.
-   */
-  currentDeleted?: boolean;
-  /**
-   * On `tooLarge`: the maintainer's per-record cap in bytes.
-   */
-  limitBytes?: number;
-  /**
-   * On `tooLarge`: the size of the rejected value in bytes.
-   */
-  actualBytes?: number;
-}
-/**
- * Ecosystem-defined extension members per SPEC.md §4.5.1.
- */
-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, Key, Namespace, Version, WriteResult };
+
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/vta/app-state/put-many/1.0" as const;
 

package/src/vta/contexts/create/1.0/payload.ts

@@ -3,6 +3,9 @@
  * Source: specs/vta/contexts/create/1.0/payload.schema.json
  */
 
+import type { ContextRecord, Ext } from "../../../../_shared/components.js";
+
+
 export interface VTAContextsCreatePayload {
   /**
    * Id for the new context. When `parent` is present this is the leaf segment and the full id becomes `<parent>/<id>`; otherwise it is a top-level id. Must be unique within its parent — a collision is refused, never merged.
@@ -22,50 +25,9 @@ export interface VTAContextsCreatePayload {
   parent?: 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;
-}
-/**
- * A context as the VTA holds it.
- */
-export interface ContextRecord {
-  /**
-   * Context id. For a nested context this is the full path (`parent/leaf`), not the leaf alone — an ACL scope naming this context must use this value verbatim.
-   */
-  id: string;
-  /**
-   * Human-readable name. Operator-facing only; carries no authorization meaning, and two contexts may share a name.
-   */
-  name: string;
-  /**
-   * DID this context acts as, when one has been assigned. Absent means the context has no identity of its own yet — not that it has been denied one.
-   */
-  did?: string;
-  /**
-   * Free-form description.
-   */
-  description?: string;
-  /**
-   * Id of the context this one nests under. Absent for a top-level context. Authority granted at a parent reaches its children, so this member is load-bearing for anyone reasoning about scope.
-   */
-  parent?: string;
-  /**
-   * Resolved path from the root context, as the VTA derives it from the parent chain. Consumers MUST treat this as derived state: it is recomputed by the maintainer and is not independently settable.
-   */
-  basePath: string;
-  /**
-   * RFC 3339.
-   */
-  createdAt: string;
-  /**
-   * RFC 3339.
-   */
-  updatedAt: string;
-  ext?: Ext;
-}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { ContextRecord, Ext };
 
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/vta/contexts/create/1.0" as const;

package/src/vta/contexts/delete/1.0/payload.ts

@@ -3,6 +3,9 @@
  * Source: specs/vta/contexts/delete/1.0/payload.schema.json
  */
 
+import type { Ext } from "../../../../_shared/components.js";
+
+
 export interface VTAContextsDeletePayload {
   /**
    * Context to delete.
@@ -14,12 +17,6 @@ export interface VTAContextsDeletePayload {
   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;
-}
 /**
  * Success response to vta/contexts/delete. Type https://trusttasks.org/spec/vta/contexts/delete/1.0#response.
  */
@@ -32,6 +29,9 @@ export interface VTAContextsDeleteResponsePayload {
   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/vta/contexts/delete/1.0" as const;