@openvtc/trust-tasks 0.16.8 → 0.16.10

package/src/persona/profile/get/1.0/payload.ts

@@ -0,0 +1,846 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/persona/profile/get/1.0/payload.schema.json
+ */
+
+import type { Attribute, ClaimType, Ext, Profile, ProfileEntry, ProofRung, Provenance, Ulid, ValueType, Version_PersonaV0_1 as Version } from "../../../../_shared/components.js";
+
+
+/**
+ * Read one profile, either as composed (the entries the holder wrote) or as resolved (the claims it would actually present).
+ */
+export interface PersonaProfileGetPayload {
+  profileId: Ulid;
+  /**
+   * When false (the default) the profile is returned as composed — entries as written, references unresolved. When true the maintainer resolves every entry against the pool and returns the claims the profile would present, which is what a preview renders and what a holder is really asking when they ask what a profile says. The default is the cheap, non-disclosing one.
+   */
+  resolve?: boolean;
+  ext?: Ext;
+}
+/**
+ * Success response to persona/profile/get. Type https://trusttasks.org/spec/persona/profile/get/1.0#response.
+ */
+export interface PersonaProfileGetResponsePayload {
+  profile: Profile;
+  /**
+   * Present only when `resolve` was true: the claims this profile would present, in entry order, with overrides applied and pinned versions honoured. A credential-backed claim whose backing could not be re-derived appears carrying `stale`, because a holder inspecting a profile needs to see that it has stopped being fully presentable.
+   *
+   * @maxItems 256
+   */
+  resolved?: Attribute[];
+  ext?: Ext;
+}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { Attribute, ClaimType, Ext, Profile, ProfileEntry, ProofRung, Provenance, Ulid, ValueType, Version };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/persona/profile/get/1.0" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = PersonaProfileGetPayload;
+
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/persona/profile/get/1.0#response" as const;
+
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = PersonaProfileGetResponsePayload;
+
+/**
+ * This specification's payload schema, as a value.
+ *
+ * SPEC.md §7.2 item 2 is performed against this. It is shipped as data
+ * rather than only as a `.json` file because TypeScript types are erased
+ * at runtime: without a schema a consumer has nothing to validate, and
+ * every REQUIRED payload member is optional in practice. Cross-file
+ * `$ref`s are already inlined, so it needs no resolver.
+ */
+export const PAYLOAD_SCHEMA = {
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://trusttasks.org/spec/persona/profile/get/1.0",
+  "title": "Persona Profile Get — payload",
+  "description": "Read one profile, either as composed (the entries the holder wrote) or as resolved (the claims it would actually present).",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "profileId"
+  ],
+  "properties": {
+    "profileId": {
+      "$ref": "#/$defs/Ulid"
+    },
+    "resolve": {
+      "type": "boolean",
+      "default": false,
+      "description": "When false (the default) the profile is returned as composed — entries as written, references unresolved. When true the maintainer resolves every entry against the pool and returns the claims the profile would present, which is what a preview renders and what a holder is really asking when they ask what a profile says. The default is the cheap, non-disclosing one."
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext"
+    }
+  },
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "Persona Profile Get — response payload",
+      "description": "Success response to persona/profile/get. Type https://trusttasks.org/spec/persona/profile/get/1.0#response.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "profile"
+      ],
+      "properties": {
+        "profile": {
+          "$ref": "#/$defs/Profile"
+        },
+        "resolved": {
+          "type": "array",
+          "maxItems": 256,
+          "items": {
+            "$ref": "#/$defs/Attribute"
+          },
+          "description": "Present only when `resolve` was true: the claims this profile would present, in entry order, with overrides applied and pinned versions honoured. A credential-backed claim whose backing could not be re-derived appears carrying `stale`, because a holder inspecting a profile needs to see that it has stopped being fully presentable."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext"
+        }
+      }
+    },
+    "Ext": {
+      "title": "Ext",
+      "description": "Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a reverse-DNS namespace; structure under each namespace is opaque to the framework.",
+      "type": "object",
+      "minProperties": 1,
+      "additionalProperties": true,
+      "propertyNames": {
+        "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
+      }
+    },
+    "Attribute": {
+      "title": "Attribute",
+      "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.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "attributeId",
+        "type",
+        "valueType",
+        "value",
+        "provenance",
+        "version",
+        "updatedAt"
+      ],
+      "properties": {
+        "attributeId": {
+          "$ref": "#/$defs/Ulid"
+        },
+        "type": {
+          "$ref": "#/$defs/ClaimType"
+        },
+        "valueType": {
+          "$ref": "#/$defs/ValueType"
+        },
+        "value": {
+          "description": "The fact itself, agreeing with `valueType`. Encrypted at rest by the maintainer. Absent when the caller asked for a metadata-only view, and absent when a credential-backed value could not be re-derived — a consumer MUST NOT conflate the two and MUST read `stale` to tell them apart."
+        },
+        "label": {
+          "type": "string",
+          "maxLength": 128,
+          "description": "The holder's own words for this attribute, shown in a picker. Never disclosed to a verifier; it is a note to self."
+        },
+        "provenance": {
+          "$ref": "#/$defs/Provenance"
+        },
+        "stale": {
+          "type": "boolean",
+          "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."
+        },
+        "staleReason": {
+          "type": "string",
+          "enum": [
+            "revoked",
+            "expired",
+            "archived",
+            "deleted",
+            "notFound"
+          ],
+          "description": "Why re-derivation failed. Present only alongside `stale`."
+        },
+        "version": {
+          "$ref": "#/$defs/Version"
+        },
+        "createdAt": {
+          "type": "string",
+          "format": "date-time"
+        },
+        "updatedAt": {
+          "type": "string",
+          "format": "date-time"
+        }
+      }
+    },
+    "Version": {
+      "title": "Version",
+      "description": "A value of the store's monotonic write counter. Server-assigned; a producer never chooses one.",
+      "type": "integer",
+      "minimum": 1
+    },
+    "Provenance": {
+      "title": "Provenance",
+      "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.",
+      "type": "object",
+      "required": [
+        "kind"
+      ],
+      "oneOf": [
+        {
+          "additionalProperties": false,
+          "required": [
+            "kind"
+          ],
+          "properties": {
+            "kind": {
+              "const": "selfAsserted"
+            }
+          }
+        },
+        {
+          "additionalProperties": false,
+          "required": [
+            "kind",
+            "credentialId",
+            "claimPath"
+          ],
+          "properties": {
+            "kind": {
+              "const": "credentialBacked"
+            },
+            "credentialId": {
+              "type": "string",
+              "minLength": 1,
+              "description": "Vault identifier of the backing credential."
+            },
+            "claimPath": {
+              "type": "string",
+              "pattern": "^(/[^/~]*(~[01][^/~]*)*)*$",
+              "description": "RFC 6901 JSON Pointer to the claim within the credential, e.g. `/credentialSubject/familyName`."
+            },
+            "issuerDid": {
+              "type": "string",
+              "minLength": 1,
+              "description": "Issuer of the backing credential. Advisory: a consumer MUST verify the credential rather than trusting this member."
+            },
+            "proof": {
+              "$ref": "#/$defs/ProofRung",
+              "description": "The disclosure rung this claim was, or will be, presented at."
+            }
+          }
+        },
+        {
+          "additionalProperties": false,
+          "required": [
+            "kind",
+            "generator"
+          ],
+          "properties": {
+            "kind": {
+              "const": "generated"
+            },
+            "generator": {
+              "type": "string",
+              "minLength": 1,
+              "maxLength": 64,
+              "description": "Names the minting scheme, e.g. `relayEmail`. Maintainer-defined."
+            },
+            "perVerifier": {
+              "type": "boolean",
+              "default": true,
+              "description": "When true (the default and the only useful setting), a distinct value is minted for each verifier."
+            }
+          }
+        }
+      ]
+    },
+    "ProofRung": {
+      "title": "ProofRung",
+      "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.",
+      "type": "string",
+      "enum": [
+        "predicate",
+        "derived",
+        "selectiveDisclosure",
+        "whole"
+      ]
+    },
+    "ValueType": {
+      "title": "ValueType",
+      "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.",
+      "type": "string",
+      "enum": [
+        "string",
+        "number",
+        "boolean",
+        "date",
+        "object"
+      ]
+    },
+    "ClaimType": {
+      "title": "ClaimType",
+      "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.",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 128,
+      "pattern": "^(x:)?[a-z][a-zA-Z0-9]*(\\.[a-z][a-zA-Z0-9]*)*$"
+    },
+    "Ulid": {
+      "title": "Ulid",
+      "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.",
+      "type": "string",
+      "pattern": "^[0-9A-HJKMNP-TV-Z]{26}$"
+    },
+    "Profile": {
+      "title": "Profile",
+      "description": "A named projection over the pool. Agent-scoped, like the pool it draws from. `entries` is ordered and the order is display order.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "profileId",
+        "name",
+        "entries",
+        "version",
+        "updatedAt"
+      ],
+      "properties": {
+        "profileId": {
+          "$ref": "#/$defs/Ulid"
+        },
+        "name": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 128,
+          "description": "The holder's name for this profile — \"Work\", \"Gaming\". Not disclosed."
+        },
+        "entries": {
+          "type": "array",
+          "maxItems": 256,
+          "items": {
+            "$ref": "#/$defs/ProfileEntry"
+          }
+        },
+        "credentialRefs": {
+          "type": "array",
+          "maxItems": 256,
+          "items": {
+            "type": "string",
+            "minLength": 1
+          },
+          "description": "Vault identifiers of credentials associated with this profile as INVENTORY, distinct from the evidence relationship a `credentialBacked` attribute expresses. The two answer different questions — what can this persona prove, versus what backs this specific claim — and a consumer MUST NOT read one as the other."
+        },
+        "version": {
+          "$ref": "#/$defs/Version"
+        },
+        "createdAt": {
+          "type": "string",
+          "format": "date-time"
+        },
+        "updatedAt": {
+          "type": "string",
+          "format": "date-time"
+        }
+      }
+    },
+    "ProfileEntry": {
+      "title": "ProfileEntry",
+      "description": "One line of a profile, in exactly one of four forms. Together they are the whole of a profile's flexibility, and each exists for a case the others handle badly.\n\n`{ref}` — use the pool attribute, live. Editing the pool updates every profile that references it, which is the point.\n\n`{ref, pinVersion}` — use the value as it was at that version. For a profile that must keep presenting the value a counterparty already verified.\n\n`{ref, override}` — the same fact, a different value here. (\"In the gaming profile my display name is different.\")\n\n`{inline}` — a value that never enters the pool, and so never leaks into another profile.\n\nOmission is exclusion; there is no removal marker.",
+      "type": "object",
+      "oneOf": [
+        {
+          "additionalProperties": false,
+          "required": [
+            "ref"
+          ],
+          "properties": {
+            "ref": {
+              "$ref": "#/$defs/Ulid"
+            }
+          }
+        },
+        {
+          "additionalProperties": false,
+          "required": [
+            "ref",
+            "pinVersion"
+          ],
+          "properties": {
+            "ref": {
+              "$ref": "#/$defs/Ulid"
+            },
+            "pinVersion": {
+              "$ref": "#/$defs/Version"
+            }
+          }
+        },
+        {
+          "additionalProperties": false,
+          "required": [
+            "ref",
+            "override"
+          ],
+          "properties": {
+            "ref": {
+              "$ref": "#/$defs/Ulid"
+            },
+            "override": {
+              "type": "object",
+              "additionalProperties": false,
+              "required": [
+                "value"
+              ],
+              "properties": {
+                "value": {},
+                "label": {
+                  "type": "string",
+                  "maxLength": 128
+                }
+              },
+              "description": "Replaces the pool attribute's value for this profile only. `type`, `valueType` and `provenance` are inherited from the referenced attribute and MUST NOT be overridden — an override that changed provenance would let a self-asserted value present as attested."
+            }
+          }
+        },
+        {
+          "additionalProperties": false,
+          "required": [
+            "inline"
+          ],
+          "properties": {
+            "inline": {
+              "type": "object",
+              "additionalProperties": false,
+              "required": [
+                "type",
+                "valueType",
+                "value",
+                "provenance"
+              ],
+              "properties": {
+                "type": {
+                  "$ref": "#/$defs/ClaimType"
+                },
+                "valueType": {
+                  "$ref": "#/$defs/ValueType"
+                },
+                "value": {},
+                "label": {
+                  "type": "string",
+                  "maxLength": 128
+                },
+                "provenance": {
+                  "$ref": "#/$defs/Provenance"
+                }
+              }
+            }
+          }
+        }
+      ]
+    }
+  }
+} as const;
+
+/** As {@link PAYLOAD_SCHEMA}, for the success-response variant. */
+export const RESPONSE_PAYLOAD_SCHEMA = {
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$ref": "#/$defs/Response",
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "Persona Profile Get — response payload",
+      "description": "Success response to persona/profile/get. Type https://trusttasks.org/spec/persona/profile/get/1.0#response.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "profile"
+      ],
+      "properties": {
+        "profile": {
+          "$ref": "#/$defs/Profile"
+        },
+        "resolved": {
+          "type": "array",
+          "maxItems": 256,
+          "items": {
+            "$ref": "#/$defs/Attribute"
+          },
+          "description": "Present only when `resolve` was true: the claims this profile would present, in entry order, with overrides applied and pinned versions honoured. A credential-backed claim whose backing could not be re-derived appears carrying `stale`, because a holder inspecting a profile needs to see that it has stopped being fully presentable."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext"
+        }
+      }
+    },
+    "Ext": {
+      "title": "Ext",
+      "description": "Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a reverse-DNS namespace; structure under each namespace is opaque to the framework.",
+      "type": "object",
+      "minProperties": 1,
+      "additionalProperties": true,
+      "propertyNames": {
+        "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
+      }
+    },
+    "Attribute": {
+      "title": "Attribute",
+      "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.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "attributeId",
+        "type",
+        "valueType",
+        "value",
+        "provenance",
+        "version",
+        "updatedAt"
+      ],
+      "properties": {
+        "attributeId": {
+          "$ref": "#/$defs/Ulid"
+        },
+        "type": {
+          "$ref": "#/$defs/ClaimType"
+        },
+        "valueType": {
+          "$ref": "#/$defs/ValueType"
+        },
+        "value": {
+          "description": "The fact itself, agreeing with `valueType`. Encrypted at rest by the maintainer. Absent when the caller asked for a metadata-only view, and absent when a credential-backed value could not be re-derived — a consumer MUST NOT conflate the two and MUST read `stale` to tell them apart."
+        },
+        "label": {
+          "type": "string",
+          "maxLength": 128,
+          "description": "The holder's own words for this attribute, shown in a picker. Never disclosed to a verifier; it is a note to self."
+        },
+        "provenance": {
+          "$ref": "#/$defs/Provenance"
+        },
+        "stale": {
+          "type": "boolean",
+          "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."
+        },
+        "staleReason": {
+          "type": "string",
+          "enum": [
+            "revoked",
+            "expired",
+            "archived",
+            "deleted",
+            "notFound"
+          ],
+          "description": "Why re-derivation failed. Present only alongside `stale`."
+        },
+        "version": {
+          "$ref": "#/$defs/Version"
+        },
+        "createdAt": {
+          "type": "string",
+          "format": "date-time"
+        },
+        "updatedAt": {
+          "type": "string",
+          "format": "date-time"
+        }
+      }
+    },
+    "Version": {
+      "title": "Version",
+      "description": "A value of the store's monotonic write counter. Server-assigned; a producer never chooses one.",
+      "type": "integer",
+      "minimum": 1
+    },
+    "Provenance": {
+      "title": "Provenance",
+      "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.",
+      "type": "object",
+      "required": [
+        "kind"
+      ],
+      "oneOf": [
+        {
+          "additionalProperties": false,
+          "required": [
+            "kind"
+          ],
+          "properties": {
+            "kind": {
+              "const": "selfAsserted"
+            }
+          }
+        },
+        {
+          "additionalProperties": false,
+          "required": [
+            "kind",
+            "credentialId",
+            "claimPath"
+          ],
+          "properties": {
+            "kind": {
+              "const": "credentialBacked"
+            },
+            "credentialId": {
+              "type": "string",
+              "minLength": 1,
+              "description": "Vault identifier of the backing credential."
+            },
+            "claimPath": {
+              "type": "string",
+              "pattern": "^(/[^/~]*(~[01][^/~]*)*)*$",
+              "description": "RFC 6901 JSON Pointer to the claim within the credential, e.g. `/credentialSubject/familyName`."
+            },
+            "issuerDid": {
+              "type": "string",
+              "minLength": 1,
+              "description": "Issuer of the backing credential. Advisory: a consumer MUST verify the credential rather than trusting this member."
+            },
+            "proof": {
+              "$ref": "#/$defs/ProofRung",
+              "description": "The disclosure rung this claim was, or will be, presented at."
+            }
+          }
+        },
+        {
+          "additionalProperties": false,
+          "required": [
+            "kind",
+            "generator"
+          ],
+          "properties": {
+            "kind": {
+              "const": "generated"
+            },
+            "generator": {
+              "type": "string",
+              "minLength": 1,
+              "maxLength": 64,
+              "description": "Names the minting scheme, e.g. `relayEmail`. Maintainer-defined."
+            },
+            "perVerifier": {
+              "type": "boolean",
+              "default": true,
+              "description": "When true (the default and the only useful setting), a distinct value is minted for each verifier."
+            }
+          }
+        }
+      ]
+    },
+    "ProofRung": {
+      "title": "ProofRung",
+      "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.",
+      "type": "string",
+      "enum": [
+        "predicate",
+        "derived",
+        "selectiveDisclosure",
+        "whole"
+      ]
+    },
+    "ValueType": {
+      "title": "ValueType",
+      "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.",
+      "type": "string",
+      "enum": [
+        "string",
+        "number",
+        "boolean",
+        "date",
+        "object"
+      ]
+    },
+    "ClaimType": {
+      "title": "ClaimType",
+      "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.",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 128,
+      "pattern": "^(x:)?[a-z][a-zA-Z0-9]*(\\.[a-z][a-zA-Z0-9]*)*$"
+    },
+    "Ulid": {
+      "title": "Ulid",
+      "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.",
+      "type": "string",
+      "pattern": "^[0-9A-HJKMNP-TV-Z]{26}$"
+    },
+    "Profile": {
+      "title": "Profile",
+      "description": "A named projection over the pool. Agent-scoped, like the pool it draws from. `entries` is ordered and the order is display order.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "profileId",
+        "name",
+        "entries",
+        "version",
+        "updatedAt"
+      ],
+      "properties": {
+        "profileId": {
+          "$ref": "#/$defs/Ulid"
+        },
+        "name": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 128,
+          "description": "The holder's name for this profile — \"Work\", \"Gaming\". Not disclosed."
+        },
+        "entries": {
+          "type": "array",
+          "maxItems": 256,
+          "items": {
+            "$ref": "#/$defs/ProfileEntry"
+          }
+        },
+        "credentialRefs": {
+          "type": "array",
+          "maxItems": 256,
+          "items": {
+            "type": "string",
+            "minLength": 1
+          },
+          "description": "Vault identifiers of credentials associated with this profile as INVENTORY, distinct from the evidence relationship a `credentialBacked` attribute expresses. The two answer different questions — what can this persona prove, versus what backs this specific claim — and a consumer MUST NOT read one as the other."
+        },
+        "version": {
+          "$ref": "#/$defs/Version"
+        },
+        "createdAt": {
+          "type": "string",
+          "format": "date-time"
+        },
+        "updatedAt": {
+          "type": "string",
+          "format": "date-time"
+        }
+      }
+    },
+    "ProfileEntry": {
+      "title": "ProfileEntry",
+      "description": "One line of a profile, in exactly one of four forms. Together they are the whole of a profile's flexibility, and each exists for a case the others handle badly.\n\n`{ref}` — use the pool attribute, live. Editing the pool updates every profile that references it, which is the point.\n\n`{ref, pinVersion}` — use the value as it was at that version. For a profile that must keep presenting the value a counterparty already verified.\n\n`{ref, override}` — the same fact, a different value here. (\"In the gaming profile my display name is different.\")\n\n`{inline}` — a value that never enters the pool, and so never leaks into another profile.\n\nOmission is exclusion; there is no removal marker.",
+      "type": "object",
+      "oneOf": [
+        {
+          "additionalProperties": false,
+          "required": [
+            "ref"
+          ],
+          "properties": {
+            "ref": {
+              "$ref": "#/$defs/Ulid"
+            }
+          }
+        },
+        {
+          "additionalProperties": false,
+          "required": [
+            "ref",
+            "pinVersion"
+          ],
+          "properties": {
+            "ref": {
+              "$ref": "#/$defs/Ulid"
+            },
+            "pinVersion": {
+              "$ref": "#/$defs/Version"
+            }
+          }
+        },
+        {
+          "additionalProperties": false,
+          "required": [
+            "ref",
+            "override"
+          ],
+          "properties": {
+            "ref": {
+              "$ref": "#/$defs/Ulid"
+            },
+            "override": {
+              "type": "object",
+              "additionalProperties": false,
+              "required": [
+                "value"
+              ],
+              "properties": {
+                "value": {},
+                "label": {
+                  "type": "string",
+                  "maxLength": 128
+                }
+              },
+              "description": "Replaces the pool attribute's value for this profile only. `type`, `valueType` and `provenance` are inherited from the referenced attribute and MUST NOT be overridden — an override that changed provenance would let a self-asserted value present as attested."
+            }
+          }
+        },
+        {
+          "additionalProperties": false,
+          "required": [
+            "inline"
+          ],
+          "properties": {
+            "inline": {
+              "type": "object",
+              "additionalProperties": false,
+              "required": [
+                "type",
+                "valueType",
+                "value",
+                "provenance"
+              ],
+              "properties": {
+                "type": {
+                  "$ref": "#/$defs/ClaimType"
+                },
+                "valueType": {
+                  "$ref": "#/$defs/ValueType"
+                },
+                "value": {},
+                "label": {
+                  "type": "string",
+                  "maxLength": 128
+                },
+                "provenance": {
+                  "$ref": "#/$defs/Provenance"
+                }
+              }
+            }
+          }
+        }
+      ]
+    }
+  }
+} as const;
+
+/**
+ * SPEC.md §7.2 policy for the request variant, from this specification's
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
+ * per-specification and cannot be derived from the document alone, and
+ * item 2 needs the schema this carries.
+ */
+export const SPEC = {
+  typeUri: TYPE_URI,
+  isBearer: false,
+  isProofRequired: true,
+  isRecipientRequired: true,
+  isIssuedAtRequired: false,
+  payloadSchema: PAYLOAD_SCHEMA,
+} as const;
+
+/**
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
+ * tracks the *issuer* party's requirement because a response swaps the
+ * parties (§7.3 item 5).
+ */
+export const RESPONSE_SPEC = {
+  typeUri: RESPONSE_TYPE_URI,
+  isBearer: false,
+  isProofRequired: true,
+  isRecipientRequired: true,
+  isIssuedAtRequired: false,
+  payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
+} as const;