@openvtc/trust-tasks 0.20.0 → 0.20.2

package/dist/persona/attribute/get/1.0/payload.d.ts

@@ -0,0 +1,1221 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/persona/attribute/get/1.0/payload.schema.json
+ */
+import type { Attribute, ClaimType, Ext, ProofRung, Provenance, ReleaseRequirement, Sensitivity, Ulid, ValueType, Version_PersonaV0_1 as Version } from "../../../../_shared/components.js";
+/**
+ * Read one attribute the holder holds, by identifier. Values are withheld unless asked for, on the same two-step as persona/attribute/list: the expensive, disclosing path is the one a producer has to name.
+ */
+export interface PersonaAttributeGetPayload {
+    /**
+     * The attribute to read. One identifier, never a list: a maintainer that accepted several would recreate the enumeration this task exists to avoid.
+     */
+    attributeId: Ulid;
+    /**
+     * When false (the default), the attribute's metadata is returned and its `value` is not. The default is false even though a caller naming one attribute usually wants its value, because the alternative makes the disclosing path the one nobody has to ask for — and the audit row can then say whether plaintext left, which is the question worth being able to answer later.
+     */
+    includeValue?: boolean;
+    /**
+     * When false (the default), a request that asked for the value still does not receive it for an attribute resolving to `sensitivity: high` — the metadata is returned, the plaintext is not. Setting it asks for that too.
+     *
+     * The second flag is not ceremony. A consumer that masks a value it has already received defends a screen; it does not keep a passport number out of a log, a crash dump, or a process's memory. The value never being sent is what does.
+     */
+    includeSensitive?: boolean;
+    /**
+     * Read a retained earlier version instead of the current one. Absent means current.
+     *
+     * This is what makes "what did I show them in March" answerable: a disclosure record and a pinned profile entry both name a version, and without this a caller holding one has no way to read what it said. A version the holder has purged is `persona/attribute/get:versionPurged` — never a silent fall back to the current value, which would answer a question about the past with a fact about the present.
+     */
+    version?: Version;
+    ext?: Ext;
+}
+/**
+ * Success response to persona/attribute/get. Type https://trusttasks.org/spec/persona/attribute/get/1.0#response.
+ */
+export interface PersonaAttributeGetResponsePayload {
+    /**
+     * The attribute as at `version`, or as it stands when none was asked for. Its `value` is present only if the request asked for it and the attribute's sensitivity permitted it.
+     */
+    attribute: Attribute;
+    /**
+     * True when the value was withheld although `includeValue` asked for it — the attribute resolves to `sensitivity: high` and `includeSensitive` was not set. Stated rather than left to inference: a consumer that reads an absent `value` as "this attribute has none" will show the holder an empty field where a passport number is, and conclude the record is broken.
+     */
+    valueWithheld?: boolean;
+    /**
+     * The versions of this attribute the maintainer still holds, newest first, including the current one. Names versions and never their values.
+     *
+     * It is here because a holder deciding whether to purge cannot see what purging would take away: which earlier versions exist, and therefore which pinned profile entries would stop presenting. A consumer that cannot enumerate them asks the holder to make an irreversible decision blind.
+     *
+     * @maxItems 64
+     */
+    retainedVersions?: Version[];
+    ext?: Ext;
+}
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { Attribute, ClaimType, Ext, ProofRung, Provenance, ReleaseRequirement, Sensitivity, Ulid, ValueType, Version };
+/** Trust Task type URI. */
+export declare const TYPE_URI: "https://trusttasks.org/spec/persona/attribute/get/1.0";
+/** Stable alias for this specification's request payload shape. */
+export type Payload = PersonaAttributeGetPayload;
+/** Trust Task response type URI (request type URI + "#response"). */
+export declare const RESPONSE_TYPE_URI: "https://trusttasks.org/spec/persona/attribute/get/1.0#response";
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = PersonaAttributeGetResponsePayload;
+/**
+ * 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/persona/attribute/get/1.0";
+    readonly title: "Persona Attribute — Get — payload";
+    readonly description: "Read one attribute the holder holds, by identifier. Values are withheld unless asked for, on the same two-step as persona/attribute/list: the expensive, disclosing path is the one a producer has to name.";
+    readonly type: "object";
+    readonly additionalProperties: false;
+    readonly required: readonly ["attributeId"];
+    readonly properties: {
+        readonly attributeId: {
+            readonly $ref: "#/$defs/Ulid";
+            readonly description: "The attribute to read. One identifier, never a list: a maintainer that accepted several would recreate the enumeration this task exists to avoid.";
+        };
+        readonly includeValue: {
+            readonly type: "boolean";
+            readonly default: false;
+            readonly description: "When false (the default), the attribute's metadata is returned and its `value` is not. The default is false even though a caller naming one attribute usually wants its value, because the alternative makes the disclosing path the one nobody has to ask for — and the audit row can then say whether plaintext left, which is the question worth being able to answer later.";
+            readonly $comment: "Mirrors includeValues on persona/attribute/list. The plural is a listing of many; this is one.";
+        };
+        readonly includeSensitive: {
+            readonly type: "boolean";
+            readonly default: false;
+            readonly description: "When false (the default), a request that asked for the value still does not receive it for an attribute resolving to `sensitivity: high` — the metadata is returned, the plaintext is not. Setting it asks for that too.\n\nThe second flag is not ceremony. A consumer that masks a value it has already received defends a screen; it does not keep a passport number out of a log, a crash dump, or a process's memory. The value never being sent is what does.";
+        };
+        readonly version: {
+            readonly $ref: "#/$defs/Version";
+            readonly description: "Read a retained earlier version instead of the current one. Absent means current.\n\nThis is what makes \"what did I show them in March\" answerable: a disclosure record and a pinned profile entry both name a version, and without this a caller holding one has no way to read what it said. A version the holder has purged is `persona/attribute/get:versionPurged` — never a silent fall back to the current value, which would answer a question about the past with a fact about the present.";
+        };
+        readonly ext: {
+            readonly $ref: "#/$defs/Ext";
+        };
+    };
+    readonly $defs: {
+        readonly Response: {
+            readonly $anchor: "response";
+            readonly title: "Persona Attribute — Get — response payload";
+            readonly description: "Success response to persona/attribute/get. Type https://trusttasks.org/spec/persona/attribute/get/1.0#response.";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["attribute"];
+            readonly properties: {
+                readonly attribute: {
+                    readonly $ref: "#/$defs/Attribute";
+                    readonly description: "The attribute as at `version`, or as it stands when none was asked for. Its `value` is present only if the request asked for it and the attribute's sensitivity permitted it.";
+                };
+                readonly valueWithheld: {
+                    readonly type: "boolean";
+                    readonly description: "True when the value was withheld although `includeValue` asked for it — the attribute resolves to `sensitivity: high` and `includeSensitive` was not set. Stated rather than left to inference: a consumer that reads an absent `value` as \"this attribute has none\" will show the holder an empty field where a passport number is, and conclude the record is broken.";
+                };
+                readonly retainedVersions: {
+                    readonly type: "array";
+                    readonly maxItems: 64;
+                    readonly description: "The versions of this attribute the maintainer still holds, newest first, including the current one. Names versions and never their values.\n\nIt is here because a holder deciding whether to purge cannot see what purging would take away: which earlier versions exist, and therefore which pinned profile entries would stop presenting. A consumer that cannot enumerate them asks the holder to make an irreversible decision blind.";
+                    readonly items: {
+                        readonly $ref: "#/$defs/Version";
+                    };
+                };
+                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 Version: {
+            readonly title: "Version";
+            readonly description: "A value of the store's monotonic write counter. Server-assigned; a producer never chooses one.";
+            readonly type: "integer";
+            readonly minimum: 1;
+        };
+        readonly Attribute: {
+            readonly title: "Attribute";
+            readonly description: "One atomic fact a holder keeps about themselves. Several attributes MAY share a `type` — three phone numbers, a legal name and a preferred name — which is why `attributeId` is the identity of a fact and `type` is not. The pool is flat and unordered; ordering is a profile's concern.";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["attributeId", "type", "valueType", "provenance", "version", "updatedAt"];
+            readonly properties: {
+                readonly attributeId: {
+                    readonly $ref: "#/$defs/Ulid";
+                };
+                readonly type: {
+                    readonly $ref: "#/$defs/ClaimType";
+                };
+                readonly valueType: {
+                    readonly $ref: "#/$defs/ValueType";
+                };
+                readonly value: {
+                    readonly description: "The fact itself, agreeing with `valueType`. Encrypted at rest by the maintainer.\n\nOPTIONAL, and its absence is meaningful in two distinct situations a consumer MUST NOT conflate: the caller asked for a metadata-only view (`list` without `includeValues`, which is the DEFAULT and the common case), or a credential-backed value could not be re-derived. `stale` tells them apart. Requiring this member would make the default listing unrepresentable — a maintainer would have to choose between disclosing every value in bulk and emitting a non-conformant response.";
+                };
+                readonly label: {
+                    readonly type: "string";
+                    readonly maxLength: 128;
+                    readonly description: "The holder's own words for this attribute, shown in a picker. Never disclosed to a verifier; it is a note to self.";
+                };
+                readonly provenance: {
+                    readonly $ref: "#/$defs/Provenance";
+                };
+                readonly stale: {
+                    readonly type: "boolean";
+                    readonly description: "Present and true when a `credentialBacked` value could not be re-derived. `staleReason` says why. A maintainer MUST refuse to disclose a stale attribute.";
+                };
+                readonly staleReason: {
+                    readonly type: "string";
+                    readonly enum: readonly ["revoked", "expired", "archived", "deleted", "notFound"];
+                    readonly description: "Why re-derivation failed. Present only alongside `stale`.";
+                };
+                readonly sensitivity: {
+                    readonly $ref: "#/$defs/Sensitivity";
+                    readonly description: "Set only where the holder decided it explicitly. Absent resolves from the claim-type registry — see CLAIM-TYPES.md §4, 'store the override, derive the default'.";
+                };
+                readonly release: {
+                    readonly $ref: "#/$defs/ReleaseRequirement";
+                    readonly description: "Set only where the holder decided it explicitly. Absent resolves from the claim-type registry.";
+                };
+                readonly endorsements: {
+                    readonly type: "array";
+                    readonly maxItems: 64;
+                    readonly uniqueItems: true;
+                    readonly items: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                    };
+                    readonly description: "Vault identifiers of credentials in which a third party endorses this value — a colleague vouching for a skill, an employer confirming a title. INVENTORY, not evidence: the value remains whatever its `provenance` says, and a vouched self-assertion is still self-asserted. Folding a vouch into `provenance` would make it render as attested, which is the one thing provenance exists to prevent. Not disclosed with the value; a holder who wants a counterparty to see an endorsement presents the credential itself. Absent when there are none.";
+                };
+                readonly version: {
+                    readonly $ref: "#/$defs/Version";
+                };
+                readonly retainedVersions: {
+                    readonly type: "array";
+                    readonly maxItems: 64;
+                    readonly description: "Earlier versions of this attribute the maintainer still holds, and why. A maintainer that keeps a replaced value to serve `pinVersion` MUST list it here: a holder who overwrote a value may reasonably believe it gone, and this is how they learn otherwise. Values are not included — the holder reads one through the profile that pins it, or removes it with persona/attribute/purge-version. Absent when none are held.";
+                    readonly items: {
+                        readonly type: "object";
+                        readonly additionalProperties: false;
+                        readonly required: readonly ["version", "pinnedBy"];
+                        readonly properties: {
+                            readonly version: {
+                                readonly $ref: "#/$defs/Version";
+                            };
+                            readonly updatedAt: {
+                                readonly type: "string";
+                                readonly format: "date-time";
+                                readonly description: "When this version was written.";
+                            };
+                            readonly pinnedBy: {
+                                readonly type: "array";
+                                readonly minItems: 1;
+                                readonly maxItems: 256;
+                                readonly items: {
+                                    readonly $ref: "#/$defs/Ulid";
+                                };
+                                readonly description: "The profiles pinning this version — the reason it is kept. A version no profile pins is not retained.";
+                            };
+                        };
+                    };
+                };
+                readonly createdAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                };
+                readonly updatedAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                };
+            };
+        };
+        readonly Ulid: {
+            readonly title: "Ulid";
+            readonly description: "A ULID in Crockford base32, uppercase. Used for `attributeId` and `profileId`. Chosen over a UUID because the leading 48 bits are a timestamp, so a key-ordered scan of the store is also creation-ordered and a `list` needs no secondary sort. Server-assigned on create; a producer MAY supply one to make a create idempotent, and a maintainer MUST reject a supplied value that already exists rather than silently overwriting.";
+            readonly type: "string";
+            readonly pattern: "^[0-9A-HJKMNP-TV-Z]{26}$";
+        };
+        readonly ReleaseRequirement: {
+            readonly title: "ReleaseRequirement";
+            readonly description: "What it takes to let a value LEAVE. Distinct from `Sensitivity`, which governs showing it to the holder.\n\n`consent` is the ordinary gate: `persona/disclosure/preview` renders what would leave and `persona/disclosure/present` releases it, so a human sees it once.\n\n`stepUp` additionally requires a fresh authentication bound to THAT preview — not to the session. Without the binding, \"each time\" degrades into \"once per login\", which is the failure the requirement exists to prevent; the single-use `previewId` the preview already mints is what an implementation binds to. A maintainer MUST refuse `persona/disclosure/present` for a `stepUp` attribute when no such approval accompanies it.\n\nAbsent means *not decided by the holder* and resolves from the claim-type registry, which defaults `payment.*` and `gov.*` to `stepUp`.";
+            readonly type: "string";
+            readonly enum: readonly ["consent", "stepUp"];
+        };
+        readonly Sensitivity: {
+            readonly title: "Sensitivity";
+            readonly description: "How carefully a value is shown TO ITS OWN HOLDER. `high` means a consumer masks it by default, reveals it one attribute at a time on a deliberate act, and — the half that is not cosmetic — omits it from a listing that did not ask for sensitive values.\n\nAbsent means *not decided by the holder*, not `normal`: a consumer resolves it from the claim-type registry (see CLAIM-TYPES.md §4), which is why this member is optional and why an unregistered token resolves conservatively rather than permissively.\n\nDistinct from how linkable the value is. A payment card is highly sensitive and barely linkable — every card number is unique, so knowing one tells a second verifier nothing about the first. Reading either as a proxy for the other produces a consumer that hides the wrong things.";
+            readonly type: "string";
+            readonly enum: readonly ["normal", "high"];
+        };
+        readonly Provenance: {
+            readonly title: "Provenance";
+            readonly description: "Where a value comes from, and the member that makes this family worth building on a trust stack rather than in an address book. It survives to the verifier, so a recipient can tell — per field — what the holder typed from what an issuer attested.\n\n`selfAsserted` — the holder supplied it.\n\n`credentialBacked` — the value is derived from a credential in the vault at `claimPath`. The stored value is a CACHE FOR DISPLAY; the credential is the truth. A maintainer MUST re-derive it on read and MUST fail closed (never presenting a stale value) when the credential has been revoked, has expired, or has been archived or deleted.\n\n`generated` — the value is minted per verifier at disclosure time and recorded against that verifier, so every relying party receives a different one that routes back to the holder. This is the shape of the most widely adopted consumer privacy feature in this space; a maintainer need not operate a relay to conform, but the shape must exist, because retrofitting per-verifier values into a pool-of-values model is a migration rather than an addition.\n\n`derived` — the value was taken from a source the holder connected or supplied — a code-hosting profile, an uploaded CV — rather than typed by them or attested by an issuer. Nobody signed it: it is the holder's claim that the source said so, and a consumer MUST NOT present it as attested. It exists as its own kind because a derived value is neither of the others — the holder did not author it, and no one vouches for it — and a holder deciding whether to disclose deserves to know which of their values they typed.\n\nFor how strongly a disclosed value identifies the holder, the kinds rank `credentialBacked` above `derived` above `selfAsserted`; `generated` values are per-verifier and do not correlate.";
+            readonly type: "object";
+            readonly required: readonly ["kind"];
+            readonly oneOf: readonly [{
+                readonly additionalProperties: false;
+                readonly required: readonly ["kind"];
+                readonly properties: {
+                    readonly kind: {
+                        readonly const: "selfAsserted";
+                    };
+                };
+            }, {
+                readonly additionalProperties: false;
+                readonly required: readonly ["kind", "credentialId", "claimPath"];
+                readonly properties: {
+                    readonly kind: {
+                        readonly const: "credentialBacked";
+                    };
+                    readonly credentialId: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "Vault identifier of the backing credential.";
+                    };
+                    readonly claimPath: {
+                        readonly type: "string";
+                        readonly pattern: "^(/[^/~]*(~[01][^/~]*)*)*$";
+                        readonly description: "RFC 6901 JSON Pointer to the claim within the credential, e.g. `/credentialSubject/familyName`.";
+                    };
+                    readonly issuerDid: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "Issuer of the backing credential. Advisory: a consumer MUST verify the credential rather than trusting this member.";
+                    };
+                    readonly proof: {
+                        readonly $ref: "#/$defs/ProofRung";
+                        readonly description: "The disclosure rung this claim was, or will be, presented at.";
+                    };
+                };
+            }, {
+                readonly additionalProperties: false;
+                readonly required: readonly ["kind", "generator"];
+                readonly properties: {
+                    readonly kind: {
+                        readonly const: "generated";
+                    };
+                    readonly generator: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly maxLength: 64;
+                        readonly description: "Names the minting scheme, e.g. `relayEmail`. Maintainer-defined.";
+                    };
+                    readonly perVerifier: {
+                        readonly type: "boolean";
+                        readonly default: true;
+                        readonly description: "When true (the default and the only useful setting), a distinct value is minted for each verifier.";
+                    };
+                };
+            }, {
+                readonly additionalProperties: false;
+                readonly required: readonly ["kind", "source", "derivedAt"];
+                readonly properties: {
+                    readonly kind: {
+                        readonly const: "derived";
+                    };
+                    readonly source: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly maxLength: 64;
+                        readonly pattern: "^[a-z][A-Za-z0-9.-]*$";
+                        readonly description: "The KIND of source the value was taken from — `github`, `cvUpload`, `linkedIn` — never an account, handle or URL. Provenance survives to the verifier, so this member is disclosed with the claim; a handle here would disclose an identifier the holder never chose to share.";
+                    };
+                    readonly derivedAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                        readonly description: "When the value was taken from the source. A derived value is a snapshot: the source may have changed since, and nothing re-derives it.";
+                    };
+                };
+            }];
+        };
+        readonly ProofRung: {
+            readonly title: "ProofRung";
+            readonly description: "How strongly a credential-backed claim is hidden when presented, ordered most private first. `predicate` proves a statement over a claim without disclosing the claim. `derived` discloses exactly the claims needed via an unlinkable derived proof, so two presentations cannot be joined. `selectiveDisclosure` discloses exactly the claims needed but carries the issuer's signature unchanged, so two presentations ARE linkable. `whole` discloses the entire credential.\n\nThe distinction between the first two and the last two is of kind, not degree: only `predicate` and `derived` avoid handing two verifiers a join key. A maintainer MUST default to the highest rung the credential's format supports, and MUST NOT silently fall to a lower one — a request that cannot be satisfied at the rung a producer asked for is refused, because a silent privacy downgrade discloses material the holder believed was hidden.";
+            readonly type: "string";
+            readonly enum: readonly ["predicate", "derived", "selectiveDisclosure", "whole"];
+        };
+        readonly ValueType: {
+            readonly title: "ValueType";
+            readonly description: "The JSON shape of `value`, declared so that a consumer can render and compare without guessing. The maintainer validates that `value` agrees with this member and does nothing further: it does NOT validate a phone number against a phone-number grammar. That is a producer's affordance, and a store that grows opinions about the contents of its records eventually blocks its consumer's release.";
+            readonly type: "string";
+            readonly enum: readonly ["string", "number", "boolean", "date", "object"];
+        };
+        readonly ClaimType: {
+            readonly title: "ClaimType";
+            readonly description: "The vocabulary token naming what a value IS — `name.legal`, `phone.mobile`, `address.postal`, `person.birthDate`. Dotted, most-general segment first, so that a consumer with no knowledge of the specific token can still group by its prefix.\n\nThe token is the maintainer's own; no external vocabulary is primary. External vocabularies (vCard/jCard, OIDC standard claims, schema.org) are mappings applied at PRESENTATION by a renderer, not at rest, so that a query written in any of them can be matched without the store having to live inside any one of them.\n\nThe `x:` prefix is an open extension namespace and is not decoration. The closest prior art — Windows CardSpace's self-issued card — supported exactly fifteen predefined claim types with no extensibility, and that is the specific way it failed the requirement a holder actually has. An `x:` attribute stores, composes, binds and discloses exactly like a known one; it renders generically and matches only an explicit query.";
+            readonly type: "string";
+            readonly minLength: 1;
+            readonly maxLength: 128;
+            readonly pattern: "^(x:)?[a-z][a-zA-Z0-9]*(\\.[a-z][a-zA-Z0-9]*)*$";
+        };
+    };
+};
+/** As {@link PAYLOAD_SCHEMA}, for the success-response variant. */
+export declare const RESPONSE_PAYLOAD_SCHEMA: {
+    readonly $schema: "https://json-schema.org/draft/2020-12/schema";
+    readonly $ref: "#/$defs/Response";
+    readonly $defs: {
+        readonly Response: {
+            readonly $anchor: "response";
+            readonly title: "Persona Attribute — Get — response payload";
+            readonly description: "Success response to persona/attribute/get. Type https://trusttasks.org/spec/persona/attribute/get/1.0#response.";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["attribute"];
+            readonly properties: {
+                readonly attribute: {
+                    readonly $ref: "#/$defs/Attribute";
+                    readonly description: "The attribute as at `version`, or as it stands when none was asked for. Its `value` is present only if the request asked for it and the attribute's sensitivity permitted it.";
+                };
+                readonly valueWithheld: {
+                    readonly type: "boolean";
+                    readonly description: "True when the value was withheld although `includeValue` asked for it — the attribute resolves to `sensitivity: high` and `includeSensitive` was not set. Stated rather than left to inference: a consumer that reads an absent `value` as \"this attribute has none\" will show the holder an empty field where a passport number is, and conclude the record is broken.";
+                };
+                readonly retainedVersions: {
+                    readonly type: "array";
+                    readonly maxItems: 64;
+                    readonly description: "The versions of this attribute the maintainer still holds, newest first, including the current one. Names versions and never their values.\n\nIt is here because a holder deciding whether to purge cannot see what purging would take away: which earlier versions exist, and therefore which pinned profile entries would stop presenting. A consumer that cannot enumerate them asks the holder to make an irreversible decision blind.";
+                    readonly items: {
+                        readonly $ref: "#/$defs/Version";
+                    };
+                };
+                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 Version: {
+            readonly title: "Version";
+            readonly description: "A value of the store's monotonic write counter. Server-assigned; a producer never chooses one.";
+            readonly type: "integer";
+            readonly minimum: 1;
+        };
+        readonly Attribute: {
+            readonly title: "Attribute";
+            readonly description: "One atomic fact a holder keeps about themselves. Several attributes MAY share a `type` — three phone numbers, a legal name and a preferred name — which is why `attributeId` is the identity of a fact and `type` is not. The pool is flat and unordered; ordering is a profile's concern.";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["attributeId", "type", "valueType", "provenance", "version", "updatedAt"];
+            readonly properties: {
+                readonly attributeId: {
+                    readonly $ref: "#/$defs/Ulid";
+                };
+                readonly type: {
+                    readonly $ref: "#/$defs/ClaimType";
+                };
+                readonly valueType: {
+                    readonly $ref: "#/$defs/ValueType";
+                };
+                readonly value: {
+                    readonly description: "The fact itself, agreeing with `valueType`. Encrypted at rest by the maintainer.\n\nOPTIONAL, and its absence is meaningful in two distinct situations a consumer MUST NOT conflate: the caller asked for a metadata-only view (`list` without `includeValues`, which is the DEFAULT and the common case), or a credential-backed value could not be re-derived. `stale` tells them apart. Requiring this member would make the default listing unrepresentable — a maintainer would have to choose between disclosing every value in bulk and emitting a non-conformant response.";
+                };
+                readonly label: {
+                    readonly type: "string";
+                    readonly maxLength: 128;
+                    readonly description: "The holder's own words for this attribute, shown in a picker. Never disclosed to a verifier; it is a note to self.";
+                };
+                readonly provenance: {
+                    readonly $ref: "#/$defs/Provenance";
+                };
+                readonly stale: {
+                    readonly type: "boolean";
+                    readonly description: "Present and true when a `credentialBacked` value could not be re-derived. `staleReason` says why. A maintainer MUST refuse to disclose a stale attribute.";
+                };
+                readonly staleReason: {
+                    readonly type: "string";
+                    readonly enum: readonly ["revoked", "expired", "archived", "deleted", "notFound"];
+                    readonly description: "Why re-derivation failed. Present only alongside `stale`.";
+                };
+                readonly sensitivity: {
+                    readonly $ref: "#/$defs/Sensitivity";
+                    readonly description: "Set only where the holder decided it explicitly. Absent resolves from the claim-type registry — see CLAIM-TYPES.md §4, 'store the override, derive the default'.";
+                };
+                readonly release: {
+                    readonly $ref: "#/$defs/ReleaseRequirement";
+                    readonly description: "Set only where the holder decided it explicitly. Absent resolves from the claim-type registry.";
+                };
+                readonly endorsements: {
+                    readonly type: "array";
+                    readonly maxItems: 64;
+                    readonly uniqueItems: true;
+                    readonly items: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                    };
+                    readonly description: "Vault identifiers of credentials in which a third party endorses this value — a colleague vouching for a skill, an employer confirming a title. INVENTORY, not evidence: the value remains whatever its `provenance` says, and a vouched self-assertion is still self-asserted. Folding a vouch into `provenance` would make it render as attested, which is the one thing provenance exists to prevent. Not disclosed with the value; a holder who wants a counterparty to see an endorsement presents the credential itself. Absent when there are none.";
+                };
+                readonly version: {
+                    readonly $ref: "#/$defs/Version";
+                };
+                readonly retainedVersions: {
+                    readonly type: "array";
+                    readonly maxItems: 64;
+                    readonly description: "Earlier versions of this attribute the maintainer still holds, and why. A maintainer that keeps a replaced value to serve `pinVersion` MUST list it here: a holder who overwrote a value may reasonably believe it gone, and this is how they learn otherwise. Values are not included — the holder reads one through the profile that pins it, or removes it with persona/attribute/purge-version. Absent when none are held.";
+                    readonly items: {
+                        readonly type: "object";
+                        readonly additionalProperties: false;
+                        readonly required: readonly ["version", "pinnedBy"];
+                        readonly properties: {
+                            readonly version: {
+                                readonly $ref: "#/$defs/Version";
+                            };
+                            readonly updatedAt: {
+                                readonly type: "string";
+                                readonly format: "date-time";
+                                readonly description: "When this version was written.";
+                            };
+                            readonly pinnedBy: {
+                                readonly type: "array";
+                                readonly minItems: 1;
+                                readonly maxItems: 256;
+                                readonly items: {
+                                    readonly $ref: "#/$defs/Ulid";
+                                };
+                                readonly description: "The profiles pinning this version — the reason it is kept. A version no profile pins is not retained.";
+                            };
+                        };
+                    };
+                };
+                readonly createdAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                };
+                readonly updatedAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                };
+            };
+        };
+        readonly Ulid: {
+            readonly title: "Ulid";
+            readonly description: "A ULID in Crockford base32, uppercase. Used for `attributeId` and `profileId`. Chosen over a UUID because the leading 48 bits are a timestamp, so a key-ordered scan of the store is also creation-ordered and a `list` needs no secondary sort. Server-assigned on create; a producer MAY supply one to make a create idempotent, and a maintainer MUST reject a supplied value that already exists rather than silently overwriting.";
+            readonly type: "string";
+            readonly pattern: "^[0-9A-HJKMNP-TV-Z]{26}$";
+        };
+        readonly ReleaseRequirement: {
+            readonly title: "ReleaseRequirement";
+            readonly description: "What it takes to let a value LEAVE. Distinct from `Sensitivity`, which governs showing it to the holder.\n\n`consent` is the ordinary gate: `persona/disclosure/preview` renders what would leave and `persona/disclosure/present` releases it, so a human sees it once.\n\n`stepUp` additionally requires a fresh authentication bound to THAT preview — not to the session. Without the binding, \"each time\" degrades into \"once per login\", which is the failure the requirement exists to prevent; the single-use `previewId` the preview already mints is what an implementation binds to. A maintainer MUST refuse `persona/disclosure/present` for a `stepUp` attribute when no such approval accompanies it.\n\nAbsent means *not decided by the holder* and resolves from the claim-type registry, which defaults `payment.*` and `gov.*` to `stepUp`.";
+            readonly type: "string";
+            readonly enum: readonly ["consent", "stepUp"];
+        };
+        readonly Sensitivity: {
+            readonly title: "Sensitivity";
+            readonly description: "How carefully a value is shown TO ITS OWN HOLDER. `high` means a consumer masks it by default, reveals it one attribute at a time on a deliberate act, and — the half that is not cosmetic — omits it from a listing that did not ask for sensitive values.\n\nAbsent means *not decided by the holder*, not `normal`: a consumer resolves it from the claim-type registry (see CLAIM-TYPES.md §4), which is why this member is optional and why an unregistered token resolves conservatively rather than permissively.\n\nDistinct from how linkable the value is. A payment card is highly sensitive and barely linkable — every card number is unique, so knowing one tells a second verifier nothing about the first. Reading either as a proxy for the other produces a consumer that hides the wrong things.";
+            readonly type: "string";
+            readonly enum: readonly ["normal", "high"];
+        };
+        readonly Provenance: {
+            readonly title: "Provenance";
+            readonly description: "Where a value comes from, and the member that makes this family worth building on a trust stack rather than in an address book. It survives to the verifier, so a recipient can tell — per field — what the holder typed from what an issuer attested.\n\n`selfAsserted` — the holder supplied it.\n\n`credentialBacked` — the value is derived from a credential in the vault at `claimPath`. The stored value is a CACHE FOR DISPLAY; the credential is the truth. A maintainer MUST re-derive it on read and MUST fail closed (never presenting a stale value) when the credential has been revoked, has expired, or has been archived or deleted.\n\n`generated` — the value is minted per verifier at disclosure time and recorded against that verifier, so every relying party receives a different one that routes back to the holder. This is the shape of the most widely adopted consumer privacy feature in this space; a maintainer need not operate a relay to conform, but the shape must exist, because retrofitting per-verifier values into a pool-of-values model is a migration rather than an addition.\n\n`derived` — the value was taken from a source the holder connected or supplied — a code-hosting profile, an uploaded CV — rather than typed by them or attested by an issuer. Nobody signed it: it is the holder's claim that the source said so, and a consumer MUST NOT present it as attested. It exists as its own kind because a derived value is neither of the others — the holder did not author it, and no one vouches for it — and a holder deciding whether to disclose deserves to know which of their values they typed.\n\nFor how strongly a disclosed value identifies the holder, the kinds rank `credentialBacked` above `derived` above `selfAsserted`; `generated` values are per-verifier and do not correlate.";
+            readonly type: "object";
+            readonly required: readonly ["kind"];
+            readonly oneOf: readonly [{
+                readonly additionalProperties: false;
+                readonly required: readonly ["kind"];
+                readonly properties: {
+                    readonly kind: {
+                        readonly const: "selfAsserted";
+                    };
+                };
+            }, {
+                readonly additionalProperties: false;
+                readonly required: readonly ["kind", "credentialId", "claimPath"];
+                readonly properties: {
+                    readonly kind: {
+                        readonly const: "credentialBacked";
+                    };
+                    readonly credentialId: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "Vault identifier of the backing credential.";
+                    };
+                    readonly claimPath: {
+                        readonly type: "string";
+                        readonly pattern: "^(/[^/~]*(~[01][^/~]*)*)*$";
+                        readonly description: "RFC 6901 JSON Pointer to the claim within the credential, e.g. `/credentialSubject/familyName`.";
+                    };
+                    readonly issuerDid: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "Issuer of the backing credential. Advisory: a consumer MUST verify the credential rather than trusting this member.";
+                    };
+                    readonly proof: {
+                        readonly $ref: "#/$defs/ProofRung";
+                        readonly description: "The disclosure rung this claim was, or will be, presented at.";
+                    };
+                };
+            }, {
+                readonly additionalProperties: false;
+                readonly required: readonly ["kind", "generator"];
+                readonly properties: {
+                    readonly kind: {
+                        readonly const: "generated";
+                    };
+                    readonly generator: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly maxLength: 64;
+                        readonly description: "Names the minting scheme, e.g. `relayEmail`. Maintainer-defined.";
+                    };
+                    readonly perVerifier: {
+                        readonly type: "boolean";
+                        readonly default: true;
+                        readonly description: "When true (the default and the only useful setting), a distinct value is minted for each verifier.";
+                    };
+                };
+            }, {
+                readonly additionalProperties: false;
+                readonly required: readonly ["kind", "source", "derivedAt"];
+                readonly properties: {
+                    readonly kind: {
+                        readonly const: "derived";
+                    };
+                    readonly source: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly maxLength: 64;
+                        readonly pattern: "^[a-z][A-Za-z0-9.-]*$";
+                        readonly description: "The KIND of source the value was taken from — `github`, `cvUpload`, `linkedIn` — never an account, handle or URL. Provenance survives to the verifier, so this member is disclosed with the claim; a handle here would disclose an identifier the holder never chose to share.";
+                    };
+                    readonly derivedAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                        readonly description: "When the value was taken from the source. A derived value is a snapshot: the source may have changed since, and nothing re-derives it.";
+                    };
+                };
+            }];
+        };
+        readonly ProofRung: {
+            readonly title: "ProofRung";
+            readonly description: "How strongly a credential-backed claim is hidden when presented, ordered most private first. `predicate` proves a statement over a claim without disclosing the claim. `derived` discloses exactly the claims needed via an unlinkable derived proof, so two presentations cannot be joined. `selectiveDisclosure` discloses exactly the claims needed but carries the issuer's signature unchanged, so two presentations ARE linkable. `whole` discloses the entire credential.\n\nThe distinction between the first two and the last two is of kind, not degree: only `predicate` and `derived` avoid handing two verifiers a join key. A maintainer MUST default to the highest rung the credential's format supports, and MUST NOT silently fall to a lower one — a request that cannot be satisfied at the rung a producer asked for is refused, because a silent privacy downgrade discloses material the holder believed was hidden.";
+            readonly type: "string";
+            readonly enum: readonly ["predicate", "derived", "selectiveDisclosure", "whole"];
+        };
+        readonly ValueType: {
+            readonly title: "ValueType";
+            readonly description: "The JSON shape of `value`, declared so that a consumer can render and compare without guessing. The maintainer validates that `value` agrees with this member and does nothing further: it does NOT validate a phone number against a phone-number grammar. That is a producer's affordance, and a store that grows opinions about the contents of its records eventually blocks its consumer's release.";
+            readonly type: "string";
+            readonly enum: readonly ["string", "number", "boolean", "date", "object"];
+        };
+        readonly ClaimType: {
+            readonly title: "ClaimType";
+            readonly description: "The vocabulary token naming what a value IS — `name.legal`, `phone.mobile`, `address.postal`, `person.birthDate`. Dotted, most-general segment first, so that a consumer with no knowledge of the specific token can still group by its prefix.\n\nThe token is the maintainer's own; no external vocabulary is primary. External vocabularies (vCard/jCard, OIDC standard claims, schema.org) are mappings applied at PRESENTATION by a renderer, not at rest, so that a query written in any of them can be matched without the store having to live inside any one of them.\n\nThe `x:` prefix is an open extension namespace and is not decoration. The closest prior art — Windows CardSpace's self-issued card — supported exactly fifteen predefined claim types with no extensibility, and that is the specific way it failed the requirement a holder actually has. An `x:` attribute stores, composes, binds and discloses exactly like a known one; it renders generically and matches only an explicit query.";
+            readonly type: "string";
+            readonly minLength: 1;
+            readonly maxLength: 128;
+            readonly pattern: "^(x:)?[a-z][a-zA-Z0-9]*(\\.[a-z][a-zA-Z0-9]*)*$";
+        };
+    };
+};
+/**
+ * SPEC.md §7.2 policy for the request variant, from this specification's
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
+ * per-specification and cannot be derived from the document alone, and
+ * item 2 needs the schema this carries.
+ */
+export declare const SPEC: {
+    readonly typeUri: "https://trusttasks.org/spec/persona/attribute/get/1.0";
+    readonly isBearer: false;
+    readonly isProofRequired: true;
+    readonly isRecipientRequired: true;
+    readonly isIssuedAtRequired: false;
+    readonly payloadSchema: {
+        readonly $schema: "https://json-schema.org/draft/2020-12/schema";
+        readonly $id: "https://trusttasks.org/spec/persona/attribute/get/1.0";
+        readonly title: "Persona Attribute — Get — payload";
+        readonly description: "Read one attribute the holder holds, by identifier. Values are withheld unless asked for, on the same two-step as persona/attribute/list: the expensive, disclosing path is the one a producer has to name.";
+        readonly type: "object";
+        readonly additionalProperties: false;
+        readonly required: readonly ["attributeId"];
+        readonly properties: {
+            readonly attributeId: {
+                readonly $ref: "#/$defs/Ulid";
+                readonly description: "The attribute to read. One identifier, never a list: a maintainer that accepted several would recreate the enumeration this task exists to avoid.";
+            };
+            readonly includeValue: {
+                readonly type: "boolean";
+                readonly default: false;
+                readonly description: "When false (the default), the attribute's metadata is returned and its `value` is not. The default is false even though a caller naming one attribute usually wants its value, because the alternative makes the disclosing path the one nobody has to ask for — and the audit row can then say whether plaintext left, which is the question worth being able to answer later.";
+                readonly $comment: "Mirrors includeValues on persona/attribute/list. The plural is a listing of many; this is one.";
+            };
+            readonly includeSensitive: {
+                readonly type: "boolean";
+                readonly default: false;
+                readonly description: "When false (the default), a request that asked for the value still does not receive it for an attribute resolving to `sensitivity: high` — the metadata is returned, the plaintext is not. Setting it asks for that too.\n\nThe second flag is not ceremony. A consumer that masks a value it has already received defends a screen; it does not keep a passport number out of a log, a crash dump, or a process's memory. The value never being sent is what does.";
+            };
+            readonly version: {
+                readonly $ref: "#/$defs/Version";
+                readonly description: "Read a retained earlier version instead of the current one. Absent means current.\n\nThis is what makes \"what did I show them in March\" answerable: a disclosure record and a pinned profile entry both name a version, and without this a caller holding one has no way to read what it said. A version the holder has purged is `persona/attribute/get:versionPurged` — never a silent fall back to the current value, which would answer a question about the past with a fact about the present.";
+            };
+            readonly ext: {
+                readonly $ref: "#/$defs/Ext";
+            };
+        };
+        readonly $defs: {
+            readonly Response: {
+                readonly $anchor: "response";
+                readonly title: "Persona Attribute — Get — response payload";
+                readonly description: "Success response to persona/attribute/get. Type https://trusttasks.org/spec/persona/attribute/get/1.0#response.";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["attribute"];
+                readonly properties: {
+                    readonly attribute: {
+                        readonly $ref: "#/$defs/Attribute";
+                        readonly description: "The attribute as at `version`, or as it stands when none was asked for. Its `value` is present only if the request asked for it and the attribute's sensitivity permitted it.";
+                    };
+                    readonly valueWithheld: {
+                        readonly type: "boolean";
+                        readonly description: "True when the value was withheld although `includeValue` asked for it — the attribute resolves to `sensitivity: high` and `includeSensitive` was not set. Stated rather than left to inference: a consumer that reads an absent `value` as \"this attribute has none\" will show the holder an empty field where a passport number is, and conclude the record is broken.";
+                    };
+                    readonly retainedVersions: {
+                        readonly type: "array";
+                        readonly maxItems: 64;
+                        readonly description: "The versions of this attribute the maintainer still holds, newest first, including the current one. Names versions and never their values.\n\nIt is here because a holder deciding whether to purge cannot see what purging would take away: which earlier versions exist, and therefore which pinned profile entries would stop presenting. A consumer that cannot enumerate them asks the holder to make an irreversible decision blind.";
+                        readonly items: {
+                            readonly $ref: "#/$defs/Version";
+                        };
+                    };
+                    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 Version: {
+                readonly title: "Version";
+                readonly description: "A value of the store's monotonic write counter. Server-assigned; a producer never chooses one.";
+                readonly type: "integer";
+                readonly minimum: 1;
+            };
+            readonly Attribute: {
+                readonly title: "Attribute";
+                readonly description: "One atomic fact a holder keeps about themselves. Several attributes MAY share a `type` — three phone numbers, a legal name and a preferred name — which is why `attributeId` is the identity of a fact and `type` is not. The pool is flat and unordered; ordering is a profile's concern.";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["attributeId", "type", "valueType", "provenance", "version", "updatedAt"];
+                readonly properties: {
+                    readonly attributeId: {
+                        readonly $ref: "#/$defs/Ulid";
+                    };
+                    readonly type: {
+                        readonly $ref: "#/$defs/ClaimType";
+                    };
+                    readonly valueType: {
+                        readonly $ref: "#/$defs/ValueType";
+                    };
+                    readonly value: {
+                        readonly description: "The fact itself, agreeing with `valueType`. Encrypted at rest by the maintainer.\n\nOPTIONAL, and its absence is meaningful in two distinct situations a consumer MUST NOT conflate: the caller asked for a metadata-only view (`list` without `includeValues`, which is the DEFAULT and the common case), or a credential-backed value could not be re-derived. `stale` tells them apart. Requiring this member would make the default listing unrepresentable — a maintainer would have to choose between disclosing every value in bulk and emitting a non-conformant response.";
+                    };
+                    readonly label: {
+                        readonly type: "string";
+                        readonly maxLength: 128;
+                        readonly description: "The holder's own words for this attribute, shown in a picker. Never disclosed to a verifier; it is a note to self.";
+                    };
+                    readonly provenance: {
+                        readonly $ref: "#/$defs/Provenance";
+                    };
+                    readonly stale: {
+                        readonly type: "boolean";
+                        readonly description: "Present and true when a `credentialBacked` value could not be re-derived. `staleReason` says why. A maintainer MUST refuse to disclose a stale attribute.";
+                    };
+                    readonly staleReason: {
+                        readonly type: "string";
+                        readonly enum: readonly ["revoked", "expired", "archived", "deleted", "notFound"];
+                        readonly description: "Why re-derivation failed. Present only alongside `stale`.";
+                    };
+                    readonly sensitivity: {
+                        readonly $ref: "#/$defs/Sensitivity";
+                        readonly description: "Set only where the holder decided it explicitly. Absent resolves from the claim-type registry — see CLAIM-TYPES.md §4, 'store the override, derive the default'.";
+                    };
+                    readonly release: {
+                        readonly $ref: "#/$defs/ReleaseRequirement";
+                        readonly description: "Set only where the holder decided it explicitly. Absent resolves from the claim-type registry.";
+                    };
+                    readonly endorsements: {
+                        readonly type: "array";
+                        readonly maxItems: 64;
+                        readonly uniqueItems: true;
+                        readonly items: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                        };
+                        readonly description: "Vault identifiers of credentials in which a third party endorses this value — a colleague vouching for a skill, an employer confirming a title. INVENTORY, not evidence: the value remains whatever its `provenance` says, and a vouched self-assertion is still self-asserted. Folding a vouch into `provenance` would make it render as attested, which is the one thing provenance exists to prevent. Not disclosed with the value; a holder who wants a counterparty to see an endorsement presents the credential itself. Absent when there are none.";
+                    };
+                    readonly version: {
+                        readonly $ref: "#/$defs/Version";
+                    };
+                    readonly retainedVersions: {
+                        readonly type: "array";
+                        readonly maxItems: 64;
+                        readonly description: "Earlier versions of this attribute the maintainer still holds, and why. A maintainer that keeps a replaced value to serve `pinVersion` MUST list it here: a holder who overwrote a value may reasonably believe it gone, and this is how they learn otherwise. Values are not included — the holder reads one through the profile that pins it, or removes it with persona/attribute/purge-version. Absent when none are held.";
+                        readonly items: {
+                            readonly type: "object";
+                            readonly additionalProperties: false;
+                            readonly required: readonly ["version", "pinnedBy"];
+                            readonly properties: {
+                                readonly version: {
+                                    readonly $ref: "#/$defs/Version";
+                                };
+                                readonly updatedAt: {
+                                    readonly type: "string";
+                                    readonly format: "date-time";
+                                    readonly description: "When this version was written.";
+                                };
+                                readonly pinnedBy: {
+                                    readonly type: "array";
+                                    readonly minItems: 1;
+                                    readonly maxItems: 256;
+                                    readonly items: {
+                                        readonly $ref: "#/$defs/Ulid";
+                                    };
+                                    readonly description: "The profiles pinning this version — the reason it is kept. A version no profile pins is not retained.";
+                                };
+                            };
+                        };
+                    };
+                    readonly createdAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                    };
+                    readonly updatedAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                    };
+                };
+            };
+            readonly Ulid: {
+                readonly title: "Ulid";
+                readonly description: "A ULID in Crockford base32, uppercase. Used for `attributeId` and `profileId`. Chosen over a UUID because the leading 48 bits are a timestamp, so a key-ordered scan of the store is also creation-ordered and a `list` needs no secondary sort. Server-assigned on create; a producer MAY supply one to make a create idempotent, and a maintainer MUST reject a supplied value that already exists rather than silently overwriting.";
+                readonly type: "string";
+                readonly pattern: "^[0-9A-HJKMNP-TV-Z]{26}$";
+            };
+            readonly ReleaseRequirement: {
+                readonly title: "ReleaseRequirement";
+                readonly description: "What it takes to let a value LEAVE. Distinct from `Sensitivity`, which governs showing it to the holder.\n\n`consent` is the ordinary gate: `persona/disclosure/preview` renders what would leave and `persona/disclosure/present` releases it, so a human sees it once.\n\n`stepUp` additionally requires a fresh authentication bound to THAT preview — not to the session. Without the binding, \"each time\" degrades into \"once per login\", which is the failure the requirement exists to prevent; the single-use `previewId` the preview already mints is what an implementation binds to. A maintainer MUST refuse `persona/disclosure/present` for a `stepUp` attribute when no such approval accompanies it.\n\nAbsent means *not decided by the holder* and resolves from the claim-type registry, which defaults `payment.*` and `gov.*` to `stepUp`.";
+                readonly type: "string";
+                readonly enum: readonly ["consent", "stepUp"];
+            };
+            readonly Sensitivity: {
+                readonly title: "Sensitivity";
+                readonly description: "How carefully a value is shown TO ITS OWN HOLDER. `high` means a consumer masks it by default, reveals it one attribute at a time on a deliberate act, and — the half that is not cosmetic — omits it from a listing that did not ask for sensitive values.\n\nAbsent means *not decided by the holder*, not `normal`: a consumer resolves it from the claim-type registry (see CLAIM-TYPES.md §4), which is why this member is optional and why an unregistered token resolves conservatively rather than permissively.\n\nDistinct from how linkable the value is. A payment card is highly sensitive and barely linkable — every card number is unique, so knowing one tells a second verifier nothing about the first. Reading either as a proxy for the other produces a consumer that hides the wrong things.";
+                readonly type: "string";
+                readonly enum: readonly ["normal", "high"];
+            };
+            readonly Provenance: {
+                readonly title: "Provenance";
+                readonly description: "Where a value comes from, and the member that makes this family worth building on a trust stack rather than in an address book. It survives to the verifier, so a recipient can tell — per field — what the holder typed from what an issuer attested.\n\n`selfAsserted` — the holder supplied it.\n\n`credentialBacked` — the value is derived from a credential in the vault at `claimPath`. The stored value is a CACHE FOR DISPLAY; the credential is the truth. A maintainer MUST re-derive it on read and MUST fail closed (never presenting a stale value) when the credential has been revoked, has expired, or has been archived or deleted.\n\n`generated` — the value is minted per verifier at disclosure time and recorded against that verifier, so every relying party receives a different one that routes back to the holder. This is the shape of the most widely adopted consumer privacy feature in this space; a maintainer need not operate a relay to conform, but the shape must exist, because retrofitting per-verifier values into a pool-of-values model is a migration rather than an addition.\n\n`derived` — the value was taken from a source the holder connected or supplied — a code-hosting profile, an uploaded CV — rather than typed by them or attested by an issuer. Nobody signed it: it is the holder's claim that the source said so, and a consumer MUST NOT present it as attested. It exists as its own kind because a derived value is neither of the others — the holder did not author it, and no one vouches for it — and a holder deciding whether to disclose deserves to know which of their values they typed.\n\nFor how strongly a disclosed value identifies the holder, the kinds rank `credentialBacked` above `derived` above `selfAsserted`; `generated` values are per-verifier and do not correlate.";
+                readonly type: "object";
+                readonly required: readonly ["kind"];
+                readonly oneOf: readonly [{
+                    readonly additionalProperties: false;
+                    readonly required: readonly ["kind"];
+                    readonly properties: {
+                        readonly kind: {
+                            readonly const: "selfAsserted";
+                        };
+                    };
+                }, {
+                    readonly additionalProperties: false;
+                    readonly required: readonly ["kind", "credentialId", "claimPath"];
+                    readonly properties: {
+                        readonly kind: {
+                            readonly const: "credentialBacked";
+                        };
+                        readonly credentialId: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                            readonly description: "Vault identifier of the backing credential.";
+                        };
+                        readonly claimPath: {
+                            readonly type: "string";
+                            readonly pattern: "^(/[^/~]*(~[01][^/~]*)*)*$";
+                            readonly description: "RFC 6901 JSON Pointer to the claim within the credential, e.g. `/credentialSubject/familyName`.";
+                        };
+                        readonly issuerDid: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                            readonly description: "Issuer of the backing credential. Advisory: a consumer MUST verify the credential rather than trusting this member.";
+                        };
+                        readonly proof: {
+                            readonly $ref: "#/$defs/ProofRung";
+                            readonly description: "The disclosure rung this claim was, or will be, presented at.";
+                        };
+                    };
+                }, {
+                    readonly additionalProperties: false;
+                    readonly required: readonly ["kind", "generator"];
+                    readonly properties: {
+                        readonly kind: {
+                            readonly const: "generated";
+                        };
+                        readonly generator: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                            readonly maxLength: 64;
+                            readonly description: "Names the minting scheme, e.g. `relayEmail`. Maintainer-defined.";
+                        };
+                        readonly perVerifier: {
+                            readonly type: "boolean";
+                            readonly default: true;
+                            readonly description: "When true (the default and the only useful setting), a distinct value is minted for each verifier.";
+                        };
+                    };
+                }, {
+                    readonly additionalProperties: false;
+                    readonly required: readonly ["kind", "source", "derivedAt"];
+                    readonly properties: {
+                        readonly kind: {
+                            readonly const: "derived";
+                        };
+                        readonly source: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                            readonly maxLength: 64;
+                            readonly pattern: "^[a-z][A-Za-z0-9.-]*$";
+                            readonly description: "The KIND of source the value was taken from — `github`, `cvUpload`, `linkedIn` — never an account, handle or URL. Provenance survives to the verifier, so this member is disclosed with the claim; a handle here would disclose an identifier the holder never chose to share.";
+                        };
+                        readonly derivedAt: {
+                            readonly type: "string";
+                            readonly format: "date-time";
+                            readonly description: "When the value was taken from the source. A derived value is a snapshot: the source may have changed since, and nothing re-derives it.";
+                        };
+                    };
+                }];
+            };
+            readonly ProofRung: {
+                readonly title: "ProofRung";
+                readonly description: "How strongly a credential-backed claim is hidden when presented, ordered most private first. `predicate` proves a statement over a claim without disclosing the claim. `derived` discloses exactly the claims needed via an unlinkable derived proof, so two presentations cannot be joined. `selectiveDisclosure` discloses exactly the claims needed but carries the issuer's signature unchanged, so two presentations ARE linkable. `whole` discloses the entire credential.\n\nThe distinction between the first two and the last two is of kind, not degree: only `predicate` and `derived` avoid handing two verifiers a join key. A maintainer MUST default to the highest rung the credential's format supports, and MUST NOT silently fall to a lower one — a request that cannot be satisfied at the rung a producer asked for is refused, because a silent privacy downgrade discloses material the holder believed was hidden.";
+                readonly type: "string";
+                readonly enum: readonly ["predicate", "derived", "selectiveDisclosure", "whole"];
+            };
+            readonly ValueType: {
+                readonly title: "ValueType";
+                readonly description: "The JSON shape of `value`, declared so that a consumer can render and compare without guessing. The maintainer validates that `value` agrees with this member and does nothing further: it does NOT validate a phone number against a phone-number grammar. That is a producer's affordance, and a store that grows opinions about the contents of its records eventually blocks its consumer's release.";
+                readonly type: "string";
+                readonly enum: readonly ["string", "number", "boolean", "date", "object"];
+            };
+            readonly ClaimType: {
+                readonly title: "ClaimType";
+                readonly description: "The vocabulary token naming what a value IS — `name.legal`, `phone.mobile`, `address.postal`, `person.birthDate`. Dotted, most-general segment first, so that a consumer with no knowledge of the specific token can still group by its prefix.\n\nThe token is the maintainer's own; no external vocabulary is primary. External vocabularies (vCard/jCard, OIDC standard claims, schema.org) are mappings applied at PRESENTATION by a renderer, not at rest, so that a query written in any of them can be matched without the store having to live inside any one of them.\n\nThe `x:` prefix is an open extension namespace and is not decoration. The closest prior art — Windows CardSpace's self-issued card — supported exactly fifteen predefined claim types with no extensibility, and that is the specific way it failed the requirement a holder actually has. An `x:` attribute stores, composes, binds and discloses exactly like a known one; it renders generically and matches only an explicit query.";
+                readonly type: "string";
+                readonly minLength: 1;
+                readonly maxLength: 128;
+                readonly pattern: "^(x:)?[a-z][a-zA-Z0-9]*(\\.[a-z][a-zA-Z0-9]*)*$";
+            };
+        };
+    };
+};
+/**
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
+ * tracks the *issuer* party's requirement because a response swaps the
+ * parties (§7.3 item 5).
+ */
+export declare const RESPONSE_SPEC: {
+    readonly typeUri: "https://trusttasks.org/spec/persona/attribute/get/1.0#response";
+    readonly isBearer: false;
+    readonly isProofRequired: true;
+    readonly isRecipientRequired: true;
+    readonly isIssuedAtRequired: false;
+    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: "Persona Attribute — Get — response payload";
+                readonly description: "Success response to persona/attribute/get. Type https://trusttasks.org/spec/persona/attribute/get/1.0#response.";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["attribute"];
+                readonly properties: {
+                    readonly attribute: {
+                        readonly $ref: "#/$defs/Attribute";
+                        readonly description: "The attribute as at `version`, or as it stands when none was asked for. Its `value` is present only if the request asked for it and the attribute's sensitivity permitted it.";
+                    };
+                    readonly valueWithheld: {
+                        readonly type: "boolean";
+                        readonly description: "True when the value was withheld although `includeValue` asked for it — the attribute resolves to `sensitivity: high` and `includeSensitive` was not set. Stated rather than left to inference: a consumer that reads an absent `value` as \"this attribute has none\" will show the holder an empty field where a passport number is, and conclude the record is broken.";
+                    };
+                    readonly retainedVersions: {
+                        readonly type: "array";
+                        readonly maxItems: 64;
+                        readonly description: "The versions of this attribute the maintainer still holds, newest first, including the current one. Names versions and never their values.\n\nIt is here because a holder deciding whether to purge cannot see what purging would take away: which earlier versions exist, and therefore which pinned profile entries would stop presenting. A consumer that cannot enumerate them asks the holder to make an irreversible decision blind.";
+                        readonly items: {
+                            readonly $ref: "#/$defs/Version";
+                        };
+                    };
+                    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 Version: {
+                readonly title: "Version";
+                readonly description: "A value of the store's monotonic write counter. Server-assigned; a producer never chooses one.";
+                readonly type: "integer";
+                readonly minimum: 1;
+            };
+            readonly Attribute: {
+                readonly title: "Attribute";
+                readonly description: "One atomic fact a holder keeps about themselves. Several attributes MAY share a `type` — three phone numbers, a legal name and a preferred name — which is why `attributeId` is the identity of a fact and `type` is not. The pool is flat and unordered; ordering is a profile's concern.";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["attributeId", "type", "valueType", "provenance", "version", "updatedAt"];
+                readonly properties: {
+                    readonly attributeId: {
+                        readonly $ref: "#/$defs/Ulid";
+                    };
+                    readonly type: {
+                        readonly $ref: "#/$defs/ClaimType";
+                    };
+                    readonly valueType: {
+                        readonly $ref: "#/$defs/ValueType";
+                    };
+                    readonly value: {
+                        readonly description: "The fact itself, agreeing with `valueType`. Encrypted at rest by the maintainer.\n\nOPTIONAL, and its absence is meaningful in two distinct situations a consumer MUST NOT conflate: the caller asked for a metadata-only view (`list` without `includeValues`, which is the DEFAULT and the common case), or a credential-backed value could not be re-derived. `stale` tells them apart. Requiring this member would make the default listing unrepresentable — a maintainer would have to choose between disclosing every value in bulk and emitting a non-conformant response.";
+                    };
+                    readonly label: {
+                        readonly type: "string";
+                        readonly maxLength: 128;
+                        readonly description: "The holder's own words for this attribute, shown in a picker. Never disclosed to a verifier; it is a note to self.";
+                    };
+                    readonly provenance: {
+                        readonly $ref: "#/$defs/Provenance";
+                    };
+                    readonly stale: {
+                        readonly type: "boolean";
+                        readonly description: "Present and true when a `credentialBacked` value could not be re-derived. `staleReason` says why. A maintainer MUST refuse to disclose a stale attribute.";
+                    };
+                    readonly staleReason: {
+                        readonly type: "string";
+                        readonly enum: readonly ["revoked", "expired", "archived", "deleted", "notFound"];
+                        readonly description: "Why re-derivation failed. Present only alongside `stale`.";
+                    };
+                    readonly sensitivity: {
+                        readonly $ref: "#/$defs/Sensitivity";
+                        readonly description: "Set only where the holder decided it explicitly. Absent resolves from the claim-type registry — see CLAIM-TYPES.md §4, 'store the override, derive the default'.";
+                    };
+                    readonly release: {
+                        readonly $ref: "#/$defs/ReleaseRequirement";
+                        readonly description: "Set only where the holder decided it explicitly. Absent resolves from the claim-type registry.";
+                    };
+                    readonly endorsements: {
+                        readonly type: "array";
+                        readonly maxItems: 64;
+                        readonly uniqueItems: true;
+                        readonly items: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                        };
+                        readonly description: "Vault identifiers of credentials in which a third party endorses this value — a colleague vouching for a skill, an employer confirming a title. INVENTORY, not evidence: the value remains whatever its `provenance` says, and a vouched self-assertion is still self-asserted. Folding a vouch into `provenance` would make it render as attested, which is the one thing provenance exists to prevent. Not disclosed with the value; a holder who wants a counterparty to see an endorsement presents the credential itself. Absent when there are none.";
+                    };
+                    readonly version: {
+                        readonly $ref: "#/$defs/Version";
+                    };
+                    readonly retainedVersions: {
+                        readonly type: "array";
+                        readonly maxItems: 64;
+                        readonly description: "Earlier versions of this attribute the maintainer still holds, and why. A maintainer that keeps a replaced value to serve `pinVersion` MUST list it here: a holder who overwrote a value may reasonably believe it gone, and this is how they learn otherwise. Values are not included — the holder reads one through the profile that pins it, or removes it with persona/attribute/purge-version. Absent when none are held.";
+                        readonly items: {
+                            readonly type: "object";
+                            readonly additionalProperties: false;
+                            readonly required: readonly ["version", "pinnedBy"];
+                            readonly properties: {
+                                readonly version: {
+                                    readonly $ref: "#/$defs/Version";
+                                };
+                                readonly updatedAt: {
+                                    readonly type: "string";
+                                    readonly format: "date-time";
+                                    readonly description: "When this version was written.";
+                                };
+                                readonly pinnedBy: {
+                                    readonly type: "array";
+                                    readonly minItems: 1;
+                                    readonly maxItems: 256;
+                                    readonly items: {
+                                        readonly $ref: "#/$defs/Ulid";
+                                    };
+                                    readonly description: "The profiles pinning this version — the reason it is kept. A version no profile pins is not retained.";
+                                };
+                            };
+                        };
+                    };
+                    readonly createdAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                    };
+                    readonly updatedAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                    };
+                };
+            };
+            readonly Ulid: {
+                readonly title: "Ulid";
+                readonly description: "A ULID in Crockford base32, uppercase. Used for `attributeId` and `profileId`. Chosen over a UUID because the leading 48 bits are a timestamp, so a key-ordered scan of the store is also creation-ordered and a `list` needs no secondary sort. Server-assigned on create; a producer MAY supply one to make a create idempotent, and a maintainer MUST reject a supplied value that already exists rather than silently overwriting.";
+                readonly type: "string";
+                readonly pattern: "^[0-9A-HJKMNP-TV-Z]{26}$";
+            };
+            readonly ReleaseRequirement: {
+                readonly title: "ReleaseRequirement";
+                readonly description: "What it takes to let a value LEAVE. Distinct from `Sensitivity`, which governs showing it to the holder.\n\n`consent` is the ordinary gate: `persona/disclosure/preview` renders what would leave and `persona/disclosure/present` releases it, so a human sees it once.\n\n`stepUp` additionally requires a fresh authentication bound to THAT preview — not to the session. Without the binding, \"each time\" degrades into \"once per login\", which is the failure the requirement exists to prevent; the single-use `previewId` the preview already mints is what an implementation binds to. A maintainer MUST refuse `persona/disclosure/present` for a `stepUp` attribute when no such approval accompanies it.\n\nAbsent means *not decided by the holder* and resolves from the claim-type registry, which defaults `payment.*` and `gov.*` to `stepUp`.";
+                readonly type: "string";
+                readonly enum: readonly ["consent", "stepUp"];
+            };
+            readonly Sensitivity: {
+                readonly title: "Sensitivity";
+                readonly description: "How carefully a value is shown TO ITS OWN HOLDER. `high` means a consumer masks it by default, reveals it one attribute at a time on a deliberate act, and — the half that is not cosmetic — omits it from a listing that did not ask for sensitive values.\n\nAbsent means *not decided by the holder*, not `normal`: a consumer resolves it from the claim-type registry (see CLAIM-TYPES.md §4), which is why this member is optional and why an unregistered token resolves conservatively rather than permissively.\n\nDistinct from how linkable the value is. A payment card is highly sensitive and barely linkable — every card number is unique, so knowing one tells a second verifier nothing about the first. Reading either as a proxy for the other produces a consumer that hides the wrong things.";
+                readonly type: "string";
+                readonly enum: readonly ["normal", "high"];
+            };
+            readonly Provenance: {
+                readonly title: "Provenance";
+                readonly description: "Where a value comes from, and the member that makes this family worth building on a trust stack rather than in an address book. It survives to the verifier, so a recipient can tell — per field — what the holder typed from what an issuer attested.\n\n`selfAsserted` — the holder supplied it.\n\n`credentialBacked` — the value is derived from a credential in the vault at `claimPath`. The stored value is a CACHE FOR DISPLAY; the credential is the truth. A maintainer MUST re-derive it on read and MUST fail closed (never presenting a stale value) when the credential has been revoked, has expired, or has been archived or deleted.\n\n`generated` — the value is minted per verifier at disclosure time and recorded against that verifier, so every relying party receives a different one that routes back to the holder. This is the shape of the most widely adopted consumer privacy feature in this space; a maintainer need not operate a relay to conform, but the shape must exist, because retrofitting per-verifier values into a pool-of-values model is a migration rather than an addition.\n\n`derived` — the value was taken from a source the holder connected or supplied — a code-hosting profile, an uploaded CV — rather than typed by them or attested by an issuer. Nobody signed it: it is the holder's claim that the source said so, and a consumer MUST NOT present it as attested. It exists as its own kind because a derived value is neither of the others — the holder did not author it, and no one vouches for it — and a holder deciding whether to disclose deserves to know which of their values they typed.\n\nFor how strongly a disclosed value identifies the holder, the kinds rank `credentialBacked` above `derived` above `selfAsserted`; `generated` values are per-verifier and do not correlate.";
+                readonly type: "object";
+                readonly required: readonly ["kind"];
+                readonly oneOf: readonly [{
+                    readonly additionalProperties: false;
+                    readonly required: readonly ["kind"];
+                    readonly properties: {
+                        readonly kind: {
+                            readonly const: "selfAsserted";
+                        };
+                    };
+                }, {
+                    readonly additionalProperties: false;
+                    readonly required: readonly ["kind", "credentialId", "claimPath"];
+                    readonly properties: {
+                        readonly kind: {
+                            readonly const: "credentialBacked";
+                        };
+                        readonly credentialId: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                            readonly description: "Vault identifier of the backing credential.";
+                        };
+                        readonly claimPath: {
+                            readonly type: "string";
+                            readonly pattern: "^(/[^/~]*(~[01][^/~]*)*)*$";
+                            readonly description: "RFC 6901 JSON Pointer to the claim within the credential, e.g. `/credentialSubject/familyName`.";
+                        };
+                        readonly issuerDid: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                            readonly description: "Issuer of the backing credential. Advisory: a consumer MUST verify the credential rather than trusting this member.";
+                        };
+                        readonly proof: {
+                            readonly $ref: "#/$defs/ProofRung";
+                            readonly description: "The disclosure rung this claim was, or will be, presented at.";
+                        };
+                    };
+                }, {
+                    readonly additionalProperties: false;
+                    readonly required: readonly ["kind", "generator"];
+                    readonly properties: {
+                        readonly kind: {
+                            readonly const: "generated";
+                        };
+                        readonly generator: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                            readonly maxLength: 64;
+                            readonly description: "Names the minting scheme, e.g. `relayEmail`. Maintainer-defined.";
+                        };
+                        readonly perVerifier: {
+                            readonly type: "boolean";
+                            readonly default: true;
+                            readonly description: "When true (the default and the only useful setting), a distinct value is minted for each verifier.";
+                        };
+                    };
+                }, {
+                    readonly additionalProperties: false;
+                    readonly required: readonly ["kind", "source", "derivedAt"];
+                    readonly properties: {
+                        readonly kind: {
+                            readonly const: "derived";
+                        };
+                        readonly source: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                            readonly maxLength: 64;
+                            readonly pattern: "^[a-z][A-Za-z0-9.-]*$";
+                            readonly description: "The KIND of source the value was taken from — `github`, `cvUpload`, `linkedIn` — never an account, handle or URL. Provenance survives to the verifier, so this member is disclosed with the claim; a handle here would disclose an identifier the holder never chose to share.";
+                        };
+                        readonly derivedAt: {
+                            readonly type: "string";
+                            readonly format: "date-time";
+                            readonly description: "When the value was taken from the source. A derived value is a snapshot: the source may have changed since, and nothing re-derives it.";
+                        };
+                    };
+                }];
+            };
+            readonly ProofRung: {
+                readonly title: "ProofRung";
+                readonly description: "How strongly a credential-backed claim is hidden when presented, ordered most private first. `predicate` proves a statement over a claim without disclosing the claim. `derived` discloses exactly the claims needed via an unlinkable derived proof, so two presentations cannot be joined. `selectiveDisclosure` discloses exactly the claims needed but carries the issuer's signature unchanged, so two presentations ARE linkable. `whole` discloses the entire credential.\n\nThe distinction between the first two and the last two is of kind, not degree: only `predicate` and `derived` avoid handing two verifiers a join key. A maintainer MUST default to the highest rung the credential's format supports, and MUST NOT silently fall to a lower one — a request that cannot be satisfied at the rung a producer asked for is refused, because a silent privacy downgrade discloses material the holder believed was hidden.";
+                readonly type: "string";
+                readonly enum: readonly ["predicate", "derived", "selectiveDisclosure", "whole"];
+            };
+            readonly ValueType: {
+                readonly title: "ValueType";
+                readonly description: "The JSON shape of `value`, declared so that a consumer can render and compare without guessing. The maintainer validates that `value` agrees with this member and does nothing further: it does NOT validate a phone number against a phone-number grammar. That is a producer's affordance, and a store that grows opinions about the contents of its records eventually blocks its consumer's release.";
+                readonly type: "string";
+                readonly enum: readonly ["string", "number", "boolean", "date", "object"];
+            };
+            readonly ClaimType: {
+                readonly title: "ClaimType";
+                readonly description: "The vocabulary token naming what a value IS — `name.legal`, `phone.mobile`, `address.postal`, `person.birthDate`. Dotted, most-general segment first, so that a consumer with no knowledge of the specific token can still group by its prefix.\n\nThe token is the maintainer's own; no external vocabulary is primary. External vocabularies (vCard/jCard, OIDC standard claims, schema.org) are mappings applied at PRESENTATION by a renderer, not at rest, so that a query written in any of them can be matched without the store having to live inside any one of them.\n\nThe `x:` prefix is an open extension namespace and is not decoration. The closest prior art — Windows CardSpace's self-issued card — supported exactly fifteen predefined claim types with no extensibility, and that is the specific way it failed the requirement a holder actually has. An `x:` attribute stores, composes, binds and discloses exactly like a known one; it renders generically and matches only an explicit query.";
+                readonly type: "string";
+                readonly minLength: 1;
+                readonly maxLength: 128;
+                readonly pattern: "^(x:)?[a-z][a-zA-Z0-9]*(\\.[a-z][a-zA-Z0-9]*)*$";
+            };
+        };
+    };
+};
+//# sourceMappingURL=payload.d.ts.map