@openvtc/trust-tasks 0.12.0 → 0.12.2

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

@@ -0,0 +1,716 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * 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;
+/**
+ * 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.
+ */
+export interface VTAApplicationStateGetManyPayload {
+    /**
+     * The VTA context the records are scoped to; the isolation boundary.
+     */
+    contextId: string;
+    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.
+     *
+     * @minItems 1
+     * @maxItems 256
+     */
+    keys: [Key, ...Key[]];
+    /**
+     * Defaults to false. When true, an address holding a tombstone yields a record with `deleted: true` rather than appearing in `missing`.
+     */
+    includeDeleted?: boolean;
+    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.
+ */
+export interface VTAApplicationStateGetManyResponsePayload {
+    /**
+     * The records found, each with its `value`, in the order the keys were requested. May be empty.
+     */
+    records: AppStateRecord[];
+    /**
+     * Requested keys holding no record — and, unless `includeDeleted` was set, keys holding only a tombstone. Reported rather than silently omitted, so a caller need not diff the request against the response to notice.
+     */
+    missing: Key[];
+    /**
+     * 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.
+     */
+    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;
+}
+/** Trust Task type URI. */
+export declare const TYPE_URI: "https://trusttasks.org/spec/vta/app-state/get-many/1.0";
+/** Stable alias for this specification's request payload shape. */
+export type Payload = VTAApplicationStateGetManyPayload;
+/** Trust Task response type URI (request type URI + "#response"). */
+export declare const RESPONSE_TYPE_URI: "https://trusttasks.org/spec/vta/app-state/get-many/1.0#response";
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = VTAApplicationStateGetManyResponsePayload;
+/**
+ * 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 declare const PAYLOAD_SCHEMA: {
+    readonly $schema: "https://json-schema.org/draft/2020-12/schema";
+    readonly $id: "https://trusttasks.org/spec/vta/app-state/get-many/1.0";
+    readonly title: "VTA Application State Get-Many — payload";
+    readonly description: "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.";
+    readonly type: "object";
+    readonly additionalProperties: false;
+    readonly required: readonly ["contextId", "namespace", "keys"];
+    readonly properties: {
+        readonly contextId: {
+            readonly type: "string";
+            readonly minLength: 1;
+            readonly description: "The VTA context the records are scoped to; the isolation boundary.";
+        };
+        readonly namespace: {
+            readonly $ref: "#/$defs/Namespace";
+            readonly description: "Required, unlike in list: a batch read addresses records by key, and a key is only unique within a namespace.";
+        };
+        readonly keys: {
+            readonly type: "array";
+            readonly minItems: 1;
+            readonly maxItems: 256;
+            readonly uniqueItems: true;
+            readonly items: {
+                readonly $ref: "#/$defs/Key";
+            };
+            readonly description: "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.";
+        };
+        readonly includeDeleted: {
+            readonly type: "boolean";
+            readonly description: "Defaults to false. When true, an address holding a tombstone yields a record with `deleted: true` rather than appearing in `missing`.";
+        };
+        readonly ext: {
+            readonly $ref: "#/$defs/Ext";
+            readonly description: "Ecosystem-defined extension members per SPEC.md §4.5.1.";
+        };
+    };
+    readonly $defs: {
+        readonly Response: {
+            readonly $anchor: "response";
+            readonly title: "VTA Application State Get-Many — response payload";
+            readonly description: "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.";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["records", "missing"];
+            readonly properties: {
+                readonly records: {
+                    readonly type: "array";
+                    readonly items: {
+                        readonly $ref: "#/$defs/AppStateRecord";
+                    };
+                    readonly description: "The records found, each with its `value`, in the order the keys were requested. May be empty.";
+                };
+                readonly missing: {
+                    readonly type: "array";
+                    readonly items: {
+                        readonly $ref: "#/$defs/Key";
+                    };
+                    readonly description: "Requested keys holding no record — and, unless `includeDeleted` was set, keys holding only a tombstone. Reported rather than silently omitted, so a caller need not diff the request against the response to notice.";
+                };
+                readonly deferred: {
+                    readonly type: "array";
+                    readonly items: {
+                        readonly $ref: "#/$defs/Key";
+                    };
+                    readonly description: "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.";
+                };
+                readonly ext: {
+                    readonly $ref: "#/$defs/Ext";
+                    readonly description: "Ecosystem-defined extension members per SPEC.md §4.5.1.";
+                };
+            };
+        };
+        readonly Ext: {
+            readonly title: "Ext";
+            readonly 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.";
+            readonly type: "object";
+            readonly minProperties: 1;
+            readonly additionalProperties: true;
+            readonly propertyNames: {
+                readonly pattern: "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$";
+            };
+        };
+        readonly Key: {
+            readonly title: "Key";
+            readonly 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.";
+            readonly type: "string";
+            readonly minLength: 1;
+            readonly maxLength: 512;
+            readonly pattern: "^[^\\u0000]+$";
+        };
+        readonly AppStateRecord: {
+            readonly title: "AppStateRecord";
+            readonly description: "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.";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["contextId", "namespace", "key", "version", "deleted", "updatedAt"];
+            readonly properties: {
+                readonly contextId: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly description: "The VTA context the record is scoped to; the isolation boundary.";
+                };
+                readonly namespace: {
+                    readonly $ref: "#/$defs/Namespace";
+                };
+                readonly key: {
+                    readonly $ref: "#/$defs/Key";
+                };
+                readonly version: {
+                    readonly $ref: "#/$defs/Version";
+                    readonly description: "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.";
+                };
+                readonly value: {
+                    readonly description: "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.";
+                };
+                readonly valueBytes: {
+                    readonly type: "integer";
+                    readonly minimum: 0;
+                    readonly description: "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.";
+                };
+                readonly deleted: {
+                    readonly type: "boolean";
+                    readonly description: "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`.";
+                };
+                readonly createdAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                    readonly description: "When the record was first created at this address. MAY be absent on a tombstone whose body has been discarded.";
+                };
+                readonly updatedAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                    readonly description: "When the write that produced this `version` was applied. For a tombstone, when the delete was applied.";
+                };
+                readonly deletedAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                    readonly description: "When the record was deleted. Present only when `deleted` is true; equal to `updatedAt` for a tombstone the maintainer has not since rewritten.";
+                };
+            };
+        };
+        readonly Version: {
+            readonly title: "Version";
+            readonly description: "A value of the namespace's monotonic write counter (see this schema's description). Server-assigned; a producer never chooses one.";
+            readonly type: "integer";
+            readonly minimum: 1;
+        };
+        readonly Namespace: {
+            readonly title: "Namespace";
+            readonly 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.";
+            readonly type: "string";
+            readonly minLength: 1;
+            readonly maxLength: 64;
+            readonly pattern: "^[a-z][a-z0-9]*(-[a-z0-9]+)*$";
+        };
+    };
+};
+/** As {@link PAYLOAD_SCHEMA}, for the success-response variant. */
+export declare const RESPONSE_PAYLOAD_SCHEMA: {
+    readonly $schema: "https://json-schema.org/draft/2020-12/schema";
+    readonly $ref: "#/$defs/Response";
+    readonly $defs: {
+        readonly Response: {
+            readonly $anchor: "response";
+            readonly title: "VTA Application State Get-Many — response payload";
+            readonly description: "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.";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["records", "missing"];
+            readonly properties: {
+                readonly records: {
+                    readonly type: "array";
+                    readonly items: {
+                        readonly $ref: "#/$defs/AppStateRecord";
+                    };
+                    readonly description: "The records found, each with its `value`, in the order the keys were requested. May be empty.";
+                };
+                readonly missing: {
+                    readonly type: "array";
+                    readonly items: {
+                        readonly $ref: "#/$defs/Key";
+                    };
+                    readonly description: "Requested keys holding no record — and, unless `includeDeleted` was set, keys holding only a tombstone. Reported rather than silently omitted, so a caller need not diff the request against the response to notice.";
+                };
+                readonly deferred: {
+                    readonly type: "array";
+                    readonly items: {
+                        readonly $ref: "#/$defs/Key";
+                    };
+                    readonly description: "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.";
+                };
+                readonly ext: {
+                    readonly $ref: "#/$defs/Ext";
+                    readonly description: "Ecosystem-defined extension members per SPEC.md §4.5.1.";
+                };
+            };
+        };
+        readonly Ext: {
+            readonly title: "Ext";
+            readonly 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.";
+            readonly type: "object";
+            readonly minProperties: 1;
+            readonly additionalProperties: true;
+            readonly propertyNames: {
+                readonly pattern: "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$";
+            };
+        };
+        readonly Key: {
+            readonly title: "Key";
+            readonly 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.";
+            readonly type: "string";
+            readonly minLength: 1;
+            readonly maxLength: 512;
+            readonly pattern: "^[^\\u0000]+$";
+        };
+        readonly AppStateRecord: {
+            readonly title: "AppStateRecord";
+            readonly description: "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.";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["contextId", "namespace", "key", "version", "deleted", "updatedAt"];
+            readonly properties: {
+                readonly contextId: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly description: "The VTA context the record is scoped to; the isolation boundary.";
+                };
+                readonly namespace: {
+                    readonly $ref: "#/$defs/Namespace";
+                };
+                readonly key: {
+                    readonly $ref: "#/$defs/Key";
+                };
+                readonly version: {
+                    readonly $ref: "#/$defs/Version";
+                    readonly description: "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.";
+                };
+                readonly value: {
+                    readonly description: "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.";
+                };
+                readonly valueBytes: {
+                    readonly type: "integer";
+                    readonly minimum: 0;
+                    readonly description: "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.";
+                };
+                readonly deleted: {
+                    readonly type: "boolean";
+                    readonly description: "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`.";
+                };
+                readonly createdAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                    readonly description: "When the record was first created at this address. MAY be absent on a tombstone whose body has been discarded.";
+                };
+                readonly updatedAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                    readonly description: "When the write that produced this `version` was applied. For a tombstone, when the delete was applied.";
+                };
+                readonly deletedAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                    readonly description: "When the record was deleted. Present only when `deleted` is true; equal to `updatedAt` for a tombstone the maintainer has not since rewritten.";
+                };
+            };
+        };
+        readonly Version: {
+            readonly title: "Version";
+            readonly description: "A value of the namespace's monotonic write counter (see this schema's description). Server-assigned; a producer never chooses one.";
+            readonly type: "integer";
+            readonly minimum: 1;
+        };
+        readonly Namespace: {
+            readonly title: "Namespace";
+            readonly 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.";
+            readonly type: "string";
+            readonly minLength: 1;
+            readonly maxLength: 64;
+            readonly pattern: "^[a-z][a-z0-9]*(-[a-z0-9]+)*$";
+        };
+    };
+};
+/**
+ * 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 declare const SPEC: {
+    readonly typeUri: "https://trusttasks.org/spec/vta/app-state/get-many/1.0";
+    readonly isBearer: false;
+    readonly isProofRequired: false;
+    readonly isRecipientRequired: true;
+    readonly payloadSchema: {
+        readonly $schema: "https://json-schema.org/draft/2020-12/schema";
+        readonly $id: "https://trusttasks.org/spec/vta/app-state/get-many/1.0";
+        readonly title: "VTA Application State Get-Many — payload";
+        readonly description: "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.";
+        readonly type: "object";
+        readonly additionalProperties: false;
+        readonly required: readonly ["contextId", "namespace", "keys"];
+        readonly properties: {
+            readonly contextId: {
+                readonly type: "string";
+                readonly minLength: 1;
+                readonly description: "The VTA context the records are scoped to; the isolation boundary.";
+            };
+            readonly namespace: {
+                readonly $ref: "#/$defs/Namespace";
+                readonly description: "Required, unlike in list: a batch read addresses records by key, and a key is only unique within a namespace.";
+            };
+            readonly keys: {
+                readonly type: "array";
+                readonly minItems: 1;
+                readonly maxItems: 256;
+                readonly uniqueItems: true;
+                readonly items: {
+                    readonly $ref: "#/$defs/Key";
+                };
+                readonly description: "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.";
+            };
+            readonly includeDeleted: {
+                readonly type: "boolean";
+                readonly description: "Defaults to false. When true, an address holding a tombstone yields a record with `deleted: true` rather than appearing in `missing`.";
+            };
+            readonly ext: {
+                readonly $ref: "#/$defs/Ext";
+                readonly description: "Ecosystem-defined extension members per SPEC.md §4.5.1.";
+            };
+        };
+        readonly $defs: {
+            readonly Response: {
+                readonly $anchor: "response";
+                readonly title: "VTA Application State Get-Many — response payload";
+                readonly description: "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.";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["records", "missing"];
+                readonly properties: {
+                    readonly records: {
+                        readonly type: "array";
+                        readonly items: {
+                            readonly $ref: "#/$defs/AppStateRecord";
+                        };
+                        readonly description: "The records found, each with its `value`, in the order the keys were requested. May be empty.";
+                    };
+                    readonly missing: {
+                        readonly type: "array";
+                        readonly items: {
+                            readonly $ref: "#/$defs/Key";
+                        };
+                        readonly description: "Requested keys holding no record — and, unless `includeDeleted` was set, keys holding only a tombstone. Reported rather than silently omitted, so a caller need not diff the request against the response to notice.";
+                    };
+                    readonly deferred: {
+                        readonly type: "array";
+                        readonly items: {
+                            readonly $ref: "#/$defs/Key";
+                        };
+                        readonly description: "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.";
+                    };
+                    readonly ext: {
+                        readonly $ref: "#/$defs/Ext";
+                        readonly description: "Ecosystem-defined extension members per SPEC.md §4.5.1.";
+                    };
+                };
+            };
+            readonly Ext: {
+                readonly title: "Ext";
+                readonly 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.";
+                readonly type: "object";
+                readonly minProperties: 1;
+                readonly additionalProperties: true;
+                readonly propertyNames: {
+                    readonly pattern: "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$";
+                };
+            };
+            readonly Key: {
+                readonly title: "Key";
+                readonly 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.";
+                readonly type: "string";
+                readonly minLength: 1;
+                readonly maxLength: 512;
+                readonly pattern: "^[^\\u0000]+$";
+            };
+            readonly AppStateRecord: {
+                readonly title: "AppStateRecord";
+                readonly description: "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.";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["contextId", "namespace", "key", "version", "deleted", "updatedAt"];
+                readonly properties: {
+                    readonly contextId: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "The VTA context the record is scoped to; the isolation boundary.";
+                    };
+                    readonly namespace: {
+                        readonly $ref: "#/$defs/Namespace";
+                    };
+                    readonly key: {
+                        readonly $ref: "#/$defs/Key";
+                    };
+                    readonly version: {
+                        readonly $ref: "#/$defs/Version";
+                        readonly description: "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.";
+                    };
+                    readonly value: {
+                        readonly description: "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.";
+                    };
+                    readonly valueBytes: {
+                        readonly type: "integer";
+                        readonly minimum: 0;
+                        readonly description: "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.";
+                    };
+                    readonly deleted: {
+                        readonly type: "boolean";
+                        readonly description: "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`.";
+                    };
+                    readonly createdAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                        readonly description: "When the record was first created at this address. MAY be absent on a tombstone whose body has been discarded.";
+                    };
+                    readonly updatedAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                        readonly description: "When the write that produced this `version` was applied. For a tombstone, when the delete was applied.";
+                    };
+                    readonly deletedAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                        readonly description: "When the record was deleted. Present only when `deleted` is true; equal to `updatedAt` for a tombstone the maintainer has not since rewritten.";
+                    };
+                };
+            };
+            readonly Version: {
+                readonly title: "Version";
+                readonly description: "A value of the namespace's monotonic write counter (see this schema's description). Server-assigned; a producer never chooses one.";
+                readonly type: "integer";
+                readonly minimum: 1;
+            };
+            readonly Namespace: {
+                readonly title: "Namespace";
+                readonly 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.";
+                readonly type: "string";
+                readonly minLength: 1;
+                readonly maxLength: 64;
+                readonly pattern: "^[a-z][a-z0-9]*(-[a-z0-9]+)*$";
+            };
+        };
+    };
+};
+/**
+ * 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 declare const RESPONSE_SPEC: {
+    readonly typeUri: "https://trusttasks.org/spec/vta/app-state/get-many/1.0#response";
+    readonly isBearer: false;
+    readonly isProofRequired: false;
+    readonly isRecipientRequired: true;
+    readonly payloadSchema: {
+        readonly $schema: "https://json-schema.org/draft/2020-12/schema";
+        readonly $ref: "#/$defs/Response";
+        readonly $defs: {
+            readonly Response: {
+                readonly $anchor: "response";
+                readonly title: "VTA Application State Get-Many — response payload";
+                readonly description: "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.";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["records", "missing"];
+                readonly properties: {
+                    readonly records: {
+                        readonly type: "array";
+                        readonly items: {
+                            readonly $ref: "#/$defs/AppStateRecord";
+                        };
+                        readonly description: "The records found, each with its `value`, in the order the keys were requested. May be empty.";
+                    };
+                    readonly missing: {
+                        readonly type: "array";
+                        readonly items: {
+                            readonly $ref: "#/$defs/Key";
+                        };
+                        readonly description: "Requested keys holding no record — and, unless `includeDeleted` was set, keys holding only a tombstone. Reported rather than silently omitted, so a caller need not diff the request against the response to notice.";
+                    };
+                    readonly deferred: {
+                        readonly type: "array";
+                        readonly items: {
+                            readonly $ref: "#/$defs/Key";
+                        };
+                        readonly description: "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.";
+                    };
+                    readonly ext: {
+                        readonly $ref: "#/$defs/Ext";
+                        readonly description: "Ecosystem-defined extension members per SPEC.md §4.5.1.";
+                    };
+                };
+            };
+            readonly Ext: {
+                readonly title: "Ext";
+                readonly 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.";
+                readonly type: "object";
+                readonly minProperties: 1;
+                readonly additionalProperties: true;
+                readonly propertyNames: {
+                    readonly pattern: "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$";
+                };
+            };
+            readonly Key: {
+                readonly title: "Key";
+                readonly 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.";
+                readonly type: "string";
+                readonly minLength: 1;
+                readonly maxLength: 512;
+                readonly pattern: "^[^\\u0000]+$";
+            };
+            readonly AppStateRecord: {
+                readonly title: "AppStateRecord";
+                readonly description: "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.";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["contextId", "namespace", "key", "version", "deleted", "updatedAt"];
+                readonly properties: {
+                    readonly contextId: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "The VTA context the record is scoped to; the isolation boundary.";
+                    };
+                    readonly namespace: {
+                        readonly $ref: "#/$defs/Namespace";
+                    };
+                    readonly key: {
+                        readonly $ref: "#/$defs/Key";
+                    };
+                    readonly version: {
+                        readonly $ref: "#/$defs/Version";
+                        readonly description: "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.";
+                    };
+                    readonly value: {
+                        readonly description: "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.";
+                    };
+                    readonly valueBytes: {
+                        readonly type: "integer";
+                        readonly minimum: 0;
+                        readonly description: "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.";
+                    };
+                    readonly deleted: {
+                        readonly type: "boolean";
+                        readonly description: "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`.";
+                    };
+                    readonly createdAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                        readonly description: "When the record was first created at this address. MAY be absent on a tombstone whose body has been discarded.";
+                    };
+                    readonly updatedAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                        readonly description: "When the write that produced this `version` was applied. For a tombstone, when the delete was applied.";
+                    };
+                    readonly deletedAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                        readonly description: "When the record was deleted. Present only when `deleted` is true; equal to `updatedAt` for a tombstone the maintainer has not since rewritten.";
+                    };
+                };
+            };
+            readonly Version: {
+                readonly title: "Version";
+                readonly description: "A value of the namespace's monotonic write counter (see this schema's description). Server-assigned; a producer never chooses one.";
+                readonly type: "integer";
+                readonly minimum: 1;
+            };
+            readonly Namespace: {
+                readonly title: "Namespace";
+                readonly 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.";
+                readonly type: "string";
+                readonly minLength: 1;
+                readonly maxLength: 64;
+                readonly pattern: "^[a-z][a-z0-9]*(-[a-z0-9]+)*$";
+            };
+        };
+    };
+};
+//# sourceMappingURL=payload.d.ts.map