@openvtc/trust-tasks 0.16.9 → 0.16.11

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (166) hide show
  1. package/CHANGELOG.md +220 -0
  2. package/dist/_shared/components.d.ts +206 -5
  3. package/dist/_shared/components.d.ts.map +1 -1
  4. package/dist/index.d.ts +27 -0
  5. package/dist/index.d.ts.map +1 -1
  6. package/dist/index.js +27 -0
  7. package/dist/index.js.map +1 -1
  8. package/dist/persona/_shared/0.1/persona-record.d.ts +22 -0
  9. package/dist/persona/_shared/0.1/persona-record.d.ts.map +1 -0
  10. package/dist/persona/_shared/0.1/persona-record.js +6 -0
  11. package/dist/persona/_shared/0.1/persona-record.js.map +1 -0
  12. package/dist/persona/attribute/delete/1.0/payload.d.ts +351 -0
  13. package/dist/persona/attribute/delete/1.0/payload.d.ts.map +1 -0
  14. package/dist/persona/attribute/delete/1.0/payload.js +188 -0
  15. package/dist/persona/attribute/delete/1.0/payload.js.map +1 -0
  16. package/dist/persona/attribute/list/1.0/payload.d.ts +895 -0
  17. package/dist/persona/attribute/list/1.0/payload.d.ts.map +1 -0
  18. package/dist/persona/attribute/list/1.0/payload.js +530 -0
  19. package/dist/persona/attribute/list/1.0/payload.js.map +1 -0
  20. package/dist/persona/attribute/put/1.0/payload.d.ts +829 -0
  21. package/dist/persona/attribute/put/1.0/payload.d.ts.map +1 -0
  22. package/dist/persona/attribute/put/1.0/payload.js +487 -0
  23. package/dist/persona/attribute/put/1.0/payload.js.map +1 -0
  24. package/dist/persona/binding/get/1.0/payload.d.ts +382 -0
  25. package/dist/persona/binding/get/1.0/payload.d.ts.map +1 -0
  26. package/dist/persona/binding/get/1.0/payload.js +206 -0
  27. package/dist/persona/binding/get/1.0/payload.js.map +1 -0
  28. package/dist/persona/binding/list/1.0/payload.d.ts +387 -0
  29. package/dist/persona/binding/list/1.0/payload.d.ts.map +1 -0
  30. package/dist/persona/binding/list/1.0/payload.js +210 -0
  31. package/dist/persona/binding/list/1.0/payload.js.map +1 -0
  32. package/dist/persona/binding/set/1.0/payload.d.ts +545 -0
  33. package/dist/persona/binding/set/1.0/payload.d.ts.map +1 -0
  34. package/dist/persona/binding/set/1.0/payload.js +302 -0
  35. package/dist/persona/binding/set/1.0/payload.js.map +1 -0
  36. package/dist/persona/contact/delete/1.0/payload.d.ts +313 -0
  37. package/dist/persona/contact/delete/1.0/payload.d.ts.map +1 -0
  38. package/dist/persona/contact/delete/1.0/payload.js +174 -0
  39. package/dist/persona/contact/delete/1.0/payload.js.map +1 -0
  40. package/dist/persona/contact/get/1.0/payload.d.ts +1027 -0
  41. package/dist/persona/contact/get/1.0/payload.d.ts.map +1 -0
  42. package/dist/persona/contact/get/1.0/payload.js +606 -0
  43. package/dist/persona/contact/get/1.0/payload.js.map +1 -0
  44. package/dist/persona/contact/list/1.0/payload.d.ts +490 -0
  45. package/dist/persona/contact/list/1.0/payload.d.ts.map +1 -0
  46. package/dist/persona/contact/list/1.0/payload.js +262 -0
  47. package/dist/persona/contact/list/1.0/payload.js.map +1 -0
  48. package/dist/persona/contact/put/1.0/payload.d.ts +885 -0
  49. package/dist/persona/contact/put/1.0/payload.d.ts.map +1 -0
  50. package/dist/persona/contact/put/1.0/payload.js +518 -0
  51. package/dist/persona/contact/put/1.0/payload.js.map +1 -0
  52. package/dist/persona/correlation/analyze/1.0/payload.d.ts +648 -0
  53. package/dist/persona/correlation/analyze/1.0/payload.d.ts.map +1 -0
  54. package/dist/persona/correlation/analyze/1.0/payload.js +338 -0
  55. package/dist/persona/correlation/analyze/1.0/payload.js.map +1 -0
  56. package/dist/persona/disclosure/history/1.0/payload.d.ts +639 -0
  57. package/dist/persona/disclosure/history/1.0/payload.d.ts.map +1 -0
  58. package/dist/persona/disclosure/history/1.0/payload.js +339 -0
  59. package/dist/persona/disclosure/history/1.0/payload.js.map +1 -0
  60. package/dist/persona/disclosure/present/1.0/payload.d.ts +400 -0
  61. package/dist/persona/disclosure/present/1.0/payload.d.ts.map +1 -0
  62. package/dist/persona/disclosure/present/1.0/payload.js +211 -0
  63. package/dist/persona/disclosure/present/1.0/payload.js.map +1 -0
  64. package/dist/persona/disclosure/preview/1.0/payload.d.ts +858 -0
  65. package/dist/persona/disclosure/preview/1.0/payload.d.ts.map +1 -0
  66. package/dist/persona/disclosure/preview/1.0/payload.js +480 -0
  67. package/dist/persona/disclosure/preview/1.0/payload.js.map +1 -0
  68. package/dist/persona/local/binding/set/1.0/payload.d.ts +394 -0
  69. package/dist/persona/local/binding/set/1.0/payload.d.ts.map +1 -0
  70. package/dist/persona/local/binding/set/1.0/payload.js +226 -0
  71. package/dist/persona/local/binding/set/1.0/payload.js.map +1 -0
  72. package/dist/persona/local/profile/delete/1.0/payload.d.ts +311 -0
  73. package/dist/persona/local/profile/delete/1.0/payload.d.ts.map +1 -0
  74. package/dist/persona/local/profile/delete/1.0/payload.js +173 -0
  75. package/dist/persona/local/profile/delete/1.0/payload.js.map +1 -0
  76. package/dist/persona/local/profile/get/1.0/payload.d.ts +368 -0
  77. package/dist/persona/local/profile/get/1.0/payload.d.ts.map +1 -0
  78. package/dist/persona/local/profile/get/1.0/payload.js +210 -0
  79. package/dist/persona/local/profile/get/1.0/payload.js.map +1 -0
  80. package/dist/persona/local/profile/list/1.0/payload.d.ts +387 -0
  81. package/dist/persona/local/profile/list/1.0/payload.d.ts.map +1 -0
  82. package/dist/persona/local/profile/list/1.0/payload.js +214 -0
  83. package/dist/persona/local/profile/list/1.0/payload.js.map +1 -0
  84. package/dist/persona/local/profile/put/1.0/payload.d.ts +545 -0
  85. package/dist/persona/local/profile/put/1.0/payload.d.ts.map +1 -0
  86. package/dist/persona/local/profile/put/1.0/payload.js +315 -0
  87. package/dist/persona/local/profile/put/1.0/payload.js.map +1 -0
  88. package/dist/persona/profile/delete/1.0/payload.d.ts +350 -0
  89. package/dist/persona/profile/delete/1.0/payload.d.ts.map +1 -0
  90. package/dist/persona/profile/delete/1.0/payload.js +189 -0
  91. package/dist/persona/profile/delete/1.0/payload.js.map +1 -0
  92. package/dist/persona/profile/get/1.0/payload.d.ts +1307 -0
  93. package/dist/persona/profile/get/1.0/payload.d.ts.map +1 -0
  94. package/dist/persona/profile/get/1.0/payload.js +802 -0
  95. package/dist/persona/profile/get/1.0/payload.js.map +1 -0
  96. package/dist/persona/profile/list/1.0/payload.d.ts +1120 -0
  97. package/dist/persona/profile/list/1.0/payload.d.ts.map +1 -0
  98. package/dist/persona/profile/list/1.0/payload.js +680 -0
  99. package/dist/persona/profile/list/1.0/payload.js.map +1 -0
  100. package/dist/persona/profile/put/1.0/payload.d.ts +1115 -0
  101. package/dist/persona/profile/put/1.0/payload.d.ts.map +1 -0
  102. package/dist/persona/profile/put/1.0/payload.js +675 -0
  103. package/dist/persona/profile/put/1.0/payload.js.map +1 -0
  104. package/dist/persona/renderers/list/1.0/payload.d.ts +362 -0
  105. package/dist/persona/renderers/list/1.0/payload.d.ts.map +1 -0
  106. package/dist/persona/renderers/list/1.0/payload.js +197 -0
  107. package/dist/persona/renderers/list/1.0/payload.js.map +1 -0
  108. package/dist/rooms/owner/claim/0.1/payload.d.ts +391 -0
  109. package/dist/rooms/owner/claim/0.1/payload.d.ts.map +1 -0
  110. package/dist/rooms/owner/claim/0.1/payload.js +214 -0
  111. package/dist/rooms/owner/claim/0.1/payload.js.map +1 -0
  112. package/dist/rooms/owner/transfer/0.1/payload.d.ts +391 -0
  113. package/dist/rooms/owner/transfer/0.1/payload.d.ts.map +1 -0
  114. package/dist/rooms/owner/transfer/0.1/payload.js +214 -0
  115. package/dist/rooms/owner/transfer/0.1/payload.js.map +1 -0
  116. package/dist/vta/_shared/0.1/app-state-record.d.ts +1 -1
  117. package/dist/vta/_shared/0.1/app-state-record.d.ts.map +1 -1
  118. package/dist/vta/app-state/delete/1.0/payload.d.ts +1 -1
  119. package/dist/vta/app-state/delete/1.0/payload.d.ts.map +1 -1
  120. package/dist/vta/app-state/get/1.0/payload.d.ts +1 -1
  121. package/dist/vta/app-state/get/1.0/payload.d.ts.map +1 -1
  122. package/dist/vta/app-state/get-many/1.0/payload.d.ts +1 -1
  123. package/dist/vta/app-state/get-many/1.0/payload.d.ts.map +1 -1
  124. package/dist/vta/app-state/list/1.0/payload.d.ts +1 -1
  125. package/dist/vta/app-state/list/1.0/payload.d.ts.map +1 -1
  126. package/dist/vta/app-state/put/1.0/payload.d.ts +1 -1
  127. package/dist/vta/app-state/put/1.0/payload.d.ts.map +1 -1
  128. package/dist/vta/app-state/put-many/1.0/payload.d.ts +1 -1
  129. package/dist/vta/app-state/put-many/1.0/payload.d.ts.map +1 -1
  130. package/package.json +1 -1
  131. package/src/_shared/components.ts +213 -5
  132. package/src/index.ts +27 -0
  133. package/src/persona/_shared/0.1/persona-record.ts +23 -0
  134. package/src/persona/attribute/delete/1.0/payload.ts +238 -0
  135. package/src/persona/attribute/list/1.0/payload.ts +588 -0
  136. package/src/persona/attribute/put/1.0/payload.ts +559 -0
  137. package/src/persona/binding/get/1.0/payload.ts +257 -0
  138. package/src/persona/binding/list/1.0/payload.ts +260 -0
  139. package/src/persona/binding/set/1.0/payload.ts +370 -0
  140. package/src/persona/contact/delete/1.0/payload.ts +216 -0
  141. package/src/persona/contact/get/1.0/payload.ts +662 -0
  142. package/src/persona/contact/list/1.0/payload.ts +323 -0
  143. package/src/persona/contact/put/1.0/payload.ts +580 -0
  144. package/src/persona/correlation/analyze/1.0/payload.ts +466 -0
  145. package/src/persona/disclosure/history/1.0/payload.ts +415 -0
  146. package/src/persona/disclosure/present/1.0/payload.ts +274 -0
  147. package/src/persona/disclosure/preview/1.0/payload.ts +597 -0
  148. package/src/persona/local/binding/set/1.0/payload.ts +267 -0
  149. package/src/persona/local/profile/delete/1.0/payload.ts +215 -0
  150. package/src/persona/local/profile/get/1.0/payload.ts +251 -0
  151. package/src/persona/local/profile/list/1.0/payload.ts +260 -0
  152. package/src/persona/local/profile/put/1.0/payload.ts +373 -0
  153. package/src/persona/profile/delete/1.0/payload.ts +236 -0
  154. package/src/persona/profile/get/1.0/payload.ts +844 -0
  155. package/src/persona/profile/list/1.0/payload.ts +723 -0
  156. package/src/persona/profile/put/1.0/payload.ts +741 -0
  157. package/src/persona/renderers/list/1.0/payload.ts +248 -0
  158. package/src/rooms/owner/claim/0.1/payload.ts +268 -0
  159. package/src/rooms/owner/transfer/0.1/payload.ts +268 -0
  160. package/src/vta/_shared/0.1/app-state-record.ts +1 -1
  161. package/src/vta/app-state/delete/1.0/payload.ts +1 -1
  162. package/src/vta/app-state/get/1.0/payload.ts +1 -1
  163. package/src/vta/app-state/get-many/1.0/payload.ts +1 -1
  164. package/src/vta/app-state/list/1.0/payload.ts +1 -1
  165. package/src/vta/app-state/put/1.0/payload.ts +1 -1
  166. package/src/vta/app-state/put-many/1.0/payload.ts +1 -1
@@ -0,0 +1,1307 @@
1
+ /**
2
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
3
+ * Source: specs/persona/profile/get/1.0/payload.schema.json
4
+ */
5
+ import type { Attribute, ClaimType, Ext, Profile, ProfileEntry, ProofRung, Provenance, Ulid, ValueType, Version_PersonaV0_1 as Version } from "../../../../_shared/components.js";
6
+ /**
7
+ * Read one profile, either as composed (the entries the holder wrote) or as resolved (the claims it would actually present).
8
+ */
9
+ export interface PersonaProfileGetPayload {
10
+ profileId: Ulid;
11
+ /**
12
+ * 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.
13
+ */
14
+ resolve?: boolean;
15
+ ext?: Ext;
16
+ }
17
+ /**
18
+ * Success response to persona/profile/get. Type https://trusttasks.org/spec/persona/profile/get/1.0#response.
19
+ */
20
+ export interface PersonaProfileGetResponsePayload {
21
+ profile: Profile;
22
+ /**
23
+ * 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.
24
+ *
25
+ * @maxItems 256
26
+ */
27
+ resolved?: Attribute[];
28
+ ext?: Ext;
29
+ }
30
+ /** Shared definitions this specification references, re-exported under the names it used to declare them with. */
31
+ export type { Attribute, ClaimType, Ext, Profile, ProfileEntry, ProofRung, Provenance, Ulid, ValueType, Version };
32
+ /** Trust Task type URI. */
33
+ export declare const TYPE_URI: "https://trusttasks.org/spec/persona/profile/get/1.0";
34
+ /** Stable alias for this specification's request payload shape. */
35
+ export type Payload = PersonaProfileGetPayload;
36
+ /** Trust Task response type URI (request type URI + "#response"). */
37
+ export declare const RESPONSE_TYPE_URI: "https://trusttasks.org/spec/persona/profile/get/1.0#response";
38
+ /** Stable alias for this specification's success-response payload shape. */
39
+ export type Response = PersonaProfileGetResponsePayload;
40
+ /**
41
+ * This specification's payload schema, as a value.
42
+ *
43
+ * SPEC.md §7.2 item 2 is performed against this. It is shipped as data
44
+ * rather than only as a `.json` file because TypeScript types are erased
45
+ * at runtime: without a schema a consumer has nothing to validate, and
46
+ * every REQUIRED payload member is optional in practice. Cross-file
47
+ * `$ref`s are already inlined, so it needs no resolver.
48
+ */
49
+ export declare const PAYLOAD_SCHEMA: {
50
+ readonly $schema: "https://json-schema.org/draft/2020-12/schema";
51
+ readonly $id: "https://trusttasks.org/spec/persona/profile/get/1.0";
52
+ readonly title: "Persona Profile Get — payload";
53
+ readonly description: "Read one profile, either as composed (the entries the holder wrote) or as resolved (the claims it would actually present).";
54
+ readonly type: "object";
55
+ readonly additionalProperties: false;
56
+ readonly required: readonly ["profileId"];
57
+ readonly properties: {
58
+ readonly profileId: {
59
+ readonly $ref: "#/$defs/Ulid";
60
+ };
61
+ readonly resolve: {
62
+ readonly type: "boolean";
63
+ readonly default: false;
64
+ readonly 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.";
65
+ };
66
+ readonly ext: {
67
+ readonly $ref: "#/$defs/Ext";
68
+ };
69
+ };
70
+ readonly $defs: {
71
+ readonly Response: {
72
+ readonly $anchor: "response";
73
+ readonly title: "Persona Profile Get — response payload";
74
+ readonly description: "Success response to persona/profile/get. Type https://trusttasks.org/spec/persona/profile/get/1.0#response.";
75
+ readonly type: "object";
76
+ readonly additionalProperties: false;
77
+ readonly required: readonly ["profile"];
78
+ readonly properties: {
79
+ readonly profile: {
80
+ readonly $ref: "#/$defs/Profile";
81
+ };
82
+ readonly resolved: {
83
+ readonly type: "array";
84
+ readonly maxItems: 256;
85
+ readonly items: {
86
+ readonly $ref: "#/$defs/Attribute";
87
+ };
88
+ readonly 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.";
89
+ };
90
+ readonly ext: {
91
+ readonly $ref: "#/$defs/Ext";
92
+ };
93
+ };
94
+ };
95
+ readonly Ext: {
96
+ readonly title: "Ext";
97
+ 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.";
98
+ readonly type: "object";
99
+ readonly minProperties: 1;
100
+ readonly additionalProperties: true;
101
+ readonly propertyNames: {
102
+ readonly pattern: "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$";
103
+ };
104
+ };
105
+ readonly Attribute: {
106
+ readonly title: "Attribute";
107
+ 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.";
108
+ readonly type: "object";
109
+ readonly additionalProperties: false;
110
+ readonly required: readonly ["attributeId", "type", "valueType", "provenance", "version", "updatedAt"];
111
+ readonly properties: {
112
+ readonly attributeId: {
113
+ readonly $ref: "#/$defs/Ulid";
114
+ };
115
+ readonly type: {
116
+ readonly $ref: "#/$defs/ClaimType";
117
+ };
118
+ readonly valueType: {
119
+ readonly $ref: "#/$defs/ValueType";
120
+ };
121
+ readonly value: {
122
+ 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.";
123
+ };
124
+ readonly label: {
125
+ readonly type: "string";
126
+ readonly maxLength: 128;
127
+ 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.";
128
+ };
129
+ readonly provenance: {
130
+ readonly $ref: "#/$defs/Provenance";
131
+ };
132
+ readonly stale: {
133
+ readonly type: "boolean";
134
+ 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.";
135
+ };
136
+ readonly staleReason: {
137
+ readonly type: "string";
138
+ readonly enum: readonly ["revoked", "expired", "archived", "deleted", "notFound"];
139
+ readonly description: "Why re-derivation failed. Present only alongside `stale`.";
140
+ };
141
+ readonly version: {
142
+ readonly $ref: "#/$defs/Version";
143
+ };
144
+ readonly createdAt: {
145
+ readonly type: "string";
146
+ readonly format: "date-time";
147
+ };
148
+ readonly updatedAt: {
149
+ readonly type: "string";
150
+ readonly format: "date-time";
151
+ };
152
+ };
153
+ };
154
+ readonly Version: {
155
+ readonly title: "Version";
156
+ readonly description: "A value of the store's monotonic write counter. Server-assigned; a producer never chooses one.";
157
+ readonly type: "integer";
158
+ readonly minimum: 1;
159
+ };
160
+ readonly Provenance: {
161
+ readonly title: "Provenance";
162
+ 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.";
163
+ readonly type: "object";
164
+ readonly required: readonly ["kind"];
165
+ readonly oneOf: readonly [{
166
+ readonly additionalProperties: false;
167
+ readonly required: readonly ["kind"];
168
+ readonly properties: {
169
+ readonly kind: {
170
+ readonly const: "selfAsserted";
171
+ };
172
+ };
173
+ }, {
174
+ readonly additionalProperties: false;
175
+ readonly required: readonly ["kind", "credentialId", "claimPath"];
176
+ readonly properties: {
177
+ readonly kind: {
178
+ readonly const: "credentialBacked";
179
+ };
180
+ readonly credentialId: {
181
+ readonly type: "string";
182
+ readonly minLength: 1;
183
+ readonly description: "Vault identifier of the backing credential.";
184
+ };
185
+ readonly claimPath: {
186
+ readonly type: "string";
187
+ readonly pattern: "^(/[^/~]*(~[01][^/~]*)*)*$";
188
+ readonly description: "RFC 6901 JSON Pointer to the claim within the credential, e.g. `/credentialSubject/familyName`.";
189
+ };
190
+ readonly issuerDid: {
191
+ readonly type: "string";
192
+ readonly minLength: 1;
193
+ readonly description: "Issuer of the backing credential. Advisory: a consumer MUST verify the credential rather than trusting this member.";
194
+ };
195
+ readonly proof: {
196
+ readonly $ref: "#/$defs/ProofRung";
197
+ readonly description: "The disclosure rung this claim was, or will be, presented at.";
198
+ };
199
+ };
200
+ }, {
201
+ readonly additionalProperties: false;
202
+ readonly required: readonly ["kind", "generator"];
203
+ readonly properties: {
204
+ readonly kind: {
205
+ readonly const: "generated";
206
+ };
207
+ readonly generator: {
208
+ readonly type: "string";
209
+ readonly minLength: 1;
210
+ readonly maxLength: 64;
211
+ readonly description: "Names the minting scheme, e.g. `relayEmail`. Maintainer-defined.";
212
+ };
213
+ readonly perVerifier: {
214
+ readonly type: "boolean";
215
+ readonly default: true;
216
+ readonly description: "When true (the default and the only useful setting), a distinct value is minted for each verifier.";
217
+ };
218
+ };
219
+ }];
220
+ };
221
+ readonly ProofRung: {
222
+ readonly title: "ProofRung";
223
+ 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.";
224
+ readonly type: "string";
225
+ readonly enum: readonly ["predicate", "derived", "selectiveDisclosure", "whole"];
226
+ };
227
+ readonly ValueType: {
228
+ readonly title: "ValueType";
229
+ 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.";
230
+ readonly type: "string";
231
+ readonly enum: readonly ["string", "number", "boolean", "date", "object"];
232
+ };
233
+ readonly ClaimType: {
234
+ readonly title: "ClaimType";
235
+ 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.";
236
+ readonly type: "string";
237
+ readonly minLength: 1;
238
+ readonly maxLength: 128;
239
+ readonly pattern: "^(x:)?[a-z][a-zA-Z0-9]*(\\.[a-z][a-zA-Z0-9]*)*$";
240
+ };
241
+ readonly Ulid: {
242
+ readonly title: "Ulid";
243
+ 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.";
244
+ readonly type: "string";
245
+ readonly pattern: "^[0-9A-HJKMNP-TV-Z]{26}$";
246
+ };
247
+ readonly Profile: {
248
+ readonly title: "Profile";
249
+ readonly description: "A named projection over the pool. Agent-scoped, like the pool it draws from. `entries` is ordered and the order is display order.";
250
+ readonly type: "object";
251
+ readonly additionalProperties: false;
252
+ readonly required: readonly ["profileId", "name", "entries", "version", "updatedAt"];
253
+ readonly properties: {
254
+ readonly profileId: {
255
+ readonly $ref: "#/$defs/Ulid";
256
+ };
257
+ readonly name: {
258
+ readonly type: "string";
259
+ readonly minLength: 1;
260
+ readonly maxLength: 128;
261
+ readonly description: "The holder's name for this profile — \"Work\", \"Gaming\". Not disclosed.";
262
+ };
263
+ readonly entries: {
264
+ readonly type: "array";
265
+ readonly maxItems: 256;
266
+ readonly items: {
267
+ readonly $ref: "#/$defs/ProfileEntry";
268
+ };
269
+ };
270
+ readonly credentialRefs: {
271
+ readonly type: "array";
272
+ readonly maxItems: 256;
273
+ readonly items: {
274
+ readonly type: "string";
275
+ readonly minLength: 1;
276
+ };
277
+ readonly 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.";
278
+ };
279
+ readonly version: {
280
+ readonly $ref: "#/$defs/Version";
281
+ };
282
+ readonly createdAt: {
283
+ readonly type: "string";
284
+ readonly format: "date-time";
285
+ };
286
+ readonly updatedAt: {
287
+ readonly type: "string";
288
+ readonly format: "date-time";
289
+ };
290
+ };
291
+ };
292
+ readonly ProfileEntry: {
293
+ readonly title: "ProfileEntry";
294
+ readonly 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.";
295
+ readonly type: "object";
296
+ readonly oneOf: readonly [{
297
+ readonly additionalProperties: false;
298
+ readonly required: readonly ["ref"];
299
+ readonly properties: {
300
+ readonly ref: {
301
+ readonly $ref: "#/$defs/Ulid";
302
+ };
303
+ };
304
+ }, {
305
+ readonly additionalProperties: false;
306
+ readonly required: readonly ["ref", "pinVersion"];
307
+ readonly properties: {
308
+ readonly ref: {
309
+ readonly $ref: "#/$defs/Ulid";
310
+ };
311
+ readonly pinVersion: {
312
+ readonly $ref: "#/$defs/Version";
313
+ };
314
+ };
315
+ }, {
316
+ readonly additionalProperties: false;
317
+ readonly required: readonly ["ref", "override"];
318
+ readonly properties: {
319
+ readonly ref: {
320
+ readonly $ref: "#/$defs/Ulid";
321
+ };
322
+ readonly override: {
323
+ readonly type: "object";
324
+ readonly additionalProperties: false;
325
+ readonly required: readonly ["value"];
326
+ readonly properties: {
327
+ readonly value: {};
328
+ readonly label: {
329
+ readonly type: "string";
330
+ readonly maxLength: 128;
331
+ };
332
+ };
333
+ readonly 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.";
334
+ };
335
+ };
336
+ }, {
337
+ readonly additionalProperties: false;
338
+ readonly required: readonly ["inline"];
339
+ readonly properties: {
340
+ readonly inline: {
341
+ readonly type: "object";
342
+ readonly additionalProperties: false;
343
+ readonly required: readonly ["type", "valueType", "value", "provenance"];
344
+ readonly properties: {
345
+ readonly type: {
346
+ readonly $ref: "#/$defs/ClaimType";
347
+ };
348
+ readonly valueType: {
349
+ readonly $ref: "#/$defs/ValueType";
350
+ };
351
+ readonly value: {};
352
+ readonly label: {
353
+ readonly type: "string";
354
+ readonly maxLength: 128;
355
+ };
356
+ readonly provenance: {
357
+ readonly $ref: "#/$defs/Provenance";
358
+ };
359
+ };
360
+ };
361
+ };
362
+ }];
363
+ };
364
+ };
365
+ };
366
+ /** As {@link PAYLOAD_SCHEMA}, for the success-response variant. */
367
+ export declare const RESPONSE_PAYLOAD_SCHEMA: {
368
+ readonly $schema: "https://json-schema.org/draft/2020-12/schema";
369
+ readonly $ref: "#/$defs/Response";
370
+ readonly $defs: {
371
+ readonly Response: {
372
+ readonly $anchor: "response";
373
+ readonly title: "Persona Profile Get — response payload";
374
+ readonly description: "Success response to persona/profile/get. Type https://trusttasks.org/spec/persona/profile/get/1.0#response.";
375
+ readonly type: "object";
376
+ readonly additionalProperties: false;
377
+ readonly required: readonly ["profile"];
378
+ readonly properties: {
379
+ readonly profile: {
380
+ readonly $ref: "#/$defs/Profile";
381
+ };
382
+ readonly resolved: {
383
+ readonly type: "array";
384
+ readonly maxItems: 256;
385
+ readonly items: {
386
+ readonly $ref: "#/$defs/Attribute";
387
+ };
388
+ readonly 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.";
389
+ };
390
+ readonly ext: {
391
+ readonly $ref: "#/$defs/Ext";
392
+ };
393
+ };
394
+ };
395
+ readonly Ext: {
396
+ readonly title: "Ext";
397
+ 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.";
398
+ readonly type: "object";
399
+ readonly minProperties: 1;
400
+ readonly additionalProperties: true;
401
+ readonly propertyNames: {
402
+ readonly pattern: "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$";
403
+ };
404
+ };
405
+ readonly Attribute: {
406
+ readonly title: "Attribute";
407
+ 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.";
408
+ readonly type: "object";
409
+ readonly additionalProperties: false;
410
+ readonly required: readonly ["attributeId", "type", "valueType", "provenance", "version", "updatedAt"];
411
+ readonly properties: {
412
+ readonly attributeId: {
413
+ readonly $ref: "#/$defs/Ulid";
414
+ };
415
+ readonly type: {
416
+ readonly $ref: "#/$defs/ClaimType";
417
+ };
418
+ readonly valueType: {
419
+ readonly $ref: "#/$defs/ValueType";
420
+ };
421
+ readonly value: {
422
+ 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.";
423
+ };
424
+ readonly label: {
425
+ readonly type: "string";
426
+ readonly maxLength: 128;
427
+ 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.";
428
+ };
429
+ readonly provenance: {
430
+ readonly $ref: "#/$defs/Provenance";
431
+ };
432
+ readonly stale: {
433
+ readonly type: "boolean";
434
+ 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.";
435
+ };
436
+ readonly staleReason: {
437
+ readonly type: "string";
438
+ readonly enum: readonly ["revoked", "expired", "archived", "deleted", "notFound"];
439
+ readonly description: "Why re-derivation failed. Present only alongside `stale`.";
440
+ };
441
+ readonly version: {
442
+ readonly $ref: "#/$defs/Version";
443
+ };
444
+ readonly createdAt: {
445
+ readonly type: "string";
446
+ readonly format: "date-time";
447
+ };
448
+ readonly updatedAt: {
449
+ readonly type: "string";
450
+ readonly format: "date-time";
451
+ };
452
+ };
453
+ };
454
+ readonly Version: {
455
+ readonly title: "Version";
456
+ readonly description: "A value of the store's monotonic write counter. Server-assigned; a producer never chooses one.";
457
+ readonly type: "integer";
458
+ readonly minimum: 1;
459
+ };
460
+ readonly Provenance: {
461
+ readonly title: "Provenance";
462
+ 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.";
463
+ readonly type: "object";
464
+ readonly required: readonly ["kind"];
465
+ readonly oneOf: readonly [{
466
+ readonly additionalProperties: false;
467
+ readonly required: readonly ["kind"];
468
+ readonly properties: {
469
+ readonly kind: {
470
+ readonly const: "selfAsserted";
471
+ };
472
+ };
473
+ }, {
474
+ readonly additionalProperties: false;
475
+ readonly required: readonly ["kind", "credentialId", "claimPath"];
476
+ readonly properties: {
477
+ readonly kind: {
478
+ readonly const: "credentialBacked";
479
+ };
480
+ readonly credentialId: {
481
+ readonly type: "string";
482
+ readonly minLength: 1;
483
+ readonly description: "Vault identifier of the backing credential.";
484
+ };
485
+ readonly claimPath: {
486
+ readonly type: "string";
487
+ readonly pattern: "^(/[^/~]*(~[01][^/~]*)*)*$";
488
+ readonly description: "RFC 6901 JSON Pointer to the claim within the credential, e.g. `/credentialSubject/familyName`.";
489
+ };
490
+ readonly issuerDid: {
491
+ readonly type: "string";
492
+ readonly minLength: 1;
493
+ readonly description: "Issuer of the backing credential. Advisory: a consumer MUST verify the credential rather than trusting this member.";
494
+ };
495
+ readonly proof: {
496
+ readonly $ref: "#/$defs/ProofRung";
497
+ readonly description: "The disclosure rung this claim was, or will be, presented at.";
498
+ };
499
+ };
500
+ }, {
501
+ readonly additionalProperties: false;
502
+ readonly required: readonly ["kind", "generator"];
503
+ readonly properties: {
504
+ readonly kind: {
505
+ readonly const: "generated";
506
+ };
507
+ readonly generator: {
508
+ readonly type: "string";
509
+ readonly minLength: 1;
510
+ readonly maxLength: 64;
511
+ readonly description: "Names the minting scheme, e.g. `relayEmail`. Maintainer-defined.";
512
+ };
513
+ readonly perVerifier: {
514
+ readonly type: "boolean";
515
+ readonly default: true;
516
+ readonly description: "When true (the default and the only useful setting), a distinct value is minted for each verifier.";
517
+ };
518
+ };
519
+ }];
520
+ };
521
+ readonly ProofRung: {
522
+ readonly title: "ProofRung";
523
+ 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.";
524
+ readonly type: "string";
525
+ readonly enum: readonly ["predicate", "derived", "selectiveDisclosure", "whole"];
526
+ };
527
+ readonly ValueType: {
528
+ readonly title: "ValueType";
529
+ 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.";
530
+ readonly type: "string";
531
+ readonly enum: readonly ["string", "number", "boolean", "date", "object"];
532
+ };
533
+ readonly ClaimType: {
534
+ readonly title: "ClaimType";
535
+ 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.";
536
+ readonly type: "string";
537
+ readonly minLength: 1;
538
+ readonly maxLength: 128;
539
+ readonly pattern: "^(x:)?[a-z][a-zA-Z0-9]*(\\.[a-z][a-zA-Z0-9]*)*$";
540
+ };
541
+ readonly Ulid: {
542
+ readonly title: "Ulid";
543
+ 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.";
544
+ readonly type: "string";
545
+ readonly pattern: "^[0-9A-HJKMNP-TV-Z]{26}$";
546
+ };
547
+ readonly Profile: {
548
+ readonly title: "Profile";
549
+ readonly description: "A named projection over the pool. Agent-scoped, like the pool it draws from. `entries` is ordered and the order is display order.";
550
+ readonly type: "object";
551
+ readonly additionalProperties: false;
552
+ readonly required: readonly ["profileId", "name", "entries", "version", "updatedAt"];
553
+ readonly properties: {
554
+ readonly profileId: {
555
+ readonly $ref: "#/$defs/Ulid";
556
+ };
557
+ readonly name: {
558
+ readonly type: "string";
559
+ readonly minLength: 1;
560
+ readonly maxLength: 128;
561
+ readonly description: "The holder's name for this profile — \"Work\", \"Gaming\". Not disclosed.";
562
+ };
563
+ readonly entries: {
564
+ readonly type: "array";
565
+ readonly maxItems: 256;
566
+ readonly items: {
567
+ readonly $ref: "#/$defs/ProfileEntry";
568
+ };
569
+ };
570
+ readonly credentialRefs: {
571
+ readonly type: "array";
572
+ readonly maxItems: 256;
573
+ readonly items: {
574
+ readonly type: "string";
575
+ readonly minLength: 1;
576
+ };
577
+ readonly 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.";
578
+ };
579
+ readonly version: {
580
+ readonly $ref: "#/$defs/Version";
581
+ };
582
+ readonly createdAt: {
583
+ readonly type: "string";
584
+ readonly format: "date-time";
585
+ };
586
+ readonly updatedAt: {
587
+ readonly type: "string";
588
+ readonly format: "date-time";
589
+ };
590
+ };
591
+ };
592
+ readonly ProfileEntry: {
593
+ readonly title: "ProfileEntry";
594
+ readonly 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.";
595
+ readonly type: "object";
596
+ readonly oneOf: readonly [{
597
+ readonly additionalProperties: false;
598
+ readonly required: readonly ["ref"];
599
+ readonly properties: {
600
+ readonly ref: {
601
+ readonly $ref: "#/$defs/Ulid";
602
+ };
603
+ };
604
+ }, {
605
+ readonly additionalProperties: false;
606
+ readonly required: readonly ["ref", "pinVersion"];
607
+ readonly properties: {
608
+ readonly ref: {
609
+ readonly $ref: "#/$defs/Ulid";
610
+ };
611
+ readonly pinVersion: {
612
+ readonly $ref: "#/$defs/Version";
613
+ };
614
+ };
615
+ }, {
616
+ readonly additionalProperties: false;
617
+ readonly required: readonly ["ref", "override"];
618
+ readonly properties: {
619
+ readonly ref: {
620
+ readonly $ref: "#/$defs/Ulid";
621
+ };
622
+ readonly override: {
623
+ readonly type: "object";
624
+ readonly additionalProperties: false;
625
+ readonly required: readonly ["value"];
626
+ readonly properties: {
627
+ readonly value: {};
628
+ readonly label: {
629
+ readonly type: "string";
630
+ readonly maxLength: 128;
631
+ };
632
+ };
633
+ readonly 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.";
634
+ };
635
+ };
636
+ }, {
637
+ readonly additionalProperties: false;
638
+ readonly required: readonly ["inline"];
639
+ readonly properties: {
640
+ readonly inline: {
641
+ readonly type: "object";
642
+ readonly additionalProperties: false;
643
+ readonly required: readonly ["type", "valueType", "value", "provenance"];
644
+ readonly properties: {
645
+ readonly type: {
646
+ readonly $ref: "#/$defs/ClaimType";
647
+ };
648
+ readonly valueType: {
649
+ readonly $ref: "#/$defs/ValueType";
650
+ };
651
+ readonly value: {};
652
+ readonly label: {
653
+ readonly type: "string";
654
+ readonly maxLength: 128;
655
+ };
656
+ readonly provenance: {
657
+ readonly $ref: "#/$defs/Provenance";
658
+ };
659
+ };
660
+ };
661
+ };
662
+ }];
663
+ };
664
+ };
665
+ };
666
+ /**
667
+ * SPEC.md §7.2 policy for the request variant, from this specification's
668
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
669
+ * per-specification and cannot be derived from the document alone, and
670
+ * item 2 needs the schema this carries.
671
+ */
672
+ export declare const SPEC: {
673
+ readonly typeUri: "https://trusttasks.org/spec/persona/profile/get/1.0";
674
+ readonly isBearer: false;
675
+ readonly isProofRequired: true;
676
+ readonly isRecipientRequired: true;
677
+ readonly isIssuedAtRequired: false;
678
+ readonly payloadSchema: {
679
+ readonly $schema: "https://json-schema.org/draft/2020-12/schema";
680
+ readonly $id: "https://trusttasks.org/spec/persona/profile/get/1.0";
681
+ readonly title: "Persona Profile Get — payload";
682
+ readonly description: "Read one profile, either as composed (the entries the holder wrote) or as resolved (the claims it would actually present).";
683
+ readonly type: "object";
684
+ readonly additionalProperties: false;
685
+ readonly required: readonly ["profileId"];
686
+ readonly properties: {
687
+ readonly profileId: {
688
+ readonly $ref: "#/$defs/Ulid";
689
+ };
690
+ readonly resolve: {
691
+ readonly type: "boolean";
692
+ readonly default: false;
693
+ readonly 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.";
694
+ };
695
+ readonly ext: {
696
+ readonly $ref: "#/$defs/Ext";
697
+ };
698
+ };
699
+ readonly $defs: {
700
+ readonly Response: {
701
+ readonly $anchor: "response";
702
+ readonly title: "Persona Profile Get — response payload";
703
+ readonly description: "Success response to persona/profile/get. Type https://trusttasks.org/spec/persona/profile/get/1.0#response.";
704
+ readonly type: "object";
705
+ readonly additionalProperties: false;
706
+ readonly required: readonly ["profile"];
707
+ readonly properties: {
708
+ readonly profile: {
709
+ readonly $ref: "#/$defs/Profile";
710
+ };
711
+ readonly resolved: {
712
+ readonly type: "array";
713
+ readonly maxItems: 256;
714
+ readonly items: {
715
+ readonly $ref: "#/$defs/Attribute";
716
+ };
717
+ readonly 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.";
718
+ };
719
+ readonly ext: {
720
+ readonly $ref: "#/$defs/Ext";
721
+ };
722
+ };
723
+ };
724
+ readonly Ext: {
725
+ readonly title: "Ext";
726
+ 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.";
727
+ readonly type: "object";
728
+ readonly minProperties: 1;
729
+ readonly additionalProperties: true;
730
+ readonly propertyNames: {
731
+ readonly pattern: "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$";
732
+ };
733
+ };
734
+ readonly Attribute: {
735
+ readonly title: "Attribute";
736
+ 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.";
737
+ readonly type: "object";
738
+ readonly additionalProperties: false;
739
+ readonly required: readonly ["attributeId", "type", "valueType", "provenance", "version", "updatedAt"];
740
+ readonly properties: {
741
+ readonly attributeId: {
742
+ readonly $ref: "#/$defs/Ulid";
743
+ };
744
+ readonly type: {
745
+ readonly $ref: "#/$defs/ClaimType";
746
+ };
747
+ readonly valueType: {
748
+ readonly $ref: "#/$defs/ValueType";
749
+ };
750
+ readonly value: {
751
+ 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.";
752
+ };
753
+ readonly label: {
754
+ readonly type: "string";
755
+ readonly maxLength: 128;
756
+ 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.";
757
+ };
758
+ readonly provenance: {
759
+ readonly $ref: "#/$defs/Provenance";
760
+ };
761
+ readonly stale: {
762
+ readonly type: "boolean";
763
+ 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.";
764
+ };
765
+ readonly staleReason: {
766
+ readonly type: "string";
767
+ readonly enum: readonly ["revoked", "expired", "archived", "deleted", "notFound"];
768
+ readonly description: "Why re-derivation failed. Present only alongside `stale`.";
769
+ };
770
+ readonly version: {
771
+ readonly $ref: "#/$defs/Version";
772
+ };
773
+ readonly createdAt: {
774
+ readonly type: "string";
775
+ readonly format: "date-time";
776
+ };
777
+ readonly updatedAt: {
778
+ readonly type: "string";
779
+ readonly format: "date-time";
780
+ };
781
+ };
782
+ };
783
+ readonly Version: {
784
+ readonly title: "Version";
785
+ readonly description: "A value of the store's monotonic write counter. Server-assigned; a producer never chooses one.";
786
+ readonly type: "integer";
787
+ readonly minimum: 1;
788
+ };
789
+ readonly Provenance: {
790
+ readonly title: "Provenance";
791
+ 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.";
792
+ readonly type: "object";
793
+ readonly required: readonly ["kind"];
794
+ readonly oneOf: readonly [{
795
+ readonly additionalProperties: false;
796
+ readonly required: readonly ["kind"];
797
+ readonly properties: {
798
+ readonly kind: {
799
+ readonly const: "selfAsserted";
800
+ };
801
+ };
802
+ }, {
803
+ readonly additionalProperties: false;
804
+ readonly required: readonly ["kind", "credentialId", "claimPath"];
805
+ readonly properties: {
806
+ readonly kind: {
807
+ readonly const: "credentialBacked";
808
+ };
809
+ readonly credentialId: {
810
+ readonly type: "string";
811
+ readonly minLength: 1;
812
+ readonly description: "Vault identifier of the backing credential.";
813
+ };
814
+ readonly claimPath: {
815
+ readonly type: "string";
816
+ readonly pattern: "^(/[^/~]*(~[01][^/~]*)*)*$";
817
+ readonly description: "RFC 6901 JSON Pointer to the claim within the credential, e.g. `/credentialSubject/familyName`.";
818
+ };
819
+ readonly issuerDid: {
820
+ readonly type: "string";
821
+ readonly minLength: 1;
822
+ readonly description: "Issuer of the backing credential. Advisory: a consumer MUST verify the credential rather than trusting this member.";
823
+ };
824
+ readonly proof: {
825
+ readonly $ref: "#/$defs/ProofRung";
826
+ readonly description: "The disclosure rung this claim was, or will be, presented at.";
827
+ };
828
+ };
829
+ }, {
830
+ readonly additionalProperties: false;
831
+ readonly required: readonly ["kind", "generator"];
832
+ readonly properties: {
833
+ readonly kind: {
834
+ readonly const: "generated";
835
+ };
836
+ readonly generator: {
837
+ readonly type: "string";
838
+ readonly minLength: 1;
839
+ readonly maxLength: 64;
840
+ readonly description: "Names the minting scheme, e.g. `relayEmail`. Maintainer-defined.";
841
+ };
842
+ readonly perVerifier: {
843
+ readonly type: "boolean";
844
+ readonly default: true;
845
+ readonly description: "When true (the default and the only useful setting), a distinct value is minted for each verifier.";
846
+ };
847
+ };
848
+ }];
849
+ };
850
+ readonly ProofRung: {
851
+ readonly title: "ProofRung";
852
+ 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.";
853
+ readonly type: "string";
854
+ readonly enum: readonly ["predicate", "derived", "selectiveDisclosure", "whole"];
855
+ };
856
+ readonly ValueType: {
857
+ readonly title: "ValueType";
858
+ 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.";
859
+ readonly type: "string";
860
+ readonly enum: readonly ["string", "number", "boolean", "date", "object"];
861
+ };
862
+ readonly ClaimType: {
863
+ readonly title: "ClaimType";
864
+ 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.";
865
+ readonly type: "string";
866
+ readonly minLength: 1;
867
+ readonly maxLength: 128;
868
+ readonly pattern: "^(x:)?[a-z][a-zA-Z0-9]*(\\.[a-z][a-zA-Z0-9]*)*$";
869
+ };
870
+ readonly Ulid: {
871
+ readonly title: "Ulid";
872
+ 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.";
873
+ readonly type: "string";
874
+ readonly pattern: "^[0-9A-HJKMNP-TV-Z]{26}$";
875
+ };
876
+ readonly Profile: {
877
+ readonly title: "Profile";
878
+ readonly description: "A named projection over the pool. Agent-scoped, like the pool it draws from. `entries` is ordered and the order is display order.";
879
+ readonly type: "object";
880
+ readonly additionalProperties: false;
881
+ readonly required: readonly ["profileId", "name", "entries", "version", "updatedAt"];
882
+ readonly properties: {
883
+ readonly profileId: {
884
+ readonly $ref: "#/$defs/Ulid";
885
+ };
886
+ readonly name: {
887
+ readonly type: "string";
888
+ readonly minLength: 1;
889
+ readonly maxLength: 128;
890
+ readonly description: "The holder's name for this profile — \"Work\", \"Gaming\". Not disclosed.";
891
+ };
892
+ readonly entries: {
893
+ readonly type: "array";
894
+ readonly maxItems: 256;
895
+ readonly items: {
896
+ readonly $ref: "#/$defs/ProfileEntry";
897
+ };
898
+ };
899
+ readonly credentialRefs: {
900
+ readonly type: "array";
901
+ readonly maxItems: 256;
902
+ readonly items: {
903
+ readonly type: "string";
904
+ readonly minLength: 1;
905
+ };
906
+ readonly 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.";
907
+ };
908
+ readonly version: {
909
+ readonly $ref: "#/$defs/Version";
910
+ };
911
+ readonly createdAt: {
912
+ readonly type: "string";
913
+ readonly format: "date-time";
914
+ };
915
+ readonly updatedAt: {
916
+ readonly type: "string";
917
+ readonly format: "date-time";
918
+ };
919
+ };
920
+ };
921
+ readonly ProfileEntry: {
922
+ readonly title: "ProfileEntry";
923
+ readonly 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.";
924
+ readonly type: "object";
925
+ readonly oneOf: readonly [{
926
+ readonly additionalProperties: false;
927
+ readonly required: readonly ["ref"];
928
+ readonly properties: {
929
+ readonly ref: {
930
+ readonly $ref: "#/$defs/Ulid";
931
+ };
932
+ };
933
+ }, {
934
+ readonly additionalProperties: false;
935
+ readonly required: readonly ["ref", "pinVersion"];
936
+ readonly properties: {
937
+ readonly ref: {
938
+ readonly $ref: "#/$defs/Ulid";
939
+ };
940
+ readonly pinVersion: {
941
+ readonly $ref: "#/$defs/Version";
942
+ };
943
+ };
944
+ }, {
945
+ readonly additionalProperties: false;
946
+ readonly required: readonly ["ref", "override"];
947
+ readonly properties: {
948
+ readonly ref: {
949
+ readonly $ref: "#/$defs/Ulid";
950
+ };
951
+ readonly override: {
952
+ readonly type: "object";
953
+ readonly additionalProperties: false;
954
+ readonly required: readonly ["value"];
955
+ readonly properties: {
956
+ readonly value: {};
957
+ readonly label: {
958
+ readonly type: "string";
959
+ readonly maxLength: 128;
960
+ };
961
+ };
962
+ readonly 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.";
963
+ };
964
+ };
965
+ }, {
966
+ readonly additionalProperties: false;
967
+ readonly required: readonly ["inline"];
968
+ readonly properties: {
969
+ readonly inline: {
970
+ readonly type: "object";
971
+ readonly additionalProperties: false;
972
+ readonly required: readonly ["type", "valueType", "value", "provenance"];
973
+ readonly properties: {
974
+ readonly type: {
975
+ readonly $ref: "#/$defs/ClaimType";
976
+ };
977
+ readonly valueType: {
978
+ readonly $ref: "#/$defs/ValueType";
979
+ };
980
+ readonly value: {};
981
+ readonly label: {
982
+ readonly type: "string";
983
+ readonly maxLength: 128;
984
+ };
985
+ readonly provenance: {
986
+ readonly $ref: "#/$defs/Provenance";
987
+ };
988
+ };
989
+ };
990
+ };
991
+ }];
992
+ };
993
+ };
994
+ };
995
+ };
996
+ /**
997
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
998
+ * tracks the *issuer* party's requirement because a response swaps the
999
+ * parties (§7.3 item 5).
1000
+ */
1001
+ export declare const RESPONSE_SPEC: {
1002
+ readonly typeUri: "https://trusttasks.org/spec/persona/profile/get/1.0#response";
1003
+ readonly isBearer: false;
1004
+ readonly isProofRequired: true;
1005
+ readonly isRecipientRequired: true;
1006
+ readonly isIssuedAtRequired: false;
1007
+ readonly payloadSchema: {
1008
+ readonly $schema: "https://json-schema.org/draft/2020-12/schema";
1009
+ readonly $ref: "#/$defs/Response";
1010
+ readonly $defs: {
1011
+ readonly Response: {
1012
+ readonly $anchor: "response";
1013
+ readonly title: "Persona Profile Get — response payload";
1014
+ readonly description: "Success response to persona/profile/get. Type https://trusttasks.org/spec/persona/profile/get/1.0#response.";
1015
+ readonly type: "object";
1016
+ readonly additionalProperties: false;
1017
+ readonly required: readonly ["profile"];
1018
+ readonly properties: {
1019
+ readonly profile: {
1020
+ readonly $ref: "#/$defs/Profile";
1021
+ };
1022
+ readonly resolved: {
1023
+ readonly type: "array";
1024
+ readonly maxItems: 256;
1025
+ readonly items: {
1026
+ readonly $ref: "#/$defs/Attribute";
1027
+ };
1028
+ readonly 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.";
1029
+ };
1030
+ readonly ext: {
1031
+ readonly $ref: "#/$defs/Ext";
1032
+ };
1033
+ };
1034
+ };
1035
+ readonly Ext: {
1036
+ readonly title: "Ext";
1037
+ 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.";
1038
+ readonly type: "object";
1039
+ readonly minProperties: 1;
1040
+ readonly additionalProperties: true;
1041
+ readonly propertyNames: {
1042
+ readonly pattern: "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$";
1043
+ };
1044
+ };
1045
+ readonly Attribute: {
1046
+ readonly title: "Attribute";
1047
+ 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.";
1048
+ readonly type: "object";
1049
+ readonly additionalProperties: false;
1050
+ readonly required: readonly ["attributeId", "type", "valueType", "provenance", "version", "updatedAt"];
1051
+ readonly properties: {
1052
+ readonly attributeId: {
1053
+ readonly $ref: "#/$defs/Ulid";
1054
+ };
1055
+ readonly type: {
1056
+ readonly $ref: "#/$defs/ClaimType";
1057
+ };
1058
+ readonly valueType: {
1059
+ readonly $ref: "#/$defs/ValueType";
1060
+ };
1061
+ readonly value: {
1062
+ 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.";
1063
+ };
1064
+ readonly label: {
1065
+ readonly type: "string";
1066
+ readonly maxLength: 128;
1067
+ 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.";
1068
+ };
1069
+ readonly provenance: {
1070
+ readonly $ref: "#/$defs/Provenance";
1071
+ };
1072
+ readonly stale: {
1073
+ readonly type: "boolean";
1074
+ 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.";
1075
+ };
1076
+ readonly staleReason: {
1077
+ readonly type: "string";
1078
+ readonly enum: readonly ["revoked", "expired", "archived", "deleted", "notFound"];
1079
+ readonly description: "Why re-derivation failed. Present only alongside `stale`.";
1080
+ };
1081
+ readonly version: {
1082
+ readonly $ref: "#/$defs/Version";
1083
+ };
1084
+ readonly createdAt: {
1085
+ readonly type: "string";
1086
+ readonly format: "date-time";
1087
+ };
1088
+ readonly updatedAt: {
1089
+ readonly type: "string";
1090
+ readonly format: "date-time";
1091
+ };
1092
+ };
1093
+ };
1094
+ readonly Version: {
1095
+ readonly title: "Version";
1096
+ readonly description: "A value of the store's monotonic write counter. Server-assigned; a producer never chooses one.";
1097
+ readonly type: "integer";
1098
+ readonly minimum: 1;
1099
+ };
1100
+ readonly Provenance: {
1101
+ readonly title: "Provenance";
1102
+ 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.";
1103
+ readonly type: "object";
1104
+ readonly required: readonly ["kind"];
1105
+ readonly oneOf: readonly [{
1106
+ readonly additionalProperties: false;
1107
+ readonly required: readonly ["kind"];
1108
+ readonly properties: {
1109
+ readonly kind: {
1110
+ readonly const: "selfAsserted";
1111
+ };
1112
+ };
1113
+ }, {
1114
+ readonly additionalProperties: false;
1115
+ readonly required: readonly ["kind", "credentialId", "claimPath"];
1116
+ readonly properties: {
1117
+ readonly kind: {
1118
+ readonly const: "credentialBacked";
1119
+ };
1120
+ readonly credentialId: {
1121
+ readonly type: "string";
1122
+ readonly minLength: 1;
1123
+ readonly description: "Vault identifier of the backing credential.";
1124
+ };
1125
+ readonly claimPath: {
1126
+ readonly type: "string";
1127
+ readonly pattern: "^(/[^/~]*(~[01][^/~]*)*)*$";
1128
+ readonly description: "RFC 6901 JSON Pointer to the claim within the credential, e.g. `/credentialSubject/familyName`.";
1129
+ };
1130
+ readonly issuerDid: {
1131
+ readonly type: "string";
1132
+ readonly minLength: 1;
1133
+ readonly description: "Issuer of the backing credential. Advisory: a consumer MUST verify the credential rather than trusting this member.";
1134
+ };
1135
+ readonly proof: {
1136
+ readonly $ref: "#/$defs/ProofRung";
1137
+ readonly description: "The disclosure rung this claim was, or will be, presented at.";
1138
+ };
1139
+ };
1140
+ }, {
1141
+ readonly additionalProperties: false;
1142
+ readonly required: readonly ["kind", "generator"];
1143
+ readonly properties: {
1144
+ readonly kind: {
1145
+ readonly const: "generated";
1146
+ };
1147
+ readonly generator: {
1148
+ readonly type: "string";
1149
+ readonly minLength: 1;
1150
+ readonly maxLength: 64;
1151
+ readonly description: "Names the minting scheme, e.g. `relayEmail`. Maintainer-defined.";
1152
+ };
1153
+ readonly perVerifier: {
1154
+ readonly type: "boolean";
1155
+ readonly default: true;
1156
+ readonly description: "When true (the default and the only useful setting), a distinct value is minted for each verifier.";
1157
+ };
1158
+ };
1159
+ }];
1160
+ };
1161
+ readonly ProofRung: {
1162
+ readonly title: "ProofRung";
1163
+ 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.";
1164
+ readonly type: "string";
1165
+ readonly enum: readonly ["predicate", "derived", "selectiveDisclosure", "whole"];
1166
+ };
1167
+ readonly ValueType: {
1168
+ readonly title: "ValueType";
1169
+ 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.";
1170
+ readonly type: "string";
1171
+ readonly enum: readonly ["string", "number", "boolean", "date", "object"];
1172
+ };
1173
+ readonly ClaimType: {
1174
+ readonly title: "ClaimType";
1175
+ 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.";
1176
+ readonly type: "string";
1177
+ readonly minLength: 1;
1178
+ readonly maxLength: 128;
1179
+ readonly pattern: "^(x:)?[a-z][a-zA-Z0-9]*(\\.[a-z][a-zA-Z0-9]*)*$";
1180
+ };
1181
+ readonly Ulid: {
1182
+ readonly title: "Ulid";
1183
+ 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.";
1184
+ readonly type: "string";
1185
+ readonly pattern: "^[0-9A-HJKMNP-TV-Z]{26}$";
1186
+ };
1187
+ readonly Profile: {
1188
+ readonly title: "Profile";
1189
+ readonly description: "A named projection over the pool. Agent-scoped, like the pool it draws from. `entries` is ordered and the order is display order.";
1190
+ readonly type: "object";
1191
+ readonly additionalProperties: false;
1192
+ readonly required: readonly ["profileId", "name", "entries", "version", "updatedAt"];
1193
+ readonly properties: {
1194
+ readonly profileId: {
1195
+ readonly $ref: "#/$defs/Ulid";
1196
+ };
1197
+ readonly name: {
1198
+ readonly type: "string";
1199
+ readonly minLength: 1;
1200
+ readonly maxLength: 128;
1201
+ readonly description: "The holder's name for this profile — \"Work\", \"Gaming\". Not disclosed.";
1202
+ };
1203
+ readonly entries: {
1204
+ readonly type: "array";
1205
+ readonly maxItems: 256;
1206
+ readonly items: {
1207
+ readonly $ref: "#/$defs/ProfileEntry";
1208
+ };
1209
+ };
1210
+ readonly credentialRefs: {
1211
+ readonly type: "array";
1212
+ readonly maxItems: 256;
1213
+ readonly items: {
1214
+ readonly type: "string";
1215
+ readonly minLength: 1;
1216
+ };
1217
+ readonly 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.";
1218
+ };
1219
+ readonly version: {
1220
+ readonly $ref: "#/$defs/Version";
1221
+ };
1222
+ readonly createdAt: {
1223
+ readonly type: "string";
1224
+ readonly format: "date-time";
1225
+ };
1226
+ readonly updatedAt: {
1227
+ readonly type: "string";
1228
+ readonly format: "date-time";
1229
+ };
1230
+ };
1231
+ };
1232
+ readonly ProfileEntry: {
1233
+ readonly title: "ProfileEntry";
1234
+ readonly 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.";
1235
+ readonly type: "object";
1236
+ readonly oneOf: readonly [{
1237
+ readonly additionalProperties: false;
1238
+ readonly required: readonly ["ref"];
1239
+ readonly properties: {
1240
+ readonly ref: {
1241
+ readonly $ref: "#/$defs/Ulid";
1242
+ };
1243
+ };
1244
+ }, {
1245
+ readonly additionalProperties: false;
1246
+ readonly required: readonly ["ref", "pinVersion"];
1247
+ readonly properties: {
1248
+ readonly ref: {
1249
+ readonly $ref: "#/$defs/Ulid";
1250
+ };
1251
+ readonly pinVersion: {
1252
+ readonly $ref: "#/$defs/Version";
1253
+ };
1254
+ };
1255
+ }, {
1256
+ readonly additionalProperties: false;
1257
+ readonly required: readonly ["ref", "override"];
1258
+ readonly properties: {
1259
+ readonly ref: {
1260
+ readonly $ref: "#/$defs/Ulid";
1261
+ };
1262
+ readonly override: {
1263
+ readonly type: "object";
1264
+ readonly additionalProperties: false;
1265
+ readonly required: readonly ["value"];
1266
+ readonly properties: {
1267
+ readonly value: {};
1268
+ readonly label: {
1269
+ readonly type: "string";
1270
+ readonly maxLength: 128;
1271
+ };
1272
+ };
1273
+ readonly 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.";
1274
+ };
1275
+ };
1276
+ }, {
1277
+ readonly additionalProperties: false;
1278
+ readonly required: readonly ["inline"];
1279
+ readonly properties: {
1280
+ readonly inline: {
1281
+ readonly type: "object";
1282
+ readonly additionalProperties: false;
1283
+ readonly required: readonly ["type", "valueType", "value", "provenance"];
1284
+ readonly properties: {
1285
+ readonly type: {
1286
+ readonly $ref: "#/$defs/ClaimType";
1287
+ };
1288
+ readonly valueType: {
1289
+ readonly $ref: "#/$defs/ValueType";
1290
+ };
1291
+ readonly value: {};
1292
+ readonly label: {
1293
+ readonly type: "string";
1294
+ readonly maxLength: 128;
1295
+ };
1296
+ readonly provenance: {
1297
+ readonly $ref: "#/$defs/Provenance";
1298
+ };
1299
+ };
1300
+ };
1301
+ };
1302
+ }];
1303
+ };
1304
+ };
1305
+ };
1306
+ };
1307
+ //# sourceMappingURL=payload.d.ts.map