@openvtc/trust-tasks 0.28.24 → 0.28.26

package/src/vta/memory/list/0.3/payload.ts

@@ -0,0 +1,491 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vta/memory/list/0.3/payload.schema.json
+ */
+
+import type { Ext, MemoryKey, MemoryPurpose, MemoryRecord, MemoryValue, MemoryVersion, Purpose_AclV0_3 as Purpose, Purpose_AclV0_31, Purpose_AclV0_32 } from "../../../../_shared/components.js";
+
+
+/**
+ * Enumerate the memory items in a context. Two modes, distinguished by whether `sinceVersion` is supplied. Without it this is a SNAPSHOT of live items, optionally narrowed by `prefix`. With it this is a CHANGE FEED: every item in the context whose version exceeds the watermark, tombstones included, which is what lets an agent's local cache on another device converge. Pagination is opaque-cursor based.
+ */
+export interface VTAMemoryListPayload {
+  /**
+   * The VTA context to enumerate; the isolation boundary.
+   */
+  contextId: string;
+  /**
+   * Restrict to items whose `key` begins with this byte prefix, compared over the UTF-8 encoding. Lets an agent recall one family of items — `contact/`, `preference/` — without dragging the whole context through the response.
+   */
+  prefix?: string;
+  /**
+   * Watermark. Selects change-feed mode: only items whose `version` is strictly greater are returned, tombstones included. Supply the `highWatermark` from the previous sync, or 0 for a first full pull in change-feed form.
+   */
+  sinceVersion?: number;
+  /**
+   * When true, each returned item carries its `value`. Defaults to TRUE — unlike vta/app-state/list — because recalling the text is what an agent lists memory for, and 0.1 always returned values. Set it false for the metadata view (key, version, timestamps, `valueBytes`), which makes a scan of a large context cheap.
+   */
+  includeValues?: boolean;
+  /**
+   * Snapshot mode only: when true, tombstones still inside the retention window are returned alongside live items. Defaults to false. In change-feed mode tombstones are always returned and this member MUST NOT be set to false — a change feed that omits deletions cannot converge.
+   */
+  includeDeleted?: boolean;
+  /**
+   * An opaque continuation token from a previous response's `nextCursor`; a responder MUST NOT accept a cursor it did not issue. Consumers MUST treat it as opaque: never construct, decode, mutate, or infer meaning from one.
+   */
+  cursor?: string;
+  /**
+   * The most items to return; the responder chooses a default and MAY return fewer, which is likely when `includeValues` is in effect and the values are large.
+   */
+  limit?: number;
+  /**
+   * OPTIONAL. The one purpose the caller will use the content this request discloses for (VTI-ACL-103). Granted only as the caller's ACL entry grants it; a purpose the entry does not grant is refused with `purposeNotGranted`. May be omitted where the entry lists exactly one purpose, or states `any`.
+   */
+  purpose?: MemoryPurpose;
+  /**
+   * Ecosystem-defined extension members per SPEC.md §4.5.1.
+   */
+  ext?: Ext;
+}
+/**
+ * Success response to vta/memory/list. Type https://trusttasks.org/spec/vta/memory/list/0.3#response.
+ */
+export interface VTAMemoryListResponsePayload {
+  /**
+   * Matching items in ascending key order in snapshot mode, and ascending version order in change-feed mode — the latter so that a consumer applying them in order reaches the same state as the maintainer. May be empty.
+   */
+  items: MemoryRecord[];
+  /**
+   * Opaque continuation token for the next page, sent back as the request's `cursor`. Present when more matching items exist beyond this page; absent on the last page.
+   */
+  nextCursor?: string;
+  /**
+   * The context's current counter value; 0 for a context that has never been written. This is what a consumer stores as its next `sinceVersion` — NOT the maximum version among `items`, 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 — the one with no `nextCursor` — because the pages of one feed share this value and adopting it early would skip the items still to come.
+   */
+  highWatermark: number;
+  /**
+   * How long this maintainer retains tombstones before reaping them. Advisory, so a consumer can schedule its syncs to stay inside the window rather than discovering it has fallen out of it via vta/memory/list:watermarkTooOld.
+   */
+  tombstoneRetentionSeconds?: number;
+  /**
+   * 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 { Ext, MemoryKey, MemoryPurpose, MemoryRecord, MemoryValue, MemoryVersion, Purpose, Purpose_AclV0_31, Purpose_AclV0_32 };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/vta/memory/list/0.3" as const;
+
+/**
+ * The earlier version of this specification that this one declares it
+ * extends (front matter `extends`, SPEC §5.2 "Declared extension"), or
+ * `null`. Only the direct declaration — follow the chain with
+ * `extendsChain` / `readForSpec`.
+ */
+export const EXTENDS: string | null = "0.2";
+
+/**
+ * Why this version is deprecated, or `null` while it is current. A
+ * superseded or retired version is still supported, and is withdrawn from
+ * this package in a later scheduled batch (SPEC "Superseded and Withdrawn
+ * Versions").
+ */
+export const DEPRECATION: string | null = null;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = VTAMemoryListPayload;
+
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/vta/memory/list/0.3#response" as const;
+
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = VTAMemoryListResponsePayload;
+
+/**
+ * This specification's payload schema, as a value.
+ *
+ * SPEC.md §7.2 item 2 is performed against this. It is shipped as data
+ * rather than only as a `.json` file because TypeScript types are erased
+ * at runtime: without a schema a consumer has nothing to validate, and
+ * every REQUIRED payload member is optional in practice. Cross-file
+ * `$ref`s are already inlined, so it needs no resolver.
+ */
+export const PAYLOAD_SCHEMA = {
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://trusttasks.org/spec/vta/memory/list/0.3",
+  "title": "VTA Memory List — payload",
+  "description": "Enumerate the memory items in a context. Two modes, distinguished by whether `sinceVersion` is supplied. Without it this is a SNAPSHOT of live items, optionally narrowed by `prefix`. With it this is a CHANGE FEED: every item in the context whose version exceeds the watermark, tombstones included, which is what lets an agent's local cache on another device converge. Pagination is opaque-cursor based.",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "contextId"
+  ],
+  "properties": {
+    "contextId": {
+      "type": "string",
+      "minLength": 1,
+      "description": "The VTA context to enumerate; the isolation boundary."
+    },
+    "prefix": {
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 512,
+      "description": "Restrict to items whose `key` begins with this byte prefix, compared over the UTF-8 encoding. Lets an agent recall one family of items — `contact/`, `preference/` — without dragging the whole context through the response."
+    },
+    "sinceVersion": {
+      "type": "integer",
+      "minimum": 0,
+      "description": "Watermark. Selects change-feed mode: only items whose `version` is strictly greater are returned, tombstones included. Supply the `highWatermark` from the previous sync, or 0 for a first full pull in change-feed form."
+    },
+    "includeValues": {
+      "type": "boolean",
+      "description": "When true, each returned item carries its `value`. Defaults to TRUE — unlike vta/app-state/list — because recalling the text is what an agent lists memory for, and 0.1 always returned values. Set it false for the metadata view (key, version, timestamps, `valueBytes`), which makes a scan of a large context cheap."
+    },
+    "includeDeleted": {
+      "type": "boolean",
+      "description": "Snapshot mode only: when true, tombstones still inside the retention window are returned alongside live items. Defaults to false. In change-feed mode tombstones are always returned and this member MUST NOT be set to false — a change feed that omits deletions cannot converge."
+    },
+    "cursor": {
+      "type": "string",
+      "description": "An opaque continuation token from a previous response's `nextCursor`; a responder MUST NOT accept a cursor it did not issue. Consumers MUST treat it as opaque: never construct, decode, mutate, or infer meaning from one."
+    },
+    "limit": {
+      "type": "integer",
+      "minimum": 1,
+      "maximum": 1000,
+      "description": "The most items to return; the responder chooses a default and MAY return fewer, which is likely when `includeValues` is in effect and the values are large."
+    },
+    "purpose": {
+      "$ref": "#/$defs/MemoryPurpose",
+      "description": "OPTIONAL. The one purpose the caller will use the content this request discloses for (VTI-ACL-103). Granted only as the caller's ACL entry grants it; a purpose the entry does not grant is refused with `purposeNotGranted`. May be omitted where the entry lists exactly one purpose, or states `any`."
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext",
+      "description": "Ecosystem-defined extension members per SPEC.md §4.5.1."
+    }
+  },
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "VTA Memory List — response payload",
+      "description": "Success response to vta/memory/list. Type https://trusttasks.org/spec/vta/memory/list/0.3#response.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "items",
+        "highWatermark"
+      ],
+      "properties": {
+        "items": {
+          "type": "array",
+          "items": {
+            "$ref": "#/$defs/MemoryRecord"
+          },
+          "description": "Matching items in ascending key order in snapshot mode, and ascending version order in change-feed mode — the latter so that a consumer applying them in order reaches the same state as the maintainer. May be empty."
+        },
+        "nextCursor": {
+          "type": "string",
+          "description": "Opaque continuation token for the next page, sent back as the request's `cursor`. Present when more matching items exist beyond this page; absent on the last page."
+        },
+        "highWatermark": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "The context's current counter value; 0 for a context that has never been written. This is what a consumer stores as its next `sinceVersion` — NOT the maximum version among `items`, 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 — the one with no `nextCursor` — because the pages of one feed share this value and adopting it early would skip the items still to come."
+        },
+        "tombstoneRetentionSeconds": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "How long this maintainer retains tombstones before reaping them. Advisory, so a consumer can schedule its syncs to stay inside the window rather than discovering it has fallen out of it via vta/memory/list:watermarkTooOld."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext",
+          "description": "Ecosystem-defined extension members per SPEC.md §4.5.1."
+        }
+      }
+    },
+    "Ext": {
+      "title": "Ext",
+      "description": "Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a reverse-DNS namespace; structure under each namespace is opaque to the framework.",
+      "type": "object",
+      "minProperties": 1,
+      "additionalProperties": true,
+      "propertyNames": {
+        "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
+      }
+    },
+    "MemoryRecord": {
+      "title": "MemoryRecord",
+      "description": "A memory item as the maintainer holds it. `value` is absent in two distinct situations and a consumer MUST NOT conflate them: the item is a tombstone (`deleted` is true), or the caller asked for a metadata-only view (`vta/memory/list` without `includeValues`). This is why `deleted` is required rather than defaulted — a consumer that infers deletion from an absent value gets the tombstone case wrong exactly when convergence depends on it.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "contextId",
+        "key",
+        "version",
+        "deleted",
+        "updatedAt"
+      ],
+      "properties": {
+        "contextId": {
+          "type": "string",
+          "minLength": 1,
+          "description": "The VTA context the item is scoped to; the isolation boundary."
+        },
+        "key": {
+          "$ref": "#/$defs/MemoryKey"
+        },
+        "version": {
+          "$ref": "#/$defs/MemoryVersion",
+          "description": "The context counter value this item's most recent write took. Supply it as `expectedVersion` on the next write to make that write conditional on nothing having changed in between."
+        },
+        "value": {
+          "$ref": "#/$defs/MemoryValue",
+          "description": "The remembered text. Absent when this is a tombstone or a metadata-only view."
+        },
+        "valueBytes": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "Size of the stored value in bytes over its UTF-8 encoding, as the maintainer measures it for the per-item cap. Present in metadata-only views so a consumer can decide what to fetch without fetching it; absent on a tombstone."
+        },
+        "deleted": {
+          "type": "boolean",
+          "description": "True when this is a tombstone: the item 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/memory/list`."
+        },
+        "createdAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When the item was first created at this key. MAY be absent on a tombstone whose body has been discarded, and on an item written before the maintainer kept versions."
+        },
+        "updatedAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When the write that produced this `version` was applied. For a tombstone, when the delete was applied."
+        },
+        "deletedAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When the item was deleted. Present only when `deleted` is true; equal to `updatedAt` for a tombstone the maintainer has not since rewritten."
+        }
+      }
+    },
+    "MemoryValue": {
+      "title": "MemoryValue",
+      "description": "The remembered text: a fact, a summary, a preference. Opaque to the maintainer, which stores it as given and never interprets, rewrites or summarises it. The maintainer enforces a documented per-item cap on its size (see `vta/memory/put`).",
+      "type": "string"
+    },
+    "MemoryVersion": {
+      "title": "MemoryVersion",
+      "description": "A value of the context's monotonic write counter (see this schema's description). Server-assigned; a producer never chooses one.",
+      "type": "integer",
+      "minimum": 1
+    },
+    "MemoryKey": {
+      "title": "MemoryKey",
+      "description": "Agent-chosen identifier for an item within a context. Opaque to the maintainer: it MUST NOT be parsed, normalized, or case-folded, and prefix matching in `vta/memory/list` is a byte-prefix comparison over the UTF-8 encoding. Agents SHOULD use `/`-delimited hierarchical keys (`contact/billing`, `preference/timezone`) so that `prefix` can address a family of items, but the delimiter is a convention between an agent and itself. A key is content as well as an address: a key naming a person, a condition or a dispute discloses something to anyone who can list the context, even without its value.",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 512,
+      "pattern": "^[^\\u0000]+$"
+    },
+    "MemoryPurpose": {
+      "title": "MemoryPurpose",
+      "description": "The one purpose for which the caller will use the memory content a request discloses (VTI-ACL-103): a name registered in the VTI specification's purpose registry (`personalisation`, `taskExecution`, `analytics`, `modelTraining`) or an absolute IRI. The VTA grants it only if the caller's ACL entry does — `any` grants every purpose but `modelTraining` — refuses it otherwise (`purposeNotGranted`), and records it in the audit record of the read. Optional where the entry lists exactly one purpose (that one applies) or states `any` (the read is recorded as for no stated purpose).",
+      "$ref": "#/$defs/Purpose"
+    },
+    "Purpose": {
+      "title": "Purpose",
+      "description": "What content is used for: a lowerCamelCase name registered in the VTI specification's purpose registry (Appendix H) — `personalisation`, `taskExecution`, `analytics`, `modelTraining` at the time of writing — or an absolute IRI naming a purpose defined elsewhere, such as a purpose of the W3C Data Privacy Vocabulary (`https://w3id.org/dpv#ServicePersonalisation`). Compared by exact string equality: a consumer MUST NOT treat a purpose it does not recognise as equal to any other, and grants only a request naming exactly a listed purpose (VTI-ACL-109). A registered name is never an IRI, because it contains no `:`.",
+      "type": "string",
+      "maxLength": 2048,
+      "anyOf": [
+        {
+          "pattern": "^[a-z][a-zA-Z0-9]{0,63}$"
+        },
+        {
+          "pattern": "^[a-zA-Z][a-zA-Z0-9+.-]*:[^\\s]+$"
+        }
+      ]
+    }
+  }
+} as const;
+
+/** As {@link PAYLOAD_SCHEMA}, for the success-response variant. */
+export const RESPONSE_PAYLOAD_SCHEMA = {
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$ref": "#/$defs/Response",
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "VTA Memory List — response payload",
+      "description": "Success response to vta/memory/list. Type https://trusttasks.org/spec/vta/memory/list/0.3#response.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "items",
+        "highWatermark"
+      ],
+      "properties": {
+        "items": {
+          "type": "array",
+          "items": {
+            "$ref": "#/$defs/MemoryRecord"
+          },
+          "description": "Matching items in ascending key order in snapshot mode, and ascending version order in change-feed mode — the latter so that a consumer applying them in order reaches the same state as the maintainer. May be empty."
+        },
+        "nextCursor": {
+          "type": "string",
+          "description": "Opaque continuation token for the next page, sent back as the request's `cursor`. Present when more matching items exist beyond this page; absent on the last page."
+        },
+        "highWatermark": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "The context's current counter value; 0 for a context that has never been written. This is what a consumer stores as its next `sinceVersion` — NOT the maximum version among `items`, 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 — the one with no `nextCursor` — because the pages of one feed share this value and adopting it early would skip the items still to come."
+        },
+        "tombstoneRetentionSeconds": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "How long this maintainer retains tombstones before reaping them. Advisory, so a consumer can schedule its syncs to stay inside the window rather than discovering it has fallen out of it via vta/memory/list:watermarkTooOld."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext",
+          "description": "Ecosystem-defined extension members per SPEC.md §4.5.1."
+        }
+      }
+    },
+    "Ext": {
+      "title": "Ext",
+      "description": "Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a reverse-DNS namespace; structure under each namespace is opaque to the framework.",
+      "type": "object",
+      "minProperties": 1,
+      "additionalProperties": true,
+      "propertyNames": {
+        "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
+      }
+    },
+    "MemoryRecord": {
+      "title": "MemoryRecord",
+      "description": "A memory item as the maintainer holds it. `value` is absent in two distinct situations and a consumer MUST NOT conflate them: the item is a tombstone (`deleted` is true), or the caller asked for a metadata-only view (`vta/memory/list` without `includeValues`). This is why `deleted` is required rather than defaulted — a consumer that infers deletion from an absent value gets the tombstone case wrong exactly when convergence depends on it.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "contextId",
+        "key",
+        "version",
+        "deleted",
+        "updatedAt"
+      ],
+      "properties": {
+        "contextId": {
+          "type": "string",
+          "minLength": 1,
+          "description": "The VTA context the item is scoped to; the isolation boundary."
+        },
+        "key": {
+          "$ref": "#/$defs/MemoryKey"
+        },
+        "version": {
+          "$ref": "#/$defs/MemoryVersion",
+          "description": "The context counter value this item's most recent write took. Supply it as `expectedVersion` on the next write to make that write conditional on nothing having changed in between."
+        },
+        "value": {
+          "$ref": "#/$defs/MemoryValue",
+          "description": "The remembered text. Absent when this is a tombstone or a metadata-only view."
+        },
+        "valueBytes": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "Size of the stored value in bytes over its UTF-8 encoding, as the maintainer measures it for the per-item cap. Present in metadata-only views so a consumer can decide what to fetch without fetching it; absent on a tombstone."
+        },
+        "deleted": {
+          "type": "boolean",
+          "description": "True when this is a tombstone: the item 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/memory/list`."
+        },
+        "createdAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When the item was first created at this key. MAY be absent on a tombstone whose body has been discarded, and on an item written before the maintainer kept versions."
+        },
+        "updatedAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When the write that produced this `version` was applied. For a tombstone, when the delete was applied."
+        },
+        "deletedAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When the item was deleted. Present only when `deleted` is true; equal to `updatedAt` for a tombstone the maintainer has not since rewritten."
+        }
+      }
+    },
+    "MemoryValue": {
+      "title": "MemoryValue",
+      "description": "The remembered text: a fact, a summary, a preference. Opaque to the maintainer, which stores it as given and never interprets, rewrites or summarises it. The maintainer enforces a documented per-item cap on its size (see `vta/memory/put`).",
+      "type": "string"
+    },
+    "MemoryVersion": {
+      "title": "MemoryVersion",
+      "description": "A value of the context's monotonic write counter (see this schema's description). Server-assigned; a producer never chooses one.",
+      "type": "integer",
+      "minimum": 1
+    },
+    "MemoryKey": {
+      "title": "MemoryKey",
+      "description": "Agent-chosen identifier for an item within a context. Opaque to the maintainer: it MUST NOT be parsed, normalized, or case-folded, and prefix matching in `vta/memory/list` is a byte-prefix comparison over the UTF-8 encoding. Agents SHOULD use `/`-delimited hierarchical keys (`contact/billing`, `preference/timezone`) so that `prefix` can address a family of items, but the delimiter is a convention between an agent and itself. A key is content as well as an address: a key naming a person, a condition or a dispute discloses something to anyone who can list the context, even without its value.",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 512,
+      "pattern": "^[^\\u0000]+$"
+    },
+    "MemoryPurpose": {
+      "title": "MemoryPurpose",
+      "description": "The one purpose for which the caller will use the memory content a request discloses (VTI-ACL-103): a name registered in the VTI specification's purpose registry (`personalisation`, `taskExecution`, `analytics`, `modelTraining`) or an absolute IRI. The VTA grants it only if the caller's ACL entry does — `any` grants every purpose but `modelTraining` — refuses it otherwise (`purposeNotGranted`), and records it in the audit record of the read. Optional where the entry lists exactly one purpose (that one applies) or states `any` (the read is recorded as for no stated purpose).",
+      "$ref": "#/$defs/Purpose"
+    },
+    "Purpose": {
+      "title": "Purpose",
+      "description": "What content is used for: a lowerCamelCase name registered in the VTI specification's purpose registry (Appendix H) — `personalisation`, `taskExecution`, `analytics`, `modelTraining` at the time of writing — or an absolute IRI naming a purpose defined elsewhere, such as a purpose of the W3C Data Privacy Vocabulary (`https://w3id.org/dpv#ServicePersonalisation`). Compared by exact string equality: a consumer MUST NOT treat a purpose it does not recognise as equal to any other, and grants only a request naming exactly a listed purpose (VTI-ACL-109). A registered name is never an IRI, because it contains no `:`.",
+      "type": "string",
+      "maxLength": 2048,
+      "anyOf": [
+        {
+          "pattern": "^[a-z][a-zA-Z0-9]{0,63}$"
+        },
+        {
+          "pattern": "^[a-zA-Z][a-zA-Z0-9+.-]*:[^\\s]+$"
+        }
+      ]
+    }
+  }
+} as const;
+
+/**
+ * SPEC.md §7.2 policy for the request variant, from this specification's
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
+ * per-specification and cannot be derived from the document alone, and
+ * item 2 needs the schema this carries.
+ */
+export const SPEC = {
+  typeUri: TYPE_URI,
+  isBearer: false,
+  isProofRequired: false,
+  isRecipientRequired: true,
+  isIssuedAtRequired: true,
+  payloadSchema: PAYLOAD_SCHEMA,
+} as const;
+
+/**
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
+ * tracks the *issuer* party's requirement because a response swaps the
+ * parties (§7.3 item 5).
+ */
+export const RESPONSE_SPEC = {
+  typeUri: RESPONSE_TYPE_URI,
+  isBearer: false,
+  isProofRequired: true,
+  isRecipientRequired: true,
+  isIssuedAtRequired: true,
+  payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
+} as const;

package/src/vta/memory/put/0.1/payload.ts

@@ -6,7 +6,7 @@
 import type { Ext } from "../../../../_shared/components.js";
 
 
-/** @deprecated superseded by vta/memory/put/0.2 */
+/** @deprecated superseded by vta/memory/put/0.3 */
 export interface VTAMemoryPutPayload {
   /**
    * The VTA context the memory item is scoped to (the isolation boundary).
@@ -28,7 +28,7 @@ export interface VTAMemoryPutPayload {
 /**
  * Success response to vta/memory/put. Type https://trusttasks.org/spec/vta/memory/put/0.1#response.
  *
- * @deprecated superseded by vta/memory/put/0.2
+ * @deprecated superseded by vta/memory/put/0.3
  */
 export interface VTAMemoryPutResponsePayload {
   /**
@@ -58,12 +58,12 @@ export const EXTENDS: string | null = null;
  * this package in a later scheduled batch (SPEC "Superseded and Withdrawn
  * Versions").
  */
-export const DEPRECATION: string | null = "superseded by vta/memory/put/0.2";
+export const DEPRECATION: string | null = "superseded by vta/memory/put/0.3";
 
 /**
  * Stable alias for this specification's request payload shape.
  *
- * @deprecated superseded by vta/memory/put/0.2
+ * @deprecated superseded by vta/memory/put/0.3
  */
 export type Payload = VTAMemoryPutPayload;
 
@@ -73,7 +73,7 @@ export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/vta/memory/put/0.1
 /**
  * Stable alias for this specification's success-response payload shape.
  *
- * @deprecated superseded by vta/memory/put/0.2
+ * @deprecated superseded by vta/memory/put/0.3
  */
 export type Response = VTAMemoryPutResponsePayload;
 

package/src/vta/memory/put/0.2/payload.ts

@@ -8,6 +8,8 @@ import type { Ext, MemoryExpectedVersion, MemoryKey, MemoryValue, MemoryVersion
 
 /**
  * Store one memory item at its `(contextId, key)` address. `expectedVersion` makes the write conditional: a positive value requires the item to be at exactly that version, and zero requires that no live item exists.
+ *
+ * @deprecated superseded by vta/memory/put/0.3
  */
 export interface VTAMemoryPutPayload {
   /**
@@ -27,6 +29,8 @@ export interface VTAMemoryPutPayload {
 }
 /**
  * Success response to vta/memory/put. Type https://trusttasks.org/spec/vta/memory/put/0.2#response. A failed precondition is not a success: it is a trust-task-error carrying vta/memory/put:versionConflict, whose details carry the maintainer's current version and value.
+ *
+ * @deprecated superseded by vta/memory/put/0.3
  */
 export interface VTAMemoryPutResponsePayload {
   /**
@@ -76,15 +80,23 @@ export const EXTENDS: string | null = null;
  * this package in a later scheduled batch (SPEC "Superseded and Withdrawn
  * Versions").
  */
-export const DEPRECATION: string | null = null;
+export const DEPRECATION: string | null = "superseded by vta/memory/put/0.3";
 
-/** Stable alias for this specification's request payload shape. */
+/**
+ * Stable alias for this specification's request payload shape.
+ *
+ * @deprecated superseded by vta/memory/put/0.3
+ */
 export type Payload = VTAMemoryPutPayload;
 
 /** Trust Task response type URI (request type URI + "#response"). */
 export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/vta/memory/put/0.2#response" as const;
 
-/** Stable alias for this specification's success-response payload shape. */
+/**
+ * Stable alias for this specification's success-response payload shape.
+ *
+ * @deprecated superseded by vta/memory/put/0.3
+ */
 export type Response = VTAMemoryPutResponsePayload;
 
 /**