@openvtc/trust-tasks 0.26.11 → 0.26.13

package/dist/vta/witness/list/0.1/payload.d.ts

@@ -0,0 +1,673 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vta/witness/list/0.1/payload.schema.json
+ */
+import type { DigestMultibase, EvidenceDocument, Ext, OutcomeEvidence } from "../../../../_shared/components.js";
+/**
+ * A client reads back from its VTA the Verifiable Witness Credentials vta/witness/accept stored for its principal, each with the outcome evidence stored beside it. Every filter is optional and those present are AND-combined.
+ */
+export interface VTAWitnessListPayload {
+    /**
+     * Only VWCs whose credentialSubject.id is this relationship DID.
+     */
+    relationshipDid?: string;
+    /**
+     * Only VWCs issued by this witness.
+     */
+    witness?: string;
+    /**
+     * Maximum entries to return. The VTA MAY return fewer and caps this value.
+     */
+    pageSize?: number;
+    /**
+     * Continue a previous page. Opaque: a consumer MUST NOT construct or parse one.
+     */
+    cursor?: string;
+    ext?: Ext;
+}
+/**
+ * One entry per stored VWC that matched and that the caller may read. Empty when nothing matched, which is a successful answer, not an error.
+ */
+export interface VTAWitnessListResponsePayload {
+    /**
+     * The matching stored VWCs, each with its evidence.
+     *
+     * @maxItems 100
+     */
+    witnessings: StoredWitnessing[];
+    /**
+     * The VTA stopped early. A consumer MUST NOT read a truncated page as a complete account of what is stored.
+     */
+    truncated: boolean;
+    /**
+     * Pass to the next request to continue. Absent when the page is the last.
+     */
+    cursor?: string;
+    ext?: Ext;
+}
+/**
+ * One VWC vta/witness/accept stored, as accept answered it, with the time it was stored. The VWC itself travels once, inside evidence.outcome, under the witness's proof.
+ */
+export interface StoredWitnessing {
+    /**
+     * The credential-vault handle the VWC is stored under: the credentialId vta/witness/accept returned.
+     */
+    credentialId: string;
+    /**
+     * The witness that issued the VWC: its issuer, which is the recipient of evidence.session.
+     */
+    witness: string;
+    /**
+     * The relationship DID the VWC names as its credentialSubject.id.
+     */
+    relationshipDid: string;
+    /**
+     * The VWC's digest, as the witness returned it and the VTA checked it at accept: over the RFC 8785 canonicalization of the VWC, proof included.
+     */
+    vwcDigestMultibase: DigestMultibase;
+    /**
+     * When vta/witness/accept stored the VWC.
+     */
+    acceptedAt: string;
+    /**
+     * The outcome evidence stored with the VWC, each document exactly as stored, never re-serialised: `session`, the witness/session document as the VTA built it, and `outcome`, the witness/session/submit #response as received, which carries the VWC. Of whichever version the session was conducted under.
+     */
+    evidence: OutcomeEvidence;
+    ext?: Ext;
+}
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { DigestMultibase, EvidenceDocument, Ext, OutcomeEvidence };
+/** Trust Task type URI. */
+export declare const TYPE_URI: "https://trusttasks.org/spec/vta/witness/list/0.1";
+/** Stable alias for this specification's request payload shape. */
+export type Payload = VTAWitnessListPayload;
+/** Trust Task response type URI (request type URI + "#response"). */
+export declare const RESPONSE_TYPE_URI: "https://trusttasks.org/spec/vta/witness/list/0.1#response";
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = VTAWitnessListResponsePayload;
+/**
+ * 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/witness/list/0.1";
+    readonly title: "VTA Witness — List — payload";
+    readonly description: "A client reads back from its VTA the Verifiable Witness Credentials vta/witness/accept stored for its principal, each with the outcome evidence stored beside it. Every filter is optional and those present are AND-combined.";
+    readonly type: "object";
+    readonly additionalProperties: false;
+    readonly properties: {
+        readonly relationshipDid: {
+            readonly type: "string";
+            readonly pattern: "^did:";
+            readonly maxLength: 2048;
+            readonly description: "Only VWCs whose credentialSubject.id is this relationship DID.";
+        };
+        readonly witness: {
+            readonly type: "string";
+            readonly pattern: "^did:";
+            readonly maxLength: 2048;
+            readonly description: "Only VWCs issued by this witness.";
+        };
+        readonly pageSize: {
+            readonly type: "integer";
+            readonly minimum: 1;
+            readonly maximum: 100;
+            readonly description: "Maximum entries to return. The VTA MAY return fewer and caps this value.";
+        };
+        readonly cursor: {
+            readonly type: "string";
+            readonly minLength: 1;
+            readonly maxLength: 4096;
+            readonly description: "Continue a previous page. Opaque: a consumer MUST NOT construct or parse one.";
+        };
+        readonly ext: {
+            readonly $ref: "#/$defs/Ext";
+        };
+    };
+    readonly $defs: {
+        readonly Response: {
+            readonly $anchor: "response";
+            readonly title: "VTA Witness — List — response payload";
+            readonly description: "One entry per stored VWC that matched and that the caller may read. Empty when nothing matched, which is a successful answer, not an error.";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["witnessings", "truncated"];
+            readonly properties: {
+                readonly witnessings: {
+                    readonly type: "array";
+                    readonly maxItems: 100;
+                    readonly items: {
+                        readonly $ref: "#/$defs/StoredWitnessing";
+                    };
+                    readonly description: "The matching stored VWCs, each with its evidence.";
+                };
+                readonly truncated: {
+                    readonly type: "boolean";
+                    readonly description: "The VTA stopped early. A consumer MUST NOT read a truncated page as a complete account of what is stored.";
+                };
+                readonly cursor: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly maxLength: 4096;
+                    readonly description: "Pass to the next request to continue. Absent when the page is the last.";
+                };
+                readonly ext: {
+                    readonly $ref: "#/$defs/Ext";
+                };
+            };
+        };
+        readonly StoredWitnessing: {
+            readonly title: "StoredWitnessing";
+            readonly description: "One VWC vta/witness/accept stored, as accept answered it, with the time it was stored. The VWC itself travels once, inside evidence.outcome, under the witness's proof.";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["credentialId", "witness", "relationshipDid", "vwcDigestMultibase", "acceptedAt", "evidence"];
+            readonly properties: {
+                readonly credentialId: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly maxLength: 256;
+                    readonly description: "The credential-vault handle the VWC is stored under: the credentialId vta/witness/accept returned.";
+                };
+                readonly witness: {
+                    readonly type: "string";
+                    readonly pattern: "^did:";
+                    readonly maxLength: 2048;
+                    readonly description: "The witness that issued the VWC: its issuer, which is the recipient of evidence.session.";
+                };
+                readonly relationshipDid: {
+                    readonly type: "string";
+                    readonly pattern: "^did:";
+                    readonly maxLength: 2048;
+                    readonly description: "The relationship DID the VWC names as its credentialSubject.id.";
+                };
+                readonly vwcDigestMultibase: {
+                    readonly $ref: "#/$defs/DigestMultibase";
+                    readonly description: "The VWC's digest, as the witness returned it and the VTA checked it at accept: over the RFC 8785 canonicalization of the VWC, proof included.";
+                };
+                readonly acceptedAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                    readonly description: "When vta/witness/accept stored the VWC.";
+                };
+                readonly evidence: {
+                    readonly $ref: "#/$defs/OutcomeEvidence";
+                    readonly description: "The outcome evidence stored with the VWC, each document exactly as stored, never re-serialised: `session`, the witness/session document as the VTA built it, and `outcome`, the witness/session/submit #response as received, which carries the VWC. Of whichever version the session was conducted under.";
+                };
+                readonly ext: {
+                    readonly $ref: "#/$defs/Ext";
+                };
+            };
+        };
+        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 OutcomeEvidence: {
+            readonly title: "OutcomeEvidence";
+            readonly description: "One witnessing session's outcome evidence. `session` is the initiating witness/session document; `outcome` is the terminal witness/session/submit #response that the initiating document's own specification declares as its outcome evidence, under the witness's proof, delivering the VWC and its vwcDigestMultibase. A consumer pairs them with a presented VWC by SPEC §4.9.4's four checks and the witnessing checks of witness/session/submit (This response is the outcome evidence).";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["session", "outcome"];
+            readonly properties: {
+                readonly session: {
+                    readonly $ref: "#/$defs/EvidenceDocument";
+                    readonly description: "The witness/session document that opened the session. The VWC's taskContext is its id and its taskDigestMultibase is computed over it (SPEC §4.9.3).";
+                };
+                readonly outcome: {
+                    readonly $ref: "#/$defs/EvidenceDocument";
+                    readonly description: "The witness/session/submit #response that closed the session, under the witness's proof. It carries the VWC and its vwcDigestMultibase.";
+                };
+            };
+        };
+        readonly EvidenceDocument: {
+            readonly title: "EvidenceDocument";
+            readonly description: "A whole Trust Task document — `id`, `type`, `payload` and every other member, `proof` included — carried exactly as it was sent or received, never re-serialised: a task digest and a proof are taken over its members, and a re-serialised copy reproduces neither reliably. Typed as an open object so every member survives; the checks that give it meaning belong to the task that reads it.";
+            readonly type: "object";
+            readonly minProperties: 1;
+        };
+        readonly DigestMultibase: {
+            readonly title: "DigestMultibase";
+            readonly description: "A cryptographic digest as a multibase-encoded multihash — the encoding the W3C Verifiable Credentials Data Model 2.0 defines for `digestMultibase`, and the one `did:webvh` uses for its SCID and entry hashes.\n\nMultihash carries the hash algorithm in-band, so the value is self-describing and the wire format survives an algorithm change without a schema revision; multibase does the same for the base encoding, so a verifier never infers base58 from base64url by context. A bare hex string or a `sha-256:`-style prefix hard-codes one algorithm into the wire contract and is non-conforming here.\n\nThis definition constrains the *encoding only*. What the digest is computed over is stated by each referencing field, because it differs legitimately: a digest over a JSON document is taken over its RFC 8785 (JCS) canonicalization, while a digest over an opaque artifact is taken over its bytes. A field whose input is a JSON document and which does not name a canonicalization is not reproducible.\n\nRestricted to the two multibase headers W3C Controlled Identifiers 1.0 §2.4 normatively requires — `z` (base58btc) and `u` (base64url-no-pad). CID permits others but states that \"interoperability is not guaranteed between implementations using such values\", and a registry whose purpose is interoperability should not mint digests a conforming verifier may be unable to read. The alphabets are enforced rather than assumed: base58btc excludes 0, O, I and l, and an earlier permissive pattern let three published examples carry digests that were not valid base58 at all. base58btc is RECOMMENDED, for consistency with `did:key` and `did:webvh`.";
+            readonly type: "string";
+            readonly minLength: 16;
+            readonly pattern: "^(z[1-9A-HJ-NP-Za-km-z]+|u[A-Za-z0-9_-]+)$";
+            readonly examples: readonly ["zQmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR"];
+        };
+    };
+};
+/** 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 Witness — List — response payload";
+            readonly description: "One entry per stored VWC that matched and that the caller may read. Empty when nothing matched, which is a successful answer, not an error.";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["witnessings", "truncated"];
+            readonly properties: {
+                readonly witnessings: {
+                    readonly type: "array";
+                    readonly maxItems: 100;
+                    readonly items: {
+                        readonly $ref: "#/$defs/StoredWitnessing";
+                    };
+                    readonly description: "The matching stored VWCs, each with its evidence.";
+                };
+                readonly truncated: {
+                    readonly type: "boolean";
+                    readonly description: "The VTA stopped early. A consumer MUST NOT read a truncated page as a complete account of what is stored.";
+                };
+                readonly cursor: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly maxLength: 4096;
+                    readonly description: "Pass to the next request to continue. Absent when the page is the last.";
+                };
+                readonly ext: {
+                    readonly $ref: "#/$defs/Ext";
+                };
+            };
+        };
+        readonly StoredWitnessing: {
+            readonly title: "StoredWitnessing";
+            readonly description: "One VWC vta/witness/accept stored, as accept answered it, with the time it was stored. The VWC itself travels once, inside evidence.outcome, under the witness's proof.";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["credentialId", "witness", "relationshipDid", "vwcDigestMultibase", "acceptedAt", "evidence"];
+            readonly properties: {
+                readonly credentialId: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly maxLength: 256;
+                    readonly description: "The credential-vault handle the VWC is stored under: the credentialId vta/witness/accept returned.";
+                };
+                readonly witness: {
+                    readonly type: "string";
+                    readonly pattern: "^did:";
+                    readonly maxLength: 2048;
+                    readonly description: "The witness that issued the VWC: its issuer, which is the recipient of evidence.session.";
+                };
+                readonly relationshipDid: {
+                    readonly type: "string";
+                    readonly pattern: "^did:";
+                    readonly maxLength: 2048;
+                    readonly description: "The relationship DID the VWC names as its credentialSubject.id.";
+                };
+                readonly vwcDigestMultibase: {
+                    readonly $ref: "#/$defs/DigestMultibase";
+                    readonly description: "The VWC's digest, as the witness returned it and the VTA checked it at accept: over the RFC 8785 canonicalization of the VWC, proof included.";
+                };
+                readonly acceptedAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                    readonly description: "When vta/witness/accept stored the VWC.";
+                };
+                readonly evidence: {
+                    readonly $ref: "#/$defs/OutcomeEvidence";
+                    readonly description: "The outcome evidence stored with the VWC, each document exactly as stored, never re-serialised: `session`, the witness/session document as the VTA built it, and `outcome`, the witness/session/submit #response as received, which carries the VWC. Of whichever version the session was conducted under.";
+                };
+                readonly ext: {
+                    readonly $ref: "#/$defs/Ext";
+                };
+            };
+        };
+        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 OutcomeEvidence: {
+            readonly title: "OutcomeEvidence";
+            readonly description: "One witnessing session's outcome evidence. `session` is the initiating witness/session document; `outcome` is the terminal witness/session/submit #response that the initiating document's own specification declares as its outcome evidence, under the witness's proof, delivering the VWC and its vwcDigestMultibase. A consumer pairs them with a presented VWC by SPEC §4.9.4's four checks and the witnessing checks of witness/session/submit (This response is the outcome evidence).";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["session", "outcome"];
+            readonly properties: {
+                readonly session: {
+                    readonly $ref: "#/$defs/EvidenceDocument";
+                    readonly description: "The witness/session document that opened the session. The VWC's taskContext is its id and its taskDigestMultibase is computed over it (SPEC §4.9.3).";
+                };
+                readonly outcome: {
+                    readonly $ref: "#/$defs/EvidenceDocument";
+                    readonly description: "The witness/session/submit #response that closed the session, under the witness's proof. It carries the VWC and its vwcDigestMultibase.";
+                };
+            };
+        };
+        readonly EvidenceDocument: {
+            readonly title: "EvidenceDocument";
+            readonly description: "A whole Trust Task document — `id`, `type`, `payload` and every other member, `proof` included — carried exactly as it was sent or received, never re-serialised: a task digest and a proof are taken over its members, and a re-serialised copy reproduces neither reliably. Typed as an open object so every member survives; the checks that give it meaning belong to the task that reads it.";
+            readonly type: "object";
+            readonly minProperties: 1;
+        };
+        readonly DigestMultibase: {
+            readonly title: "DigestMultibase";
+            readonly description: "A cryptographic digest as a multibase-encoded multihash — the encoding the W3C Verifiable Credentials Data Model 2.0 defines for `digestMultibase`, and the one `did:webvh` uses for its SCID and entry hashes.\n\nMultihash carries the hash algorithm in-band, so the value is self-describing and the wire format survives an algorithm change without a schema revision; multibase does the same for the base encoding, so a verifier never infers base58 from base64url by context. A bare hex string or a `sha-256:`-style prefix hard-codes one algorithm into the wire contract and is non-conforming here.\n\nThis definition constrains the *encoding only*. What the digest is computed over is stated by each referencing field, because it differs legitimately: a digest over a JSON document is taken over its RFC 8785 (JCS) canonicalization, while a digest over an opaque artifact is taken over its bytes. A field whose input is a JSON document and which does not name a canonicalization is not reproducible.\n\nRestricted to the two multibase headers W3C Controlled Identifiers 1.0 §2.4 normatively requires — `z` (base58btc) and `u` (base64url-no-pad). CID permits others but states that \"interoperability is not guaranteed between implementations using such values\", and a registry whose purpose is interoperability should not mint digests a conforming verifier may be unable to read. The alphabets are enforced rather than assumed: base58btc excludes 0, O, I and l, and an earlier permissive pattern let three published examples carry digests that were not valid base58 at all. base58btc is RECOMMENDED, for consistency with `did:key` and `did:webvh`.";
+            readonly type: "string";
+            readonly minLength: 16;
+            readonly pattern: "^(z[1-9A-HJ-NP-Za-km-z]+|u[A-Za-z0-9_-]+)$";
+            readonly examples: readonly ["zQmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR"];
+        };
+    };
+};
+/**
+ * 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/witness/list/0.1";
+    readonly isBearer: false;
+    readonly isProofRequired: true;
+    readonly isRecipientRequired: true;
+    readonly isIssuedAtRequired: true;
+    readonly payloadSchema: {
+        readonly $schema: "https://json-schema.org/draft/2020-12/schema";
+        readonly $id: "https://trusttasks.org/spec/vta/witness/list/0.1";
+        readonly title: "VTA Witness — List — payload";
+        readonly description: "A client reads back from its VTA the Verifiable Witness Credentials vta/witness/accept stored for its principal, each with the outcome evidence stored beside it. Every filter is optional and those present are AND-combined.";
+        readonly type: "object";
+        readonly additionalProperties: false;
+        readonly properties: {
+            readonly relationshipDid: {
+                readonly type: "string";
+                readonly pattern: "^did:";
+                readonly maxLength: 2048;
+                readonly description: "Only VWCs whose credentialSubject.id is this relationship DID.";
+            };
+            readonly witness: {
+                readonly type: "string";
+                readonly pattern: "^did:";
+                readonly maxLength: 2048;
+                readonly description: "Only VWCs issued by this witness.";
+            };
+            readonly pageSize: {
+                readonly type: "integer";
+                readonly minimum: 1;
+                readonly maximum: 100;
+                readonly description: "Maximum entries to return. The VTA MAY return fewer and caps this value.";
+            };
+            readonly cursor: {
+                readonly type: "string";
+                readonly minLength: 1;
+                readonly maxLength: 4096;
+                readonly description: "Continue a previous page. Opaque: a consumer MUST NOT construct or parse one.";
+            };
+            readonly ext: {
+                readonly $ref: "#/$defs/Ext";
+            };
+        };
+        readonly $defs: {
+            readonly Response: {
+                readonly $anchor: "response";
+                readonly title: "VTA Witness — List — response payload";
+                readonly description: "One entry per stored VWC that matched and that the caller may read. Empty when nothing matched, which is a successful answer, not an error.";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["witnessings", "truncated"];
+                readonly properties: {
+                    readonly witnessings: {
+                        readonly type: "array";
+                        readonly maxItems: 100;
+                        readonly items: {
+                            readonly $ref: "#/$defs/StoredWitnessing";
+                        };
+                        readonly description: "The matching stored VWCs, each with its evidence.";
+                    };
+                    readonly truncated: {
+                        readonly type: "boolean";
+                        readonly description: "The VTA stopped early. A consumer MUST NOT read a truncated page as a complete account of what is stored.";
+                    };
+                    readonly cursor: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly maxLength: 4096;
+                        readonly description: "Pass to the next request to continue. Absent when the page is the last.";
+                    };
+                    readonly ext: {
+                        readonly $ref: "#/$defs/Ext";
+                    };
+                };
+            };
+            readonly StoredWitnessing: {
+                readonly title: "StoredWitnessing";
+                readonly description: "One VWC vta/witness/accept stored, as accept answered it, with the time it was stored. The VWC itself travels once, inside evidence.outcome, under the witness's proof.";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["credentialId", "witness", "relationshipDid", "vwcDigestMultibase", "acceptedAt", "evidence"];
+                readonly properties: {
+                    readonly credentialId: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly maxLength: 256;
+                        readonly description: "The credential-vault handle the VWC is stored under: the credentialId vta/witness/accept returned.";
+                    };
+                    readonly witness: {
+                        readonly type: "string";
+                        readonly pattern: "^did:";
+                        readonly maxLength: 2048;
+                        readonly description: "The witness that issued the VWC: its issuer, which is the recipient of evidence.session.";
+                    };
+                    readonly relationshipDid: {
+                        readonly type: "string";
+                        readonly pattern: "^did:";
+                        readonly maxLength: 2048;
+                        readonly description: "The relationship DID the VWC names as its credentialSubject.id.";
+                    };
+                    readonly vwcDigestMultibase: {
+                        readonly $ref: "#/$defs/DigestMultibase";
+                        readonly description: "The VWC's digest, as the witness returned it and the VTA checked it at accept: over the RFC 8785 canonicalization of the VWC, proof included.";
+                    };
+                    readonly acceptedAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                        readonly description: "When vta/witness/accept stored the VWC.";
+                    };
+                    readonly evidence: {
+                        readonly $ref: "#/$defs/OutcomeEvidence";
+                        readonly description: "The outcome evidence stored with the VWC, each document exactly as stored, never re-serialised: `session`, the witness/session document as the VTA built it, and `outcome`, the witness/session/submit #response as received, which carries the VWC. Of whichever version the session was conducted under.";
+                    };
+                    readonly ext: {
+                        readonly $ref: "#/$defs/Ext";
+                    };
+                };
+            };
+            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 OutcomeEvidence: {
+                readonly title: "OutcomeEvidence";
+                readonly description: "One witnessing session's outcome evidence. `session` is the initiating witness/session document; `outcome` is the terminal witness/session/submit #response that the initiating document's own specification declares as its outcome evidence, under the witness's proof, delivering the VWC and its vwcDigestMultibase. A consumer pairs them with a presented VWC by SPEC §4.9.4's four checks and the witnessing checks of witness/session/submit (This response is the outcome evidence).";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["session", "outcome"];
+                readonly properties: {
+                    readonly session: {
+                        readonly $ref: "#/$defs/EvidenceDocument";
+                        readonly description: "The witness/session document that opened the session. The VWC's taskContext is its id and its taskDigestMultibase is computed over it (SPEC §4.9.3).";
+                    };
+                    readonly outcome: {
+                        readonly $ref: "#/$defs/EvidenceDocument";
+                        readonly description: "The witness/session/submit #response that closed the session, under the witness's proof. It carries the VWC and its vwcDigestMultibase.";
+                    };
+                };
+            };
+            readonly EvidenceDocument: {
+                readonly title: "EvidenceDocument";
+                readonly description: "A whole Trust Task document — `id`, `type`, `payload` and every other member, `proof` included — carried exactly as it was sent or received, never re-serialised: a task digest and a proof are taken over its members, and a re-serialised copy reproduces neither reliably. Typed as an open object so every member survives; the checks that give it meaning belong to the task that reads it.";
+                readonly type: "object";
+                readonly minProperties: 1;
+            };
+            readonly DigestMultibase: {
+                readonly title: "DigestMultibase";
+                readonly description: "A cryptographic digest as a multibase-encoded multihash — the encoding the W3C Verifiable Credentials Data Model 2.0 defines for `digestMultibase`, and the one `did:webvh` uses for its SCID and entry hashes.\n\nMultihash carries the hash algorithm in-band, so the value is self-describing and the wire format survives an algorithm change without a schema revision; multibase does the same for the base encoding, so a verifier never infers base58 from base64url by context. A bare hex string or a `sha-256:`-style prefix hard-codes one algorithm into the wire contract and is non-conforming here.\n\nThis definition constrains the *encoding only*. What the digest is computed over is stated by each referencing field, because it differs legitimately: a digest over a JSON document is taken over its RFC 8785 (JCS) canonicalization, while a digest over an opaque artifact is taken over its bytes. A field whose input is a JSON document and which does not name a canonicalization is not reproducible.\n\nRestricted to the two multibase headers W3C Controlled Identifiers 1.0 §2.4 normatively requires — `z` (base58btc) and `u` (base64url-no-pad). CID permits others but states that \"interoperability is not guaranteed between implementations using such values\", and a registry whose purpose is interoperability should not mint digests a conforming verifier may be unable to read. The alphabets are enforced rather than assumed: base58btc excludes 0, O, I and l, and an earlier permissive pattern let three published examples carry digests that were not valid base58 at all. base58btc is RECOMMENDED, for consistency with `did:key` and `did:webvh`.";
+                readonly type: "string";
+                readonly minLength: 16;
+                readonly pattern: "^(z[1-9A-HJ-NP-Za-km-z]+|u[A-Za-z0-9_-]+)$";
+                readonly examples: readonly ["zQmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR"];
+            };
+        };
+    };
+};
+/**
+ * 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/witness/list/0.1#response";
+    readonly isBearer: false;
+    readonly isProofRequired: true;
+    readonly isRecipientRequired: true;
+    readonly isIssuedAtRequired: 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 Witness — List — response payload";
+                readonly description: "One entry per stored VWC that matched and that the caller may read. Empty when nothing matched, which is a successful answer, not an error.";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["witnessings", "truncated"];
+                readonly properties: {
+                    readonly witnessings: {
+                        readonly type: "array";
+                        readonly maxItems: 100;
+                        readonly items: {
+                            readonly $ref: "#/$defs/StoredWitnessing";
+                        };
+                        readonly description: "The matching stored VWCs, each with its evidence.";
+                    };
+                    readonly truncated: {
+                        readonly type: "boolean";
+                        readonly description: "The VTA stopped early. A consumer MUST NOT read a truncated page as a complete account of what is stored.";
+                    };
+                    readonly cursor: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly maxLength: 4096;
+                        readonly description: "Pass to the next request to continue. Absent when the page is the last.";
+                    };
+                    readonly ext: {
+                        readonly $ref: "#/$defs/Ext";
+                    };
+                };
+            };
+            readonly StoredWitnessing: {
+                readonly title: "StoredWitnessing";
+                readonly description: "One VWC vta/witness/accept stored, as accept answered it, with the time it was stored. The VWC itself travels once, inside evidence.outcome, under the witness's proof.";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["credentialId", "witness", "relationshipDid", "vwcDigestMultibase", "acceptedAt", "evidence"];
+                readonly properties: {
+                    readonly credentialId: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly maxLength: 256;
+                        readonly description: "The credential-vault handle the VWC is stored under: the credentialId vta/witness/accept returned.";
+                    };
+                    readonly witness: {
+                        readonly type: "string";
+                        readonly pattern: "^did:";
+                        readonly maxLength: 2048;
+                        readonly description: "The witness that issued the VWC: its issuer, which is the recipient of evidence.session.";
+                    };
+                    readonly relationshipDid: {
+                        readonly type: "string";
+                        readonly pattern: "^did:";
+                        readonly maxLength: 2048;
+                        readonly description: "The relationship DID the VWC names as its credentialSubject.id.";
+                    };
+                    readonly vwcDigestMultibase: {
+                        readonly $ref: "#/$defs/DigestMultibase";
+                        readonly description: "The VWC's digest, as the witness returned it and the VTA checked it at accept: over the RFC 8785 canonicalization of the VWC, proof included.";
+                    };
+                    readonly acceptedAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                        readonly description: "When vta/witness/accept stored the VWC.";
+                    };
+                    readonly evidence: {
+                        readonly $ref: "#/$defs/OutcomeEvidence";
+                        readonly description: "The outcome evidence stored with the VWC, each document exactly as stored, never re-serialised: `session`, the witness/session document as the VTA built it, and `outcome`, the witness/session/submit #response as received, which carries the VWC. Of whichever version the session was conducted under.";
+                    };
+                    readonly ext: {
+                        readonly $ref: "#/$defs/Ext";
+                    };
+                };
+            };
+            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 OutcomeEvidence: {
+                readonly title: "OutcomeEvidence";
+                readonly description: "One witnessing session's outcome evidence. `session` is the initiating witness/session document; `outcome` is the terminal witness/session/submit #response that the initiating document's own specification declares as its outcome evidence, under the witness's proof, delivering the VWC and its vwcDigestMultibase. A consumer pairs them with a presented VWC by SPEC §4.9.4's four checks and the witnessing checks of witness/session/submit (This response is the outcome evidence).";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["session", "outcome"];
+                readonly properties: {
+                    readonly session: {
+                        readonly $ref: "#/$defs/EvidenceDocument";
+                        readonly description: "The witness/session document that opened the session. The VWC's taskContext is its id and its taskDigestMultibase is computed over it (SPEC §4.9.3).";
+                    };
+                    readonly outcome: {
+                        readonly $ref: "#/$defs/EvidenceDocument";
+                        readonly description: "The witness/session/submit #response that closed the session, under the witness's proof. It carries the VWC and its vwcDigestMultibase.";
+                    };
+                };
+            };
+            readonly EvidenceDocument: {
+                readonly title: "EvidenceDocument";
+                readonly description: "A whole Trust Task document — `id`, `type`, `payload` and every other member, `proof` included — carried exactly as it was sent or received, never re-serialised: a task digest and a proof are taken over its members, and a re-serialised copy reproduces neither reliably. Typed as an open object so every member survives; the checks that give it meaning belong to the task that reads it.";
+                readonly type: "object";
+                readonly minProperties: 1;
+            };
+            readonly DigestMultibase: {
+                readonly title: "DigestMultibase";
+                readonly description: "A cryptographic digest as a multibase-encoded multihash — the encoding the W3C Verifiable Credentials Data Model 2.0 defines for `digestMultibase`, and the one `did:webvh` uses for its SCID and entry hashes.\n\nMultihash carries the hash algorithm in-band, so the value is self-describing and the wire format survives an algorithm change without a schema revision; multibase does the same for the base encoding, so a verifier never infers base58 from base64url by context. A bare hex string or a `sha-256:`-style prefix hard-codes one algorithm into the wire contract and is non-conforming here.\n\nThis definition constrains the *encoding only*. What the digest is computed over is stated by each referencing field, because it differs legitimately: a digest over a JSON document is taken over its RFC 8785 (JCS) canonicalization, while a digest over an opaque artifact is taken over its bytes. A field whose input is a JSON document and which does not name a canonicalization is not reproducible.\n\nRestricted to the two multibase headers W3C Controlled Identifiers 1.0 §2.4 normatively requires — `z` (base58btc) and `u` (base64url-no-pad). CID permits others but states that \"interoperability is not guaranteed between implementations using such values\", and a registry whose purpose is interoperability should not mint digests a conforming verifier may be unable to read. The alphabets are enforced rather than assumed: base58btc excludes 0, O, I and l, and an earlier permissive pattern let three published examples carry digests that were not valid base58 at all. base58btc is RECOMMENDED, for consistency with `did:key` and `did:webvh`.";
+                readonly type: "string";
+                readonly minLength: 16;
+                readonly pattern: "^(z[1-9A-HJ-NP-Za-km-z]+|u[A-Za-z0-9_-]+)$";
+                readonly examples: readonly ["zQmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR"];
+            };
+        };
+    };
+};
+//# sourceMappingURL=payload.d.ts.map