@openvtc/trust-tasks 0.22.3 → 0.22.5

package/dist/vtc/join-requests/submit/0.3/payload.d.ts

@@ -0,0 +1,662 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vtc/join-requests/submit/0.3/payload.schema.json
+ */
+import type { DigestMultibase, Ext, Verdict, VerdictEffect, VerdictWith } from "../../../../_shared/components.js";
+export interface VTCJoinRequestsSubmitPayload {
+    /**
+     * The applicant's W3C Verifiable Presentation (opaque here), satisfying the community's join policy. The applicant DID is the document proof's signer — not a payload field.
+     */
+    vp: {};
+    /**
+     * The `requirementsDigest` of the criterion this submission is made under, as vtc/join-requests/manifest/0.3 published it. Absent: the community decides the submission under the first criterion, in the order it publishes them, that the submission meets.
+     */
+    criterion?: DigestMultibase;
+    /**
+     * Whether the applicant consents to trust-registry publication.
+     */
+    registryConsent?: boolean;
+    /**
+     * Opaque applicant-supplied extension bag.
+     */
+    extensions?: {};
+    /**
+     * The applicant's answers to the manifest's `requestedAttributes`: one entry per attribute given. Self-asserted and bound to the applicant by the document proof. A maintainer MUST refuse the submission with `attributesMissing` when a required attribute is absent and with `attributesUnrequested` when an entry names a type the manifest does not request.
+     *
+     * @maxItems 32
+     */
+    attributes?: {
+        /**
+         * A claim-type token from the persona claim-type registry (persona/_shared/0.1/CLAIM-TYPES.md) — `name.display`, `address.country` — or an `x:` extension token.
+         */
+        type: string;
+        /**
+         * The value the applicant gives. Self-asserted: the applicant's own statement, bound to them by the document proof, and attested by nobody.
+         */
+        value: {
+            [k: string]: unknown | undefined;
+        };
+    }[];
+    ext?: Ext;
+}
+export interface VTCJoinRequestsSubmitResponsePayload {
+    /**
+     * Id of the created join request (a UUID).
+     */
+    requestId: string;
+    /**
+     * What the community decided about this submission.
+     *
+     * `0.1` returned `status: "pending"` — a constant, which could express only one of the four outcomes a submission actually has. A policy that admits outright, refuses outright, or asks for more evidence had to be reported as 'pending' or not at all.
+     */
+    verdict: Verdict;
+    ext?: Ext;
+}
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { DigestMultibase, Ext, Verdict, VerdictEffect, VerdictWith };
+/** Trust Task type URI. */
+export declare const TYPE_URI: "https://trusttasks.org/spec/vtc/join-requests/submit/0.3";
+/** Stable alias for this specification's request payload shape. */
+export type Payload = VTCJoinRequestsSubmitPayload;
+/** Trust Task response type URI (request type URI + "#response"). */
+export declare const RESPONSE_TYPE_URI: "https://trusttasks.org/spec/vtc/join-requests/submit/0.3#response";
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = VTCJoinRequestsSubmitResponsePayload;
+/**
+ * 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/vtc/join-requests/submit/0.3";
+    readonly title: "VTC Join-Requests Submit — payload";
+    readonly type: "object";
+    readonly additionalProperties: false;
+    readonly required: readonly ["vp"];
+    readonly properties: {
+        readonly vp: {
+            readonly type: "object";
+            readonly description: "The applicant's W3C Verifiable Presentation (opaque here), satisfying the community's join policy. The applicant DID is the document proof's signer — not a payload field.";
+        };
+        readonly criterion: {
+            readonly $ref: "#/$defs/DigestMultibase";
+            readonly description: "The `requirementsDigest` of the criterion this submission is made under, as vtc/join-requests/manifest/0.3 published it. Absent: the community decides the submission under the first criterion, in the order it publishes them, that the submission meets.";
+        };
+        readonly registryConsent: {
+            readonly type: "boolean";
+            readonly description: "Whether the applicant consents to trust-registry publication.";
+        };
+        readonly extensions: {
+            readonly type: "object";
+            readonly description: "Opaque applicant-supplied extension bag.";
+        };
+        readonly attributes: {
+            readonly type: "array";
+            readonly maxItems: 32;
+            readonly description: "The applicant's answers to the manifest's `requestedAttributes`: one entry per attribute given. Self-asserted and bound to the applicant by the document proof. A maintainer MUST refuse the submission with `attributesMissing` when a required attribute is absent and with `attributesUnrequested` when an entry names a type the manifest does not request.";
+            readonly items: {
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["type", "value"];
+                readonly properties: {
+                    readonly type: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly maxLength: 128;
+                        readonly pattern: "^(x:)?[a-z][A-Za-z0-9]*(\\.[a-z][A-Za-z0-9]*)*$";
+                        readonly description: "A claim-type token from the persona claim-type registry (persona/_shared/0.1/CLAIM-TYPES.md) — `name.display`, `address.country` — or an `x:` extension token.";
+                    };
+                    readonly value: {
+                        readonly description: "The value the applicant gives. Self-asserted: the applicant's own statement, bound to them by the document proof, and attested by nobody.";
+                    };
+                };
+            };
+        };
+        readonly ext: {
+            readonly $ref: "#/$defs/Ext";
+        };
+    };
+    readonly $defs: {
+        readonly Response: {
+            readonly $anchor: "response";
+            readonly title: "VTC Join-Requests Submit — response payload";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["requestId", "verdict"];
+            readonly properties: {
+                readonly requestId: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly description: "Id of the created join request (a UUID).";
+                };
+                readonly verdict: {
+                    readonly $ref: "#/$defs/Verdict";
+                    readonly description: "What the community decided about this submission.\n\n`0.1` returned `status: \"pending\"` — a constant, which could express only one of the four outcomes a submission actually has. A policy that admits outright, refuses outright, or asks for more evidence had to be reported as 'pending' or not at all.";
+                };
+                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 Verdict: {
+            readonly $anchor: "verdict";
+            readonly title: "Verdict";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["effect", "with"];
+            readonly description: "A ceremony decision: the effect, plus its effect-dependent detail.";
+            readonly properties: {
+                readonly effect: {
+                    readonly $ref: "#/$defs/VerdictEffect";
+                };
+                readonly with: {
+                    readonly $ref: "#/$defs/VerdictWith";
+                };
+            };
+        };
+        readonly VerdictWith: {
+            readonly $anchor: "verdictWith";
+            readonly title: "VerdictWith";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly description: "The effect-dependent detail of a verdict.\n\nEvery member is optional at the schema level and which ones are meaningful depends on `effect`: `role` / `obligations` / `bundleRef` on `allow`, `code` / `reason` on `deny`, `queue` / `reason` on `refer`, `needs` / `presentationDefinition` on `requestMore`. The dependency is stated here rather than enforced by `if`/`then` per effect, so that the shape stays a single flat object a generated type can carry without a discriminated union per family — a deliberate trade of schema strictness for implementability, and the reason a consumer MUST branch on `effect` rather than on which members happen to be present.";
+            readonly properties: {
+                readonly role: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly description: "The granted local role. `allow` only.";
+                };
+                readonly obligations: {
+                    readonly type: "object";
+                    readonly description: "Conditions attached to the grant. `allow` only.";
+                };
+                readonly bundleRef: {
+                    readonly type: "object";
+                    readonly description: "Pointer to a sealed credential bundle, added by the community where issuance occurred rather than emitted by the policy. `allow` only.";
+                };
+                readonly code: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly description: "Stable refusal code, safe to branch on. `deny` only.";
+                };
+                readonly reason: {
+                    readonly type: readonly ["string", "null"];
+                    readonly maxLength: 1024;
+                    readonly description: "Elaboration in prose, when the decider gave one. `deny` and `refer`.";
+                };
+                readonly queue: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly description: "Which review queue the decision was parked in, so an applicant can be told who now holds it. `refer` only.";
+                };
+                readonly needs: {
+                    readonly type: "array";
+                    readonly items: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                    };
+                    readonly description: "What further evidence is required, named so the applicant can act without a support conversation. `requestMore` only.";
+                };
+                readonly presentationDefinition: {
+                    readonly type: "object";
+                    readonly description: "A machine-readable statement of the same request, so a wallet can satisfy it without a human reading `needs`. `requestMore` only.";
+                };
+            };
+        };
+        readonly VerdictEffect: {
+            readonly $anchor: "verdictEffect";
+            readonly title: "VerdictEffect";
+            readonly type: "string";
+            readonly enum: readonly ["allow", "deny", "refer", "requestMore"];
+            readonly description: "What the policy decided.\n\n`allow` — admitted. `deny` — refused, terminally for this submission. `refer` — parked for a human or quorum decision; the applicant is neither in nor out. `requestMore` — the policy cannot decide yet and names what further evidence it needs.\n\nThe four are not reducible to a pending/decided pair. `refer` and `requestMore` are both 'not decided', but they place the next action with different parties: `refer` waits on the community, `requestMore` waits on the applicant. A consumer that cannot tell them apart cannot tell a user whether to wait or to act.";
+        };
+        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: "VTC Join-Requests Submit — response payload";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["requestId", "verdict"];
+            readonly properties: {
+                readonly requestId: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly description: "Id of the created join request (a UUID).";
+                };
+                readonly verdict: {
+                    readonly $ref: "#/$defs/Verdict";
+                    readonly description: "What the community decided about this submission.\n\n`0.1` returned `status: \"pending\"` — a constant, which could express only one of the four outcomes a submission actually has. A policy that admits outright, refuses outright, or asks for more evidence had to be reported as 'pending' or not at all.";
+                };
+                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 Verdict: {
+            readonly $anchor: "verdict";
+            readonly title: "Verdict";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["effect", "with"];
+            readonly description: "A ceremony decision: the effect, plus its effect-dependent detail.";
+            readonly properties: {
+                readonly effect: {
+                    readonly $ref: "#/$defs/VerdictEffect";
+                };
+                readonly with: {
+                    readonly $ref: "#/$defs/VerdictWith";
+                };
+            };
+        };
+        readonly VerdictWith: {
+            readonly $anchor: "verdictWith";
+            readonly title: "VerdictWith";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly description: "The effect-dependent detail of a verdict.\n\nEvery member is optional at the schema level and which ones are meaningful depends on `effect`: `role` / `obligations` / `bundleRef` on `allow`, `code` / `reason` on `deny`, `queue` / `reason` on `refer`, `needs` / `presentationDefinition` on `requestMore`. The dependency is stated here rather than enforced by `if`/`then` per effect, so that the shape stays a single flat object a generated type can carry without a discriminated union per family — a deliberate trade of schema strictness for implementability, and the reason a consumer MUST branch on `effect` rather than on which members happen to be present.";
+            readonly properties: {
+                readonly role: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly description: "The granted local role. `allow` only.";
+                };
+                readonly obligations: {
+                    readonly type: "object";
+                    readonly description: "Conditions attached to the grant. `allow` only.";
+                };
+                readonly bundleRef: {
+                    readonly type: "object";
+                    readonly description: "Pointer to a sealed credential bundle, added by the community where issuance occurred rather than emitted by the policy. `allow` only.";
+                };
+                readonly code: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly description: "Stable refusal code, safe to branch on. `deny` only.";
+                };
+                readonly reason: {
+                    readonly type: readonly ["string", "null"];
+                    readonly maxLength: 1024;
+                    readonly description: "Elaboration in prose, when the decider gave one. `deny` and `refer`.";
+                };
+                readonly queue: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly description: "Which review queue the decision was parked in, so an applicant can be told who now holds it. `refer` only.";
+                };
+                readonly needs: {
+                    readonly type: "array";
+                    readonly items: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                    };
+                    readonly description: "What further evidence is required, named so the applicant can act without a support conversation. `requestMore` only.";
+                };
+                readonly presentationDefinition: {
+                    readonly type: "object";
+                    readonly description: "A machine-readable statement of the same request, so a wallet can satisfy it without a human reading `needs`. `requestMore` only.";
+                };
+            };
+        };
+        readonly VerdictEffect: {
+            readonly $anchor: "verdictEffect";
+            readonly title: "VerdictEffect";
+            readonly type: "string";
+            readonly enum: readonly ["allow", "deny", "refer", "requestMore"];
+            readonly description: "What the policy decided.\n\n`allow` — admitted. `deny` — refused, terminally for this submission. `refer` — parked for a human or quorum decision; the applicant is neither in nor out. `requestMore` — the policy cannot decide yet and names what further evidence it needs.\n\nThe four are not reducible to a pending/decided pair. `refer` and `requestMore` are both 'not decided', but they place the next action with different parties: `refer` waits on the community, `requestMore` waits on the applicant. A consumer that cannot tell them apart cannot tell a user whether to wait or to act.";
+        };
+        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/vtc/join-requests/submit/0.3";
+    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/vtc/join-requests/submit/0.3";
+        readonly title: "VTC Join-Requests Submit — payload";
+        readonly type: "object";
+        readonly additionalProperties: false;
+        readonly required: readonly ["vp"];
+        readonly properties: {
+            readonly vp: {
+                readonly type: "object";
+                readonly description: "The applicant's W3C Verifiable Presentation (opaque here), satisfying the community's join policy. The applicant DID is the document proof's signer — not a payload field.";
+            };
+            readonly criterion: {
+                readonly $ref: "#/$defs/DigestMultibase";
+                readonly description: "The `requirementsDigest` of the criterion this submission is made under, as vtc/join-requests/manifest/0.3 published it. Absent: the community decides the submission under the first criterion, in the order it publishes them, that the submission meets.";
+            };
+            readonly registryConsent: {
+                readonly type: "boolean";
+                readonly description: "Whether the applicant consents to trust-registry publication.";
+            };
+            readonly extensions: {
+                readonly type: "object";
+                readonly description: "Opaque applicant-supplied extension bag.";
+            };
+            readonly attributes: {
+                readonly type: "array";
+                readonly maxItems: 32;
+                readonly description: "The applicant's answers to the manifest's `requestedAttributes`: one entry per attribute given. Self-asserted and bound to the applicant by the document proof. A maintainer MUST refuse the submission with `attributesMissing` when a required attribute is absent and with `attributesUnrequested` when an entry names a type the manifest does not request.";
+                readonly items: {
+                    readonly type: "object";
+                    readonly additionalProperties: false;
+                    readonly required: readonly ["type", "value"];
+                    readonly properties: {
+                        readonly type: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                            readonly maxLength: 128;
+                            readonly pattern: "^(x:)?[a-z][A-Za-z0-9]*(\\.[a-z][A-Za-z0-9]*)*$";
+                            readonly description: "A claim-type token from the persona claim-type registry (persona/_shared/0.1/CLAIM-TYPES.md) — `name.display`, `address.country` — or an `x:` extension token.";
+                        };
+                        readonly value: {
+                            readonly description: "The value the applicant gives. Self-asserted: the applicant's own statement, bound to them by the document proof, and attested by nobody.";
+                        };
+                    };
+                };
+            };
+            readonly ext: {
+                readonly $ref: "#/$defs/Ext";
+            };
+        };
+        readonly $defs: {
+            readonly Response: {
+                readonly $anchor: "response";
+                readonly title: "VTC Join-Requests Submit — response payload";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["requestId", "verdict"];
+                readonly properties: {
+                    readonly requestId: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "Id of the created join request (a UUID).";
+                    };
+                    readonly verdict: {
+                        readonly $ref: "#/$defs/Verdict";
+                        readonly description: "What the community decided about this submission.\n\n`0.1` returned `status: \"pending\"` — a constant, which could express only one of the four outcomes a submission actually has. A policy that admits outright, refuses outright, or asks for more evidence had to be reported as 'pending' or not at all.";
+                    };
+                    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 Verdict: {
+                readonly $anchor: "verdict";
+                readonly title: "Verdict";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["effect", "with"];
+                readonly description: "A ceremony decision: the effect, plus its effect-dependent detail.";
+                readonly properties: {
+                    readonly effect: {
+                        readonly $ref: "#/$defs/VerdictEffect";
+                    };
+                    readonly with: {
+                        readonly $ref: "#/$defs/VerdictWith";
+                    };
+                };
+            };
+            readonly VerdictWith: {
+                readonly $anchor: "verdictWith";
+                readonly title: "VerdictWith";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly description: "The effect-dependent detail of a verdict.\n\nEvery member is optional at the schema level and which ones are meaningful depends on `effect`: `role` / `obligations` / `bundleRef` on `allow`, `code` / `reason` on `deny`, `queue` / `reason` on `refer`, `needs` / `presentationDefinition` on `requestMore`. The dependency is stated here rather than enforced by `if`/`then` per effect, so that the shape stays a single flat object a generated type can carry without a discriminated union per family — a deliberate trade of schema strictness for implementability, and the reason a consumer MUST branch on `effect` rather than on which members happen to be present.";
+                readonly properties: {
+                    readonly role: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "The granted local role. `allow` only.";
+                    };
+                    readonly obligations: {
+                        readonly type: "object";
+                        readonly description: "Conditions attached to the grant. `allow` only.";
+                    };
+                    readonly bundleRef: {
+                        readonly type: "object";
+                        readonly description: "Pointer to a sealed credential bundle, added by the community where issuance occurred rather than emitted by the policy. `allow` only.";
+                    };
+                    readonly code: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "Stable refusal code, safe to branch on. `deny` only.";
+                    };
+                    readonly reason: {
+                        readonly type: readonly ["string", "null"];
+                        readonly maxLength: 1024;
+                        readonly description: "Elaboration in prose, when the decider gave one. `deny` and `refer`.";
+                    };
+                    readonly queue: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "Which review queue the decision was parked in, so an applicant can be told who now holds it. `refer` only.";
+                    };
+                    readonly needs: {
+                        readonly type: "array";
+                        readonly items: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                        };
+                        readonly description: "What further evidence is required, named so the applicant can act without a support conversation. `requestMore` only.";
+                    };
+                    readonly presentationDefinition: {
+                        readonly type: "object";
+                        readonly description: "A machine-readable statement of the same request, so a wallet can satisfy it without a human reading `needs`. `requestMore` only.";
+                    };
+                };
+            };
+            readonly VerdictEffect: {
+                readonly $anchor: "verdictEffect";
+                readonly title: "VerdictEffect";
+                readonly type: "string";
+                readonly enum: readonly ["allow", "deny", "refer", "requestMore"];
+                readonly description: "What the policy decided.\n\n`allow` — admitted. `deny` — refused, terminally for this submission. `refer` — parked for a human or quorum decision; the applicant is neither in nor out. `requestMore` — the policy cannot decide yet and names what further evidence it needs.\n\nThe four are not reducible to a pending/decided pair. `refer` and `requestMore` are both 'not decided', but they place the next action with different parties: `refer` waits on the community, `requestMore` waits on the applicant. A consumer that cannot tell them apart cannot tell a user whether to wait or to act.";
+            };
+            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/vtc/join-requests/submit/0.3#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: "VTC Join-Requests Submit — response payload";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["requestId", "verdict"];
+                readonly properties: {
+                    readonly requestId: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "Id of the created join request (a UUID).";
+                    };
+                    readonly verdict: {
+                        readonly $ref: "#/$defs/Verdict";
+                        readonly description: "What the community decided about this submission.\n\n`0.1` returned `status: \"pending\"` — a constant, which could express only one of the four outcomes a submission actually has. A policy that admits outright, refuses outright, or asks for more evidence had to be reported as 'pending' or not at all.";
+                    };
+                    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 Verdict: {
+                readonly $anchor: "verdict";
+                readonly title: "Verdict";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["effect", "with"];
+                readonly description: "A ceremony decision: the effect, plus its effect-dependent detail.";
+                readonly properties: {
+                    readonly effect: {
+                        readonly $ref: "#/$defs/VerdictEffect";
+                    };
+                    readonly with: {
+                        readonly $ref: "#/$defs/VerdictWith";
+                    };
+                };
+            };
+            readonly VerdictWith: {
+                readonly $anchor: "verdictWith";
+                readonly title: "VerdictWith";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly description: "The effect-dependent detail of a verdict.\n\nEvery member is optional at the schema level and which ones are meaningful depends on `effect`: `role` / `obligations` / `bundleRef` on `allow`, `code` / `reason` on `deny`, `queue` / `reason` on `refer`, `needs` / `presentationDefinition` on `requestMore`. The dependency is stated here rather than enforced by `if`/`then` per effect, so that the shape stays a single flat object a generated type can carry without a discriminated union per family — a deliberate trade of schema strictness for implementability, and the reason a consumer MUST branch on `effect` rather than on which members happen to be present.";
+                readonly properties: {
+                    readonly role: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "The granted local role. `allow` only.";
+                    };
+                    readonly obligations: {
+                        readonly type: "object";
+                        readonly description: "Conditions attached to the grant. `allow` only.";
+                    };
+                    readonly bundleRef: {
+                        readonly type: "object";
+                        readonly description: "Pointer to a sealed credential bundle, added by the community where issuance occurred rather than emitted by the policy. `allow` only.";
+                    };
+                    readonly code: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "Stable refusal code, safe to branch on. `deny` only.";
+                    };
+                    readonly reason: {
+                        readonly type: readonly ["string", "null"];
+                        readonly maxLength: 1024;
+                        readonly description: "Elaboration in prose, when the decider gave one. `deny` and `refer`.";
+                    };
+                    readonly queue: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "Which review queue the decision was parked in, so an applicant can be told who now holds it. `refer` only.";
+                    };
+                    readonly needs: {
+                        readonly type: "array";
+                        readonly items: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                        };
+                        readonly description: "What further evidence is required, named so the applicant can act without a support conversation. `requestMore` only.";
+                    };
+                    readonly presentationDefinition: {
+                        readonly type: "object";
+                        readonly description: "A machine-readable statement of the same request, so a wallet can satisfy it without a human reading `needs`. `requestMore` only.";
+                    };
+                };
+            };
+            readonly VerdictEffect: {
+                readonly $anchor: "verdictEffect";
+                readonly title: "VerdictEffect";
+                readonly type: "string";
+                readonly enum: readonly ["allow", "deny", "refer", "requestMore"];
+                readonly description: "What the policy decided.\n\n`allow` — admitted. `deny` — refused, terminally for this submission. `refer` — parked for a human or quorum decision; the applicant is neither in nor out. `requestMore` — the policy cannot decide yet and names what further evidence it needs.\n\nThe four are not reducible to a pending/decided pair. `refer` and `requestMore` are both 'not decided', but they place the next action with different parties: `refer` waits on the community, `requestMore` waits on the applicant. A consumer that cannot tell them apart cannot tell a user whether to wait or to act.";
+            };
+            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