@openvtc/trust-tasks 0.12.1 → 0.12.2

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

@@ -0,0 +1,584 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * 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;
+/**
+ * One write within the batch. Shaped exactly like a vta/app-state/put payload minus the context and namespace, which the batch supplies.
+ */
+export type Write =
+  | {
+      [k: string]: unknown | undefined;
+    }
+  | {
+      [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.
+ */
+export interface VTAApplicationStatePutManyPayload {
+  /**
+   * The VTA context the records are scoped to; the isolation boundary.
+   */
+  contextId: string;
+  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.
+   */
+  mode?: "independent" | "atomic";
+  /**
+   * The writes to apply. Keys MUST be distinct: two writes to one key in a batch have no defined order and are refused rather than serialised.
+   *
+   * @minItems 1
+   * @maxItems 64
+   */
+  writes: [Write, ...Write[]];
+  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.
+ */
+export interface VTAApplicationStatePutManyResponsePayload {
+  /**
+   * The mode the maintainer applied, echoed so a caller relying on the default sees what it got.
+   */
+  mode: "independent" | "atomic";
+  /**
+   * One result per requested write, in request order. Every write is accounted for.
+   *
+   * @minItems 1
+   * @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.
+   */
+  outcome: "written" | "conflict" | "tooLarge" | "notFound" | "skipped";
+  version?: Version;
+  /**
+   * On `written`: true when no live record existed at the address beforehand.
+   */
+  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;
+}
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/vta/app-state/put-many/1.0" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = VTAApplicationStatePutManyPayload;
+
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/vta/app-state/put-many/1.0#response" as const;
+
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = VTAApplicationStatePutManyResponsePayload;
+
+/**
+ * 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/app-state/put-many/1.0",
+  "title": "VTA Application State Put-Many — payload",
+  "description": "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.",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "contextId",
+    "namespace",
+    "writes"
+  ],
+  "properties": {
+    "contextId": {
+      "type": "string",
+      "minLength": 1,
+      "description": "The VTA context the records are scoped to; the isolation boundary."
+    },
+    "namespace": {
+      "$ref": "#/$defs/Namespace",
+      "description": "One namespace per batch. Atomicity is only meaningful within the counter the writes take their versions from, and that counter is per (contextId, namespace)."
+    },
+    "mode": {
+      "type": "string",
+      "enum": [
+        "independent",
+        "atomic"
+      ],
+      "default": "independent",
+      "description": "`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.",
+      "$comment": "The default is load-bearing rather than a convenience; see the spec's Abstract."
+    },
+    "writes": {
+      "type": "array",
+      "minItems": 1,
+      "maxItems": 64,
+      "items": {
+        "$ref": "#/$defs/Write"
+      },
+      "description": "The writes to apply. Keys MUST be distinct: two writes to one key in a batch have no defined order and are refused rather than serialised."
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext",
+      "description": "Ecosystem-defined extension members per SPEC.md §4.5.1."
+    }
+  },
+  "$defs": {
+    "Write": {
+      "title": "Write",
+      "description": "One write within the batch. Shaped exactly like a vta/app-state/put payload minus the context and namespace, which the batch supplies.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "key"
+      ],
+      "oneOf": [
+        {
+          "required": [
+            "value"
+          ],
+          "not": {
+            "required": [
+              "mergePatch"
+            ]
+          }
+        },
+        {
+          "required": [
+            "mergePatch"
+          ],
+          "not": {
+            "required": [
+              "value"
+            ]
+          }
+        }
+      ],
+      "properties": {
+        "key": {
+          "$ref": "#/$defs/Key"
+        },
+        "value": {
+          "description": "The complete new value, replacing whatever the record held. Any JSON value, including `null`. Mutually exclusive with `mergePatch`."
+        },
+        "mergePatch": {
+          "type": "object",
+          "description": "An RFC 7386 JSON Merge Patch applied to the record's current value. Requires a live record at the address; otherwise this write's outcome is `notFound`. Mutually exclusive with `value`."
+        },
+        "expectedVersion": {
+          "$ref": "#/$defs/ExpectedVersion",
+          "description": "This write's own precondition, evaluated independently of every other write in the batch. A positive value requires the record to be at exactly that version; 0 requires that no live record exists."
+        }
+      }
+    },
+    "Response": {
+      "$anchor": "response",
+      "title": "VTA Application State Put-Many — response payload",
+      "description": "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.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "mode",
+        "results"
+      ],
+      "properties": {
+        "mode": {
+          "type": "string",
+          "enum": [
+            "independent",
+            "atomic"
+          ],
+          "description": "The mode the maintainer applied, echoed so a caller relying on the default sees what it got."
+        },
+        "results": {
+          "type": "array",
+          "minItems": 1,
+          "maxItems": 64,
+          "items": {
+            "$ref": "#/$defs/WriteResult"
+          },
+          "description": "One result per requested write, in request order. Every write is accounted for."
+        },
+        "highWatermark": {
+          "$ref": "#/$defs/Version",
+          "description": "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."
+        },
+        "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-]+)+$"
+      }
+    },
+    "Version": {
+      "title": "Version",
+      "description": "A value of the namespace's monotonic write counter (see this schema's description). Server-assigned; a producer never chooses one.",
+      "type": "integer",
+      "minimum": 1
+    },
+    "WriteResult": {
+      "title": "WriteResult",
+      "description": "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.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "key",
+        "outcome"
+      ],
+      "properties": {
+        "key": {
+          "$ref": "#/$defs/Key"
+        },
+        "outcome": {
+          "type": "string",
+          "enum": [
+            "written",
+            "conflict",
+            "tooLarge",
+            "notFound",
+            "skipped"
+          ],
+          "description": "`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."
+        },
+        "version": {
+          "$ref": "#/$defs/Version",
+          "description": "The new version, on `written`."
+        },
+        "created": {
+          "type": "boolean",
+          "description": "On `written`: true when no live record existed at the address beforehand."
+        },
+        "currentVersion": {
+          "$ref": "#/$defs/Version",
+          "description": "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)."
+        },
+        "currentValue": {
+          "description": "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."
+        },
+        "currentDeleted": {
+          "type": "boolean",
+          "description": "On `conflict`: true when the address holds a tombstone rather than a live record."
+        },
+        "limitBytes": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "On `tooLarge`: the maintainer's per-record cap in bytes."
+        },
+        "actualBytes": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "On `tooLarge`: the size of the rejected value in bytes."
+        }
+      }
+    },
+    "Key": {
+      "title": "Key",
+      "description": "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.",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 512,
+      "pattern": "^[^\\u0000]+$"
+    },
+    "ExpectedVersion": {
+      "title": "ExpectedVersion",
+      "description": "Optimistic-concurrency precondition on a write. A positive value requires that the record's current `version` equals it exactly. Zero means \"create only\" — the write applies only if no LIVE record exists at the address, which is what makes lease acquisition safe: without it two instances can each read \"absent\", each write, and each believe it won. A tombstone is not a live record, so `expectedVersion: 0` succeeds over one; the created record takes the namespace's next counter value, which is necessarily greater than the tombstone's.",
+      "type": "integer",
+      "minimum": 0
+    },
+    "Namespace": {
+      "title": "Namespace",
+      "description": "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.",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 64,
+      "pattern": "^[a-z][a-z0-9]*(-[a-z0-9]+)*$"
+    }
+  }
+} 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": {
+    "Write": {
+      "title": "Write",
+      "description": "One write within the batch. Shaped exactly like a vta/app-state/put payload minus the context and namespace, which the batch supplies.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "key"
+      ],
+      "oneOf": [
+        {
+          "required": [
+            "value"
+          ],
+          "not": {
+            "required": [
+              "mergePatch"
+            ]
+          }
+        },
+        {
+          "required": [
+            "mergePatch"
+          ],
+          "not": {
+            "required": [
+              "value"
+            ]
+          }
+        }
+      ],
+      "properties": {
+        "key": {
+          "$ref": "#/$defs/Key"
+        },
+        "value": {
+          "description": "The complete new value, replacing whatever the record held. Any JSON value, including `null`. Mutually exclusive with `mergePatch`."
+        },
+        "mergePatch": {
+          "type": "object",
+          "description": "An RFC 7386 JSON Merge Patch applied to the record's current value. Requires a live record at the address; otherwise this write's outcome is `notFound`. Mutually exclusive with `value`."
+        },
+        "expectedVersion": {
+          "$ref": "#/$defs/ExpectedVersion",
+          "description": "This write's own precondition, evaluated independently of every other write in the batch. A positive value requires the record to be at exactly that version; 0 requires that no live record exists."
+        }
+      }
+    },
+    "Response": {
+      "$anchor": "response",
+      "title": "VTA Application State Put-Many — response payload",
+      "description": "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.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "mode",
+        "results"
+      ],
+      "properties": {
+        "mode": {
+          "type": "string",
+          "enum": [
+            "independent",
+            "atomic"
+          ],
+          "description": "The mode the maintainer applied, echoed so a caller relying on the default sees what it got."
+        },
+        "results": {
+          "type": "array",
+          "minItems": 1,
+          "maxItems": 64,
+          "items": {
+            "$ref": "#/$defs/WriteResult"
+          },
+          "description": "One result per requested write, in request order. Every write is accounted for."
+        },
+        "highWatermark": {
+          "$ref": "#/$defs/Version",
+          "description": "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."
+        },
+        "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-]+)+$"
+      }
+    },
+    "Version": {
+      "title": "Version",
+      "description": "A value of the namespace's monotonic write counter (see this schema's description). Server-assigned; a producer never chooses one.",
+      "type": "integer",
+      "minimum": 1
+    },
+    "WriteResult": {
+      "title": "WriteResult",
+      "description": "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.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "key",
+        "outcome"
+      ],
+      "properties": {
+        "key": {
+          "$ref": "#/$defs/Key"
+        },
+        "outcome": {
+          "type": "string",
+          "enum": [
+            "written",
+            "conflict",
+            "tooLarge",
+            "notFound",
+            "skipped"
+          ],
+          "description": "`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."
+        },
+        "version": {
+          "$ref": "#/$defs/Version",
+          "description": "The new version, on `written`."
+        },
+        "created": {
+          "type": "boolean",
+          "description": "On `written`: true when no live record existed at the address beforehand."
+        },
+        "currentVersion": {
+          "$ref": "#/$defs/Version",
+          "description": "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)."
+        },
+        "currentValue": {
+          "description": "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."
+        },
+        "currentDeleted": {
+          "type": "boolean",
+          "description": "On `conflict`: true when the address holds a tombstone rather than a live record."
+        },
+        "limitBytes": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "On `tooLarge`: the maintainer's per-record cap in bytes."
+        },
+        "actualBytes": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "On `tooLarge`: the size of the rejected value in bytes."
+        }
+      }
+    },
+    "Key": {
+      "title": "Key",
+      "description": "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.",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 512,
+      "pattern": "^[^\\u0000]+$"
+    },
+    "ExpectedVersion": {
+      "title": "ExpectedVersion",
+      "description": "Optimistic-concurrency precondition on a write. A positive value requires that the record's current `version` equals it exactly. Zero means \"create only\" — the write applies only if no LIVE record exists at the address, which is what makes lease acquisition safe: without it two instances can each read \"absent\", each write, and each believe it won. A tombstone is not a live record, so `expectedVersion: 0` succeeds over one; the created record takes the namespace's next counter value, which is necessarily greater than the tombstone's.",
+      "type": "integer",
+      "minimum": 0
+    },
+    "Namespace": {
+      "title": "Namespace",
+      "description": "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.",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 64,
+      "pattern": "^[a-z][a-z0-9]*(-[a-z0-9]+)*$"
+    }
+  }
+} 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: true,
+  isRecipientRequired: 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,
+  payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
+} as const;