@openvtc/trust-tasks 0.26.17 → 0.26.19

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 (368) hide show
  1. package/CHANGELOG.md +222 -0
  2. package/dist/_shared/components.d.ts +867 -3
  3. package/dist/_shared/components.d.ts.map +1 -1
  4. package/dist/auth/oob/_shared/0.1/oob.d.ts +1 -1
  5. package/dist/auth/oob/_shared/0.1/oob.d.ts.map +1 -1
  6. package/dist/auth/oob/grant/0.2/payload.d.ts +262 -0
  7. package/dist/auth/oob/grant/0.2/payload.d.ts.map +1 -0
  8. package/dist/auth/oob/grant/0.2/payload.js +140 -0
  9. package/dist/auth/oob/grant/0.2/payload.js.map +1 -0
  10. package/dist/auth/oob/prove/0.2/payload.d.ts +836 -0
  11. package/dist/auth/oob/prove/0.2/payload.d.ts.map +1 -0
  12. package/dist/auth/oob/prove/0.2/payload.js +468 -0
  13. package/dist/auth/oob/prove/0.2/payload.js.map +1 -0
  14. package/dist/auth/oob/respond/0.2/payload.d.ts +235 -0
  15. package/dist/auth/oob/respond/0.2/payload.d.ts.map +1 -0
  16. package/dist/auth/oob/respond/0.2/payload.js +140 -0
  17. package/dist/auth/oob/respond/0.2/payload.js.map +1 -0
  18. package/dist/device/list/0.1/payload.d.ts +4 -4
  19. package/dist/device/list/0.1/payload.d.ts.map +1 -1
  20. package/dist/device/list/0.1/payload.js +2 -0
  21. package/dist/device/list/0.1/payload.js.map +1 -1
  22. package/dist/device/list/0.2/payload.d.ts +4 -4
  23. package/dist/device/list/0.2/payload.d.ts.map +1 -1
  24. package/dist/device/list/0.2/payload.js +2 -0
  25. package/dist/device/list/0.2/payload.js.map +1 -1
  26. package/dist/device/register/0.1/payload.d.ts +4 -4
  27. package/dist/device/register/0.1/payload.d.ts.map +1 -1
  28. package/dist/device/register/0.1/payload.js +2 -0
  29. package/dist/device/register/0.1/payload.js.map +1 -1
  30. package/dist/device/register/0.2/payload.d.ts +4 -4
  31. package/dist/device/register/0.2/payload.d.ts.map +1 -1
  32. package/dist/device/register/0.2/payload.js +2 -0
  33. package/dist/device/register/0.2/payload.js.map +1 -1
  34. package/dist/index.d.ts +61 -0
  35. package/dist/index.d.ts.map +1 -1
  36. package/dist/index.js +61 -0
  37. package/dist/index.js.map +1 -1
  38. package/dist/keys/sign-document/0.1/payload.d.ts +627 -0
  39. package/dist/keys/sign-document/0.1/payload.d.ts.map +1 -0
  40. package/dist/keys/sign-document/0.1/payload.js +341 -0
  41. package/dist/keys/sign-document/0.1/payload.js.map +1 -0
  42. package/dist/persona/_shared/0.1/contact-annotations.d.ts +22 -0
  43. package/dist/persona/_shared/0.1/contact-annotations.d.ts.map +1 -0
  44. package/dist/persona/_shared/0.1/contact-annotations.js +6 -0
  45. package/dist/persona/_shared/0.1/contact-annotations.js.map +1 -0
  46. package/dist/persona/contact/get/1.1/payload.d.ts +1403 -0
  47. package/dist/persona/contact/get/1.1/payload.d.ts.map +1 -0
  48. package/dist/persona/contact/get/1.1/payload.js +804 -0
  49. package/dist/persona/contact/get/1.1/payload.js.map +1 -0
  50. package/dist/persona/contact/list/1.1/payload.d.ts +803 -0
  51. package/dist/persona/contact/list/1.1/payload.d.ts.map +1 -0
  52. package/dist/persona/contact/list/1.1/payload.js +417 -0
  53. package/dist/persona/contact/list/1.1/payload.js.map +1 -0
  54. package/dist/persona/contact/lists/delete/1.0/payload.d.ts +289 -0
  55. package/dist/persona/contact/lists/delete/1.0/payload.d.ts.map +1 -0
  56. package/dist/persona/contact/lists/delete/1.0/payload.js +166 -0
  57. package/dist/persona/contact/lists/delete/1.0/payload.js.map +1 -0
  58. package/dist/persona/contact/lists/list/1.0/payload.d.ts +527 -0
  59. package/dist/persona/contact/lists/list/1.0/payload.d.ts.map +1 -0
  60. package/dist/persona/contact/lists/list/1.0/payload.js +294 -0
  61. package/dist/persona/contact/lists/list/1.0/payload.js.map +1 -0
  62. package/dist/persona/contact/lists/put/1.0/payload.d.ts +629 -0
  63. package/dist/persona/contact/lists/put/1.0/payload.d.ts.map +1 -0
  64. package/dist/persona/contact/lists/put/1.0/payload.js +366 -0
  65. package/dist/persona/contact/lists/put/1.0/payload.js.map +1 -0
  66. package/dist/persona/contact/lists/show/1.0/payload.d.ts +476 -0
  67. package/dist/persona/contact/lists/show/1.0/payload.d.ts.map +1 -0
  68. package/dist/persona/contact/lists/show/1.0/payload.js +272 -0
  69. package/dist/persona/contact/lists/show/1.0/payload.js.map +1 -0
  70. package/dist/persona/contact/put/1.1/payload.d.ts +1444 -0
  71. package/dist/persona/contact/put/1.1/payload.d.ts.map +1 -0
  72. package/dist/persona/contact/put/1.1/payload.js +850 -0
  73. package/dist/persona/contact/put/1.1/payload.js.map +1 -0
  74. package/dist/rooms/keys/seal/0.1/payload.d.ts +24 -4
  75. package/dist/rooms/keys/seal/0.1/payload.d.ts.map +1 -1
  76. package/dist/rooms/keys/seal/0.1/payload.js +12 -2
  77. package/dist/rooms/keys/seal/0.1/payload.js.map +1 -1
  78. package/dist/rooms/keys/seal/0.2/payload.d.ts +24 -4
  79. package/dist/rooms/keys/seal/0.2/payload.d.ts.map +1 -1
  80. package/dist/rooms/keys/seal/0.2/payload.js +12 -2
  81. package/dist/rooms/keys/seal/0.2/payload.js.map +1 -1
  82. package/dist/rooms/owner/group/add/0.3/payload.d.ts +417 -0
  83. package/dist/rooms/owner/group/add/0.3/payload.d.ts.map +1 -0
  84. package/dist/rooms/owner/group/add/0.3/payload.js +218 -0
  85. package/dist/rooms/owner/group/add/0.3/payload.js.map +1 -0
  86. package/dist/rooms/owner/group/remove/0.3/payload.d.ts +600 -0
  87. package/dist/rooms/owner/group/remove/0.3/payload.d.ts.map +1 -0
  88. package/dist/rooms/owner/group/remove/0.3/payload.js +310 -0
  89. package/dist/rooms/owner/group/remove/0.3/payload.js.map +1 -0
  90. package/dist/rooms/owner/group/renew/0.2/payload.d.ts +299 -0
  91. package/dist/rooms/owner/group/renew/0.2/payload.d.ts.map +1 -0
  92. package/dist/rooms/owner/group/renew/0.2/payload.js +163 -0
  93. package/dist/rooms/owner/group/renew/0.2/payload.js.map +1 -0
  94. package/dist/rooms/owner/register/0.2/payload.d.ts +591 -0
  95. package/dist/rooms/owner/register/0.2/payload.d.ts.map +1 -0
  96. package/dist/rooms/owner/register/0.2/payload.js +335 -0
  97. package/dist/rooms/owner/register/0.2/payload.js.map +1 -0
  98. package/dist/rooms/records/get/0.1/payload.d.ts +24 -4
  99. package/dist/rooms/records/get/0.1/payload.d.ts.map +1 -1
  100. package/dist/rooms/records/get/0.1/payload.js +12 -2
  101. package/dist/rooms/records/get/0.1/payload.js.map +1 -1
  102. package/dist/rooms/records/get/0.2/payload.d.ts +24 -4
  103. package/dist/rooms/records/get/0.2/payload.d.ts.map +1 -1
  104. package/dist/rooms/records/get/0.2/payload.js +12 -2
  105. package/dist/rooms/records/get/0.2/payload.js.map +1 -1
  106. package/dist/rooms/records/put/0.1/payload.d.ts +24 -4
  107. package/dist/rooms/records/put/0.1/payload.d.ts.map +1 -1
  108. package/dist/rooms/records/put/0.1/payload.js +12 -2
  109. package/dist/rooms/records/put/0.1/payload.js.map +1 -1
  110. package/dist/rooms/records/put/0.2/payload.d.ts +24 -4
  111. package/dist/rooms/records/put/0.2/payload.d.ts.map +1 -1
  112. package/dist/rooms/records/put/0.2/payload.js +12 -2
  113. package/dist/rooms/records/put/0.2/payload.js.map +1 -1
  114. package/dist/vtc/admin/events/_shared/0.3/topic.d.ts +30 -0
  115. package/dist/vtc/admin/events/_shared/0.3/topic.d.ts.map +1 -0
  116. package/dist/vtc/admin/events/_shared/0.3/topic.js +6 -0
  117. package/dist/vtc/admin/events/_shared/0.3/topic.js.map +1 -0
  118. package/dist/vtc/admin/events/event/0.3/payload.d.ts +172 -0
  119. package/dist/vtc/admin/events/event/0.3/payload.d.ts.map +1 -0
  120. package/dist/vtc/admin/events/event/0.3/payload.js +102 -0
  121. package/dist/vtc/admin/events/event/0.3/payload.js.map +1 -0
  122. package/dist/vtc/admin/events/subscribe/0.3/payload.d.ts +409 -0
  123. package/dist/vtc/admin/events/subscribe/0.3/payload.d.ts.map +1 -0
  124. package/dist/vtc/admin/events/subscribe/0.3/payload.js +236 -0
  125. package/dist/vtc/admin/events/subscribe/0.3/payload.js.map +1 -0
  126. package/dist/vtc/directory/_shared/0.1/admin-note.d.ts +16 -0
  127. package/dist/vtc/directory/_shared/0.1/admin-note.d.ts.map +1 -0
  128. package/dist/vtc/directory/_shared/0.1/admin-note.js +6 -0
  129. package/dist/vtc/directory/_shared/0.1/admin-note.js.map +1 -0
  130. package/dist/vtc/directory/_shared/0.1/directory-card.d.ts +22 -0
  131. package/dist/vtc/directory/_shared/0.1/directory-card.d.ts.map +1 -0
  132. package/dist/vtc/directory/_shared/0.1/directory-card.js +6 -0
  133. package/dist/vtc/directory/_shared/0.1/directory-card.js.map +1 -0
  134. package/dist/vtc/directory/_shared/0.1/disclosure-statement.d.ts +18 -0
  135. package/dist/vtc/directory/_shared/0.1/disclosure-statement.d.ts.map +1 -0
  136. package/dist/vtc/directory/_shared/0.1/disclosure-statement.js +6 -0
  137. package/dist/vtc/directory/_shared/0.1/disclosure-statement.js.map +1 -0
  138. package/dist/vtc/directory/_shared/0.1/field-definition.d.ts +16 -0
  139. package/dist/vtc/directory/_shared/0.1/field-definition.d.ts.map +1 -0
  140. package/dist/vtc/directory/_shared/0.1/field-definition.js +6 -0
  141. package/dist/vtc/directory/_shared/0.1/field-definition.js.map +1 -0
  142. package/dist/vtc/directory/card/assert/0.1/payload.d.ts +780 -0
  143. package/dist/vtc/directory/card/assert/0.1/payload.d.ts.map +1 -0
  144. package/dist/vtc/directory/card/assert/0.1/payload.js +454 -0
  145. package/dist/vtc/directory/card/assert/0.1/payload.js.map +1 -0
  146. package/dist/vtc/directory/card/present/0.1/payload.d.ts +603 -0
  147. package/dist/vtc/directory/card/present/0.1/payload.d.ts.map +1 -0
  148. package/dist/vtc/directory/card/present/0.1/payload.js +297 -0
  149. package/dist/vtc/directory/card/present/0.1/payload.js.map +1 -0
  150. package/dist/vtc/directory/card/public/0.1/payload.d.ts +348 -0
  151. package/dist/vtc/directory/card/public/0.1/payload.d.ts.map +1 -0
  152. package/dist/vtc/directory/card/public/0.1/payload.js +197 -0
  153. package/dist/vtc/directory/card/public/0.1/payload.js.map +1 -0
  154. package/dist/vtc/directory/card/publish/0.1/payload.d.ts +384 -0
  155. package/dist/vtc/directory/card/publish/0.1/payload.d.ts.map +1 -0
  156. package/dist/vtc/directory/card/publish/0.1/payload.js +222 -0
  157. package/dist/vtc/directory/card/publish/0.1/payload.js.map +1 -0
  158. package/dist/vtc/directory/card/show/0.1/payload.d.ts +1276 -0
  159. package/dist/vtc/directory/card/show/0.1/payload.d.ts.map +1 -0
  160. package/dist/vtc/directory/card/show/0.1/payload.js +775 -0
  161. package/dist/vtc/directory/card/show/0.1/payload.js.map +1 -0
  162. package/dist/vtc/directory/card/update/0.1/payload.d.ts +1423 -0
  163. package/dist/vtc/directory/card/update/0.1/payload.d.ts.map +1 -0
  164. package/dist/vtc/directory/card/update/0.1/payload.js +845 -0
  165. package/dist/vtc/directory/card/update/0.1/payload.js.map +1 -0
  166. package/dist/vtc/directory/disclosure/0.1/payload.d.ts +951 -0
  167. package/dist/vtc/directory/disclosure/0.1/payload.d.ts.map +1 -0
  168. package/dist/vtc/directory/disclosure/0.1/payload.js +613 -0
  169. package/dist/vtc/directory/disclosure/0.1/payload.js.map +1 -0
  170. package/dist/vtc/directory/entries/list/0.1/payload.d.ts +5525 -0
  171. package/dist/vtc/directory/entries/list/0.1/payload.d.ts.map +1 -0
  172. package/dist/vtc/directory/entries/list/0.1/payload.js +656 -0
  173. package/dist/vtc/directory/entries/list/0.1/payload.js.map +1 -0
  174. package/dist/vtc/directory/entries/show/0.1/payload.d.ts +861 -0
  175. package/dist/vtc/directory/entries/show/0.1/payload.d.ts.map +1 -0
  176. package/dist/vtc/directory/entries/show/0.1/payload.js +502 -0
  177. package/dist/vtc/directory/entries/show/0.1/payload.js.map +1 -0
  178. package/dist/vtc/directory/export/0.1/payload.d.ts +346 -0
  179. package/dist/vtc/directory/export/0.1/payload.d.ts.map +1 -0
  180. package/dist/vtc/directory/export/0.1/payload.js +192 -0
  181. package/dist/vtc/directory/export/0.1/payload.js.map +1 -0
  182. package/dist/vtc/directory/fields/define/0.1/payload.d.ts +1355 -0
  183. package/dist/vtc/directory/fields/define/0.1/payload.d.ts.map +1 -0
  184. package/dist/vtc/directory/fields/define/0.1/payload.js +811 -0
  185. package/dist/vtc/directory/fields/define/0.1/payload.js.map +1 -0
  186. package/dist/vtc/directory/fields/list/0.1/payload.d.ts +1236 -0
  187. package/dist/vtc/directory/fields/list/0.1/payload.d.ts.map +1 -0
  188. package/dist/vtc/directory/fields/list/0.1/payload.js +739 -0
  189. package/dist/vtc/directory/fields/list/0.1/payload.js.map +1 -0
  190. package/dist/vtc/directory/fields/retire/0.1/payload.d.ts +1146 -0
  191. package/dist/vtc/directory/fields/retire/0.1/payload.d.ts.map +1 -0
  192. package/dist/vtc/directory/fields/retire/0.1/payload.js +684 -0
  193. package/dist/vtc/directory/fields/retire/0.1/payload.js.map +1 -0
  194. package/dist/vtc/directory/fields/update/0.1/payload.d.ts +1223 -0
  195. package/dist/vtc/directory/fields/update/0.1/payload.d.ts.map +1 -0
  196. package/dist/vtc/directory/fields/update/0.1/payload.js +715 -0
  197. package/dist/vtc/directory/fields/update/0.1/payload.js.map +1 -0
  198. package/dist/vtc/directory/images/get/0.1/payload.d.ts +484 -0
  199. package/dist/vtc/directory/images/get/0.1/payload.d.ts.map +1 -0
  200. package/dist/vtc/directory/images/get/0.1/payload.js +273 -0
  201. package/dist/vtc/directory/images/get/0.1/payload.js.map +1 -0
  202. package/dist/vtc/directory/images/upload/0.1/payload.d.ts +441 -0
  203. package/dist/vtc/directory/images/upload/0.1/payload.d.ts.map +1 -0
  204. package/dist/vtc/directory/images/upload/0.1/payload.js +262 -0
  205. package/dist/vtc/directory/images/upload/0.1/payload.js.map +1 -0
  206. package/dist/vtc/directory/introduce/0.1/payload.d.ts +417 -0
  207. package/dist/vtc/directory/introduce/0.1/payload.d.ts.map +1 -0
  208. package/dist/vtc/directory/introduce/0.1/payload.js +183 -0
  209. package/dist/vtc/directory/introduce/0.1/payload.js.map +1 -0
  210. package/dist/vtc/directory/introduction/0.1/payload.d.ts +423 -0
  211. package/dist/vtc/directory/introduction/0.1/payload.d.ts.map +1 -0
  212. package/dist/vtc/directory/introduction/0.1/payload.js +241 -0
  213. package/dist/vtc/directory/introduction/0.1/payload.js.map +1 -0
  214. package/dist/vtc/directory/notes/append/0.1/payload.d.ts +494 -0
  215. package/dist/vtc/directory/notes/append/0.1/payload.d.ts.map +1 -0
  216. package/dist/vtc/directory/notes/append/0.1/payload.js +281 -0
  217. package/dist/vtc/directory/notes/append/0.1/payload.js.map +1 -0
  218. package/dist/vtc/directory/notes/export/0.1/payload.d.ts +530 -0
  219. package/dist/vtc/directory/notes/export/0.1/payload.d.ts.map +1 -0
  220. package/dist/vtc/directory/notes/export/0.1/payload.js +294 -0
  221. package/dist/vtc/directory/notes/export/0.1/payload.js.map +1 -0
  222. package/dist/vtc/directory/notes/list/0.1/payload.d.ts +528 -0
  223. package/dist/vtc/directory/notes/list/0.1/payload.d.ts.map +1 -0
  224. package/dist/vtc/directory/notes/list/0.1/payload.js +294 -0
  225. package/dist/vtc/directory/notes/list/0.1/payload.js.map +1 -0
  226. package/dist/vtc/groups/_shared/0.1/group.d.ts +22 -0
  227. package/dist/vtc/groups/_shared/0.1/group.d.ts.map +1 -0
  228. package/dist/vtc/groups/_shared/0.1/group.js +6 -0
  229. package/dist/vtc/groups/_shared/0.1/group.js.map +1 -0
  230. package/dist/vtc/groups/bindings/add/0.1/payload.d.ts +914 -0
  231. package/dist/vtc/groups/bindings/add/0.1/payload.d.ts.map +1 -0
  232. package/dist/vtc/groups/bindings/add/0.1/payload.js +536 -0
  233. package/dist/vtc/groups/bindings/add/0.1/payload.js.map +1 -0
  234. package/dist/vtc/groups/bindings/list/0.1/payload.d.ts +910 -0
  235. package/dist/vtc/groups/bindings/list/0.1/payload.d.ts.map +1 -0
  236. package/dist/vtc/groups/bindings/list/0.1/payload.js +533 -0
  237. package/dist/vtc/groups/bindings/list/0.1/payload.js.map +1 -0
  238. package/dist/vtc/groups/bindings/remove/0.1/payload.d.ts +310 -0
  239. package/dist/vtc/groups/bindings/remove/0.1/payload.d.ts.map +1 -0
  240. package/dist/vtc/groups/bindings/remove/0.1/payload.js +182 -0
  241. package/dist/vtc/groups/bindings/remove/0.1/payload.js.map +1 -0
  242. package/dist/vtc/groups/create/0.1/payload.d.ts +1075 -0
  243. package/dist/vtc/groups/create/0.1/payload.d.ts.map +1 -0
  244. package/dist/vtc/groups/create/0.1/payload.js +631 -0
  245. package/dist/vtc/groups/create/0.1/payload.js.map +1 -0
  246. package/dist/vtc/groups/delete/0.1/payload.d.ts +317 -0
  247. package/dist/vtc/groups/delete/0.1/payload.d.ts.map +1 -0
  248. package/dist/vtc/groups/delete/0.1/payload.js +182 -0
  249. package/dist/vtc/groups/delete/0.1/payload.js.map +1 -0
  250. package/dist/vtc/groups/join/0.1/payload.d.ts +1262 -0
  251. package/dist/vtc/groups/join/0.1/payload.d.ts.map +1 -0
  252. package/dist/vtc/groups/join/0.1/payload.js +758 -0
  253. package/dist/vtc/groups/join/0.1/payload.js.map +1 -0
  254. package/dist/vtc/groups/leave/0.1/payload.d.ts +291 -0
  255. package/dist/vtc/groups/leave/0.1/payload.d.ts.map +1 -0
  256. package/dist/vtc/groups/leave/0.1/payload.js +179 -0
  257. package/dist/vtc/groups/leave/0.1/payload.js.map +1 -0
  258. package/dist/vtc/groups/list/0.1/payload.d.ts +1127 -0
  259. package/dist/vtc/groups/list/0.1/payload.d.ts.map +1 -0
  260. package/dist/vtc/groups/list/0.1/payload.js +674 -0
  261. package/dist/vtc/groups/list/0.1/payload.js.map +1 -0
  262. package/dist/vtc/groups/members/add/0.1/payload.d.ts +1014 -0
  263. package/dist/vtc/groups/members/add/0.1/payload.d.ts.map +1 -0
  264. package/dist/vtc/groups/members/add/0.1/payload.js +607 -0
  265. package/dist/vtc/groups/members/add/0.1/payload.js.map +1 -0
  266. package/dist/vtc/groups/members/list/0.1/payload.d.ts +1018 -0
  267. package/dist/vtc/groups/members/list/0.1/payload.d.ts.map +1 -0
  268. package/dist/vtc/groups/members/list/0.1/payload.js +606 -0
  269. package/dist/vtc/groups/members/list/0.1/payload.js.map +1 -0
  270. package/dist/vtc/groups/members/remove/0.1/payload.d.ts +351 -0
  271. package/dist/vtc/groups/members/remove/0.1/payload.d.ts.map +1 -0
  272. package/dist/vtc/groups/members/remove/0.1/payload.js +205 -0
  273. package/dist/vtc/groups/members/remove/0.1/payload.js.map +1 -0
  274. package/dist/vtc/groups/requests/decide/0.1/payload.d.ts +1236 -0
  275. package/dist/vtc/groups/requests/decide/0.1/payload.d.ts.map +1 -0
  276. package/dist/vtc/groups/requests/decide/0.1/payload.js +741 -0
  277. package/dist/vtc/groups/requests/decide/0.1/payload.js.map +1 -0
  278. package/dist/vtc/groups/requests/list/0.1/payload.d.ts +1063 -0
  279. package/dist/vtc/groups/requests/list/0.1/payload.d.ts.map +1 -0
  280. package/dist/vtc/groups/requests/list/0.1/payload.js +622 -0
  281. package/dist/vtc/groups/requests/list/0.1/payload.js.map +1 -0
  282. package/dist/vtc/groups/show/0.1/payload.d.ts +1012 -0
  283. package/dist/vtc/groups/show/0.1/payload.d.ts.map +1 -0
  284. package/dist/vtc/groups/show/0.1/payload.js +619 -0
  285. package/dist/vtc/groups/show/0.1/payload.js.map +1 -0
  286. package/dist/vtc/groups/update/0.1/payload.d.ts +1078 -0
  287. package/dist/vtc/groups/update/0.1/payload.d.ts.map +1 -0
  288. package/dist/vtc/groups/update/0.1/payload.js +633 -0
  289. package/dist/vtc/groups/update/0.1/payload.js.map +1 -0
  290. package/dist/vtc/join-requests/manifest/0.4/payload.d.ts +2303 -0
  291. package/dist/vtc/join-requests/manifest/0.4/payload.d.ts.map +1 -0
  292. package/dist/vtc/join-requests/manifest/0.4/payload.js +1293 -0
  293. package/dist/vtc/join-requests/manifest/0.4/payload.js.map +1 -0
  294. package/package.json +1 -1
  295. package/src/_shared/components.ts +912 -1
  296. package/src/auth/oob/_shared/0.1/oob.ts +1 -1
  297. package/src/auth/oob/grant/0.2/payload.ts +186 -0
  298. package/src/auth/oob/prove/0.2/payload.ts +523 -0
  299. package/src/auth/oob/respond/0.2/payload.ts +178 -0
  300. package/src/device/list/0.1/payload.ts +2 -0
  301. package/src/device/list/0.2/payload.ts +2 -0
  302. package/src/device/register/0.1/payload.ts +2 -0
  303. package/src/device/register/0.2/payload.ts +2 -0
  304. package/src/index.ts +61 -0
  305. package/src/keys/sign-document/0.1/payload.ts +437 -0
  306. package/src/persona/_shared/0.1/contact-annotations.ts +23 -0
  307. package/src/persona/contact/get/1.1/payload.ts +876 -0
  308. package/src/persona/contact/list/1.1/payload.ts +497 -0
  309. package/src/persona/contact/lists/delete/1.0/payload.ts +204 -0
  310. package/src/persona/contact/lists/list/1.0/payload.ts +332 -0
  311. package/src/persona/contact/lists/put/1.0/payload.ts +429 -0
  312. package/src/persona/contact/lists/show/1.0/payload.ts +305 -0
  313. package/src/persona/contact/put/1.1/payload.ts +958 -0
  314. package/src/rooms/keys/seal/0.1/payload.ts +12 -2
  315. package/src/rooms/keys/seal/0.2/payload.ts +12 -2
  316. package/src/rooms/owner/group/add/0.3/payload.ts +288 -0
  317. package/src/rooms/owner/group/remove/0.3/payload.ts +415 -0
  318. package/src/rooms/owner/group/renew/0.2/payload.ts +213 -0
  319. package/src/rooms/owner/register/0.2/payload.ts +415 -0
  320. package/src/rooms/records/get/0.1/payload.ts +12 -2
  321. package/src/rooms/records/get/0.2/payload.ts +12 -2
  322. package/src/rooms/records/put/0.1/payload.ts +12 -2
  323. package/src/rooms/records/put/0.2/payload.ts +12 -2
  324. package/src/vtc/admin/events/_shared/0.3/topic.ts +31 -0
  325. package/src/vtc/admin/events/event/0.3/payload.ts +136 -0
  326. package/src/vtc/admin/events/subscribe/0.3/payload.ts +314 -0
  327. package/src/vtc/directory/_shared/0.1/admin-note.ts +17 -0
  328. package/src/vtc/directory/_shared/0.1/directory-card.ts +23 -0
  329. package/src/vtc/directory/_shared/0.1/disclosure-statement.ts +19 -0
  330. package/src/vtc/directory/_shared/0.1/field-definition.ts +17 -0
  331. package/src/vtc/directory/card/assert/0.1/payload.ts +503 -0
  332. package/src/vtc/directory/card/present/0.1/payload.ts +437 -0
  333. package/src/vtc/directory/card/public/0.1/payload.ts +238 -0
  334. package/src/vtc/directory/card/publish/0.1/payload.ts +261 -0
  335. package/src/vtc/directory/card/show/0.1/payload.ts +812 -0
  336. package/src/vtc/directory/card/update/0.1/payload.ts +907 -0
  337. package/src/vtc/directory/disclosure/0.1/payload.ts +645 -0
  338. package/src/vtc/directory/entries/list/0.1/payload.ts +5676 -0
  339. package/src/vtc/directory/entries/show/0.1/payload.ts +541 -0
  340. package/src/vtc/directory/export/0.1/payload.ts +241 -0
  341. package/src/vtc/directory/fields/define/0.1/payload.ts +847 -0
  342. package/src/vtc/directory/fields/list/0.1/payload.ts +780 -0
  343. package/src/vtc/directory/fields/retire/0.1/payload.ts +723 -0
  344. package/src/vtc/directory/fields/update/0.1/payload.ts +767 -0
  345. package/src/vtc/directory/images/get/0.1/payload.ts +320 -0
  346. package/src/vtc/directory/images/upload/0.1/payload.ts +308 -0
  347. package/src/vtc/directory/introduce/0.1/payload.ts +324 -0
  348. package/src/vtc/directory/introduction/0.1/payload.ts +278 -0
  349. package/src/vtc/directory/notes/append/0.1/payload.ts +319 -0
  350. package/src/vtc/directory/notes/export/0.1/payload.ts +337 -0
  351. package/src/vtc/directory/notes/list/0.1/payload.ts +337 -0
  352. package/src/vtc/groups/_shared/0.1/group.ts +23 -0
  353. package/src/vtc/groups/bindings/add/0.1/payload.ts +573 -0
  354. package/src/vtc/groups/bindings/list/0.1/payload.ts +568 -0
  355. package/src/vtc/groups/bindings/remove/0.1/payload.ts +223 -0
  356. package/src/vtc/groups/create/0.1/payload.ts +683 -0
  357. package/src/vtc/groups/delete/0.1/payload.ts +224 -0
  358. package/src/vtc/groups/join/0.1/payload.ts +807 -0
  359. package/src/vtc/groups/leave/0.1/payload.ts +219 -0
  360. package/src/vtc/groups/list/0.1/payload.ts +728 -0
  361. package/src/vtc/groups/members/add/0.1/payload.ts +648 -0
  362. package/src/vtc/groups/members/list/0.1/payload.ts +647 -0
  363. package/src/vtc/groups/members/remove/0.1/payload.ts +251 -0
  364. package/src/vtc/groups/requests/decide/0.1/payload.ts +786 -0
  365. package/src/vtc/groups/requests/list/0.1/payload.ts +670 -0
  366. package/src/vtc/groups/show/0.1/payload.ts +652 -0
  367. package/src/vtc/groups/update/0.1/payload.ts +682 -0
  368. package/src/vtc/join-requests/manifest/0.4/payload.ts +1490 -0
@@ -0,0 +1,1444 @@
1
+ /**
2
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
3
+ * Source: specs/persona/contact/put/1.1/payload.schema.json
4
+ */
5
+ import type { ClaimType, ContactDocument, DirectoryEntryId, DirectoryRef, Ext, ListId, ListIds, Petname, ProofRung, Provenance, Ulid, ValueType } from "../../../../_shared/components.js";
6
+ /**
7
+ * File what a peer disclosed, or change the holder's own annotations on a contact, or both. Two forms. FILING (`subjectDid`, `knownByPersona`, `document`; no `contactId`) appends a revision, never overwrites, so a changed value is visible as a change rather than arriving silently — exactly as 1.0. ANNOTATING (`contactId`; no `subjectDid`, `knownByPersona`, `document` or `credentialRefs`) changes the holder's star, petname, lists, directory link or notes on an existing contact and appends no revision. In either form each annotation given replaces the stored one, each `removeX` removes one, and each annotation absent is unchanged. The outer document members are owned by the framework — SPEC §6.3.
8
+ */
9
+ export type PersonaContactPutPayload = {
10
+ contextId: string;
11
+ /**
12
+ * Annotating form only: the existing contact whose annotations change. A filing never names one — the agent keys a filing on (contextId, subjectDid, knownByPersona) as in 1.0.
13
+ */
14
+ contactId?: Ulid;
15
+ /**
16
+ * Filing form only. The DID the document is about, as disclosed. Normally pairwise, so it names this relationship and not the person across all of theirs.
17
+ */
18
+ subjectDid?: string;
19
+ /**
20
+ * Filing form only. Which of the holder's personas knows this contact. A contact belongs to the relationship, not to the holder at large — the same peer met through two personas is two contacts, and collapsing them would correlate the holder's own personas in their own address book.
21
+ */
22
+ knownByPersona?: string;
23
+ document?: ContactDocument;
24
+ /**
25
+ * Filing form only. Vault identifiers of credentials the peer presented alongside the document. The credentials themselves belong in the credential vault and the contact holds references.
26
+ *
27
+ * @maxItems 256
28
+ */
29
+ credentialRefs?: string[];
30
+ /**
31
+ * Star or unstar the contact. Absent: unchanged. A boolean rather than a remove member because `false` is a value the holder chose, not an absence.
32
+ */
33
+ starred?: boolean;
34
+ /**
35
+ * The holder's private name for the contact, replacing any they had. Absent: unchanged.
36
+ */
37
+ petname?: Petname;
38
+ /**
39
+ * Remove the petname. Only `true` is meaningful, so only `true` is accepted. A separate member rather than `petname: null`, because a nullable optional member makes "unchanged" and "remove" the same value in libraries that map both to one absent option.
40
+ */
41
+ removePetname?: true;
42
+ /**
43
+ * The lists the contact is on, replacing the whole set. Every identifier MUST name a list in this context. Absent: unchanged. Take the contact off every list with `removeLists`.
44
+ */
45
+ lists?: ListIds;
46
+ /**
47
+ * Take the contact off every list. Only `true` is accepted.
48
+ */
49
+ removeLists?: true;
50
+ /**
51
+ * Link the contact to a community directory entry, replacing any link it had. Absent: unchanged.
52
+ */
53
+ directoryRef?: DirectoryRef;
54
+ /**
55
+ * Remove the contact's directory link. Only `true` is accepted.
56
+ */
57
+ removeDirectoryRef?: true;
58
+ /**
59
+ * The holder's private note about this contact, replacing any they had. Absent: unchanged. Never disclosed to anyone, including the contact.
60
+ */
61
+ notes?: string;
62
+ /**
63
+ * Remove the note. Only `true` is accepted.
64
+ */
65
+ removeNotes?: true;
66
+ ext?: Ext;
67
+ } & {
68
+ [k: string]: unknown | undefined;
69
+ };
70
+ /**
71
+ * Success response to persona/contact/put. Type https://trusttasks.org/spec/persona/contact/put/1.1#response. Identifiers, the current revision and what changed; no claim value and no annotation text is echoed.
72
+ */
73
+ export interface PersonaContactPutResponsePayload {
74
+ contactId: Ulid;
75
+ /**
76
+ * The contact's current revision: the one a filing just appended, or, for an annotating request, the revision that was already current. Annotations never move it.
77
+ */
78
+ rev: number;
79
+ /**
80
+ * True when this is the first revision for the subject. Always false for an annotating request.
81
+ */
82
+ created: boolean;
83
+ /**
84
+ * True when any annotation now differs from what was stored. False when every annotation given already matched and every one named for removal was already absent — including a filing that named none.
85
+ */
86
+ annotationsChanged: boolean;
87
+ /**
88
+ * Claim types whose value differs from the previous revision. Present only on a filing that updated an existing contact.
89
+ *
90
+ * @maxItems 256
91
+ */
92
+ changedClaims?: ClaimType[];
93
+ ext?: Ext;
94
+ }
95
+ /** Shared definitions this specification references, re-exported under the names it used to declare them with. */
96
+ export type { ClaimType, ContactDocument, DirectoryEntryId, DirectoryRef, Ext, ListId, ListIds, Petname, ProofRung, Provenance, Ulid, ValueType };
97
+ /** Trust Task type URI. */
98
+ export declare const TYPE_URI: "https://trusttasks.org/spec/persona/contact/put/1.1";
99
+ /** Stable alias for this specification's request payload shape. */
100
+ export type Payload = PersonaContactPutPayload;
101
+ /** Trust Task response type URI (request type URI + "#response"). */
102
+ export declare const RESPONSE_TYPE_URI: "https://trusttasks.org/spec/persona/contact/put/1.1#response";
103
+ /** Stable alias for this specification's success-response payload shape. */
104
+ export type Response = PersonaContactPutResponsePayload;
105
+ /**
106
+ * This specification's payload schema, as a value.
107
+ *
108
+ * SPEC.md §7.2 item 2 is performed against this. It is shipped as data
109
+ * rather than only as a `.json` file because TypeScript types are erased
110
+ * at runtime: without a schema a consumer has nothing to validate, and
111
+ * every REQUIRED payload member is optional in practice. Cross-file
112
+ * `$ref`s are already inlined, so it needs no resolver.
113
+ */
114
+ export declare const PAYLOAD_SCHEMA: {
115
+ readonly $schema: "https://json-schema.org/draft/2020-12/schema";
116
+ readonly $id: "https://trusttasks.org/spec/persona/contact/put/1.1";
117
+ readonly title: "Persona Contact Put — payload";
118
+ readonly description: "File what a peer disclosed, or change the holder's own annotations on a contact, or both. Two forms. FILING (`subjectDid`, `knownByPersona`, `document`; no `contactId`) appends a revision, never overwrites, so a changed value is visible as a change rather than arriving silently — exactly as 1.0. ANNOTATING (`contactId`; no `subjectDid`, `knownByPersona`, `document` or `credentialRefs`) changes the holder's star, petname, lists, directory link or notes on an existing contact and appends no revision. In either form each annotation given replaces the stored one, each `removeX` removes one, and each annotation absent is unchanged. The outer document members are owned by the framework — SPEC §6.3.";
119
+ readonly type: "object";
120
+ readonly additionalProperties: false;
121
+ readonly required: readonly ["contextId"];
122
+ readonly oneOf: readonly [{
123
+ readonly required: readonly ["subjectDid", "knownByPersona", "document"];
124
+ readonly not: {
125
+ readonly required: readonly ["contactId"];
126
+ };
127
+ }, {
128
+ readonly required: readonly ["contactId"];
129
+ readonly not: {
130
+ readonly anyOf: readonly [{
131
+ readonly required: readonly ["subjectDid"];
132
+ }, {
133
+ readonly required: readonly ["knownByPersona"];
134
+ }, {
135
+ readonly required: readonly ["document"];
136
+ }, {
137
+ readonly required: readonly ["credentialRefs"];
138
+ }];
139
+ };
140
+ readonly anyOf: readonly [{
141
+ readonly required: readonly ["starred"];
142
+ }, {
143
+ readonly required: readonly ["petname"];
144
+ }, {
145
+ readonly required: readonly ["removePetname"];
146
+ }, {
147
+ readonly required: readonly ["lists"];
148
+ }, {
149
+ readonly required: readonly ["removeLists"];
150
+ }, {
151
+ readonly required: readonly ["directoryRef"];
152
+ }, {
153
+ readonly required: readonly ["removeDirectoryRef"];
154
+ }, {
155
+ readonly required: readonly ["notes"];
156
+ }, {
157
+ readonly required: readonly ["removeNotes"];
158
+ }];
159
+ }];
160
+ readonly dependentSchemas: {
161
+ readonly removePetname: {
162
+ readonly not: {
163
+ readonly required: readonly ["petname"];
164
+ };
165
+ };
166
+ readonly removeLists: {
167
+ readonly not: {
168
+ readonly required: readonly ["lists"];
169
+ };
170
+ };
171
+ readonly removeDirectoryRef: {
172
+ readonly not: {
173
+ readonly required: readonly ["directoryRef"];
174
+ };
175
+ };
176
+ readonly removeNotes: {
177
+ readonly not: {
178
+ readonly required: readonly ["notes"];
179
+ };
180
+ };
181
+ };
182
+ readonly properties: {
183
+ readonly contextId: {
184
+ readonly type: "string";
185
+ readonly minLength: 1;
186
+ };
187
+ readonly contactId: {
188
+ readonly $ref: "#/$defs/Ulid";
189
+ readonly description: "Annotating form only: the existing contact whose annotations change. A filing never names one — the agent keys a filing on (contextId, subjectDid, knownByPersona) as in 1.0.";
190
+ };
191
+ readonly subjectDid: {
192
+ readonly type: "string";
193
+ readonly minLength: 1;
194
+ readonly maxLength: 2048;
195
+ readonly description: "Filing form only. The DID the document is about, as disclosed. Normally pairwise, so it names this relationship and not the person across all of theirs.";
196
+ };
197
+ readonly knownByPersona: {
198
+ readonly type: "string";
199
+ readonly minLength: 1;
200
+ readonly maxLength: 2048;
201
+ readonly description: "Filing form only. Which of the holder's personas knows this contact. A contact belongs to the relationship, not to the holder at large — the same peer met through two personas is two contacts, and collapsing them would correlate the holder's own personas in their own address book.";
202
+ };
203
+ readonly document: {
204
+ readonly $ref: "#/$defs/ContactDocument";
205
+ };
206
+ readonly credentialRefs: {
207
+ readonly type: "array";
208
+ readonly maxItems: 256;
209
+ readonly items: {
210
+ readonly type: "string";
211
+ readonly minLength: 1;
212
+ };
213
+ readonly description: "Filing form only. Vault identifiers of credentials the peer presented alongside the document. The credentials themselves belong in the credential vault and the contact holds references.";
214
+ };
215
+ readonly starred: {
216
+ readonly type: "boolean";
217
+ readonly description: "Star or unstar the contact. Absent: unchanged. A boolean rather than a remove member because `false` is a value the holder chose, not an absence.";
218
+ };
219
+ readonly petname: {
220
+ readonly $ref: "#/$defs/Petname";
221
+ readonly description: "The holder's private name for the contact, replacing any they had. Absent: unchanged.";
222
+ };
223
+ readonly removePetname: {
224
+ readonly type: "boolean";
225
+ readonly const: true;
226
+ readonly description: "Remove the petname. Only `true` is meaningful, so only `true` is accepted. A separate member rather than `petname: null`, because a nullable optional member makes \"unchanged\" and \"remove\" the same value in libraries that map both to one absent option.";
227
+ };
228
+ readonly lists: {
229
+ readonly $ref: "#/$defs/ListIds";
230
+ readonly description: "The lists the contact is on, replacing the whole set. Every identifier MUST name a list in this context. Absent: unchanged. Take the contact off every list with `removeLists`.";
231
+ };
232
+ readonly removeLists: {
233
+ readonly type: "boolean";
234
+ readonly const: true;
235
+ readonly description: "Take the contact off every list. Only `true` is accepted.";
236
+ };
237
+ readonly directoryRef: {
238
+ readonly $ref: "#/$defs/DirectoryRef";
239
+ readonly description: "Link the contact to a community directory entry, replacing any link it had. Absent: unchanged.";
240
+ };
241
+ readonly removeDirectoryRef: {
242
+ readonly type: "boolean";
243
+ readonly const: true;
244
+ readonly description: "Remove the contact's directory link. Only `true` is accepted.";
245
+ };
246
+ readonly notes: {
247
+ readonly type: "string";
248
+ readonly minLength: 1;
249
+ readonly maxLength: 4096;
250
+ readonly description: "The holder's private note about this contact, replacing any they had. Absent: unchanged. Never disclosed to anyone, including the contact.";
251
+ };
252
+ readonly removeNotes: {
253
+ readonly type: "boolean";
254
+ readonly const: true;
255
+ readonly description: "Remove the note. Only `true` is accepted.";
256
+ };
257
+ readonly ext: {
258
+ readonly $ref: "#/$defs/Ext";
259
+ };
260
+ };
261
+ readonly $defs: {
262
+ readonly Response: {
263
+ readonly $anchor: "response";
264
+ readonly title: "Persona Contact Put — response payload";
265
+ readonly description: "Success response to persona/contact/put. Type https://trusttasks.org/spec/persona/contact/put/1.1#response. Identifiers, the current revision and what changed; no claim value and no annotation text is echoed.";
266
+ readonly type: "object";
267
+ readonly additionalProperties: false;
268
+ readonly required: readonly ["contactId", "rev", "created", "annotationsChanged"];
269
+ readonly properties: {
270
+ readonly contactId: {
271
+ readonly $ref: "#/$defs/Ulid";
272
+ };
273
+ readonly rev: {
274
+ readonly type: "integer";
275
+ readonly minimum: 1;
276
+ readonly description: "The contact's current revision: the one a filing just appended, or, for an annotating request, the revision that was already current. Annotations never move it.";
277
+ };
278
+ readonly created: {
279
+ readonly type: "boolean";
280
+ readonly description: "True when this is the first revision for the subject. Always false for an annotating request.";
281
+ };
282
+ readonly annotationsChanged: {
283
+ readonly type: "boolean";
284
+ readonly description: "True when any annotation now differs from what was stored. False when every annotation given already matched and every one named for removal was already absent — including a filing that named none.";
285
+ };
286
+ readonly changedClaims: {
287
+ readonly type: "array";
288
+ readonly maxItems: 256;
289
+ readonly items: {
290
+ readonly $ref: "#/$defs/ClaimType";
291
+ };
292
+ readonly description: "Claim types whose value differs from the previous revision. Present only on a filing that updated an existing contact.";
293
+ };
294
+ readonly ext: {
295
+ readonly $ref: "#/$defs/Ext";
296
+ };
297
+ };
298
+ };
299
+ readonly Ext: {
300
+ readonly title: "Ext";
301
+ 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.";
302
+ readonly type: "object";
303
+ readonly minProperties: 1;
304
+ readonly additionalProperties: true;
305
+ readonly propertyNames: {
306
+ readonly pattern: "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$";
307
+ };
308
+ };
309
+ readonly ClaimType: {
310
+ readonly title: "ClaimType";
311
+ 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.";
312
+ readonly type: "string";
313
+ readonly minLength: 1;
314
+ readonly maxLength: 128;
315
+ readonly pattern: "^(x:)?[a-z][a-zA-Z0-9]*(\\.[a-z][a-zA-Z0-9]*)*$";
316
+ };
317
+ readonly Ulid: {
318
+ readonly title: "Ulid";
319
+ 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.";
320
+ readonly type: "string";
321
+ readonly pattern: "^[0-9A-HJKMNP-TV-Z]{26}$";
322
+ };
323
+ readonly DirectoryRef: {
324
+ readonly title: "DirectoryRef";
325
+ readonly description: "Links a contact to the entry in a community's member directory it corresponds to, so the holder's own client can join that community's directory with the holder's address book — showing a star or a petname beside an entry — without either side telling the other. The community never learns the link exists; the contact never learns it either. A contact has at most one.";
326
+ readonly type: "object";
327
+ readonly additionalProperties: false;
328
+ readonly required: readonly ["vtcDid", "entryId"];
329
+ readonly properties: {
330
+ readonly vtcDid: {
331
+ readonly type: "string";
332
+ readonly minLength: 1;
333
+ readonly maxLength: 2048;
334
+ readonly pattern: "^did:[a-z0-9]+:";
335
+ readonly description: "The DID of the community whose directory holds the entry.";
336
+ };
337
+ readonly entryId: {
338
+ readonly $ref: "#/$defs/DirectoryEntryId";
339
+ readonly description: "The entry, as that community's directory identifies it.";
340
+ };
341
+ };
342
+ };
343
+ readonly DirectoryEntryId: {
344
+ readonly title: "DirectoryEntryId";
345
+ readonly description: "A community directory entry's identifier, exactly as that community's directory returned it. Opaque and community-scoped: the agent stores and compares it as a string, never parses it, and never treats the same value under two communities as the same entry.";
346
+ readonly type: "string";
347
+ readonly minLength: 1;
348
+ readonly maxLength: 128;
349
+ readonly pattern: "^[A-Za-z0-9_-]+$";
350
+ };
351
+ readonly ListIds: {
352
+ readonly title: "ListIds";
353
+ readonly description: "The lists a contact is on, as a set: order carries no meaning. A contact on no list has no `lists` member, never an empty array, so there is one way to say \"none\".";
354
+ readonly type: "array";
355
+ readonly minItems: 1;
356
+ readonly maxItems: 64;
357
+ readonly uniqueItems: true;
358
+ readonly items: {
359
+ readonly $ref: "#/$defs/ListId";
360
+ };
361
+ };
362
+ readonly ListId: {
363
+ readonly title: "ListId";
364
+ readonly description: "Identifier of one of the holder's contact lists: a ULID in Crockford base32, uppercase, assigned by the agent when the list is created. Meaningful only inside the context that holds the list; it is never sent to anyone but the holder's own clients.";
365
+ readonly type: "string";
366
+ readonly pattern: "^[0-9A-HJKMNP-TV-Z]{26}$";
367
+ };
368
+ readonly Petname: {
369
+ readonly title: "Petname";
370
+ readonly description: "The holder's private name for a contact, on one line: no control characters, line breaks included. A petname in Zooko's sense — chosen by the holder, meaningful to the holder, and unforgeable by anyone else, because nobody else can write it. Distinct from the contact's own disclosed `nickname` or display name, which the contact chose and may change. Compared exactly, as a string: an agent does not case-fold or normalise it.";
371
+ readonly type: "string";
372
+ readonly minLength: 1;
373
+ readonly maxLength: 64;
374
+ readonly pattern: "^[^\\u0000-\\u001F\\u007F]+$";
375
+ };
376
+ readonly ContactDocument: {
377
+ readonly title: "ContactDocument";
378
+ readonly description: "What a peer disclosed, as received. Structurally the same claim set a holder composes and presents — a profile and a contact card are one schema seen from two sides — which is why a maintainer validates both with the same code and a consumer renders both with the same view.";
379
+ readonly type: "object";
380
+ readonly additionalProperties: false;
381
+ readonly required: readonly ["claims"];
382
+ readonly properties: {
383
+ readonly publisher: {
384
+ readonly type: "string";
385
+ readonly maxLength: 2048;
386
+ readonly description: "The DID that published the document, as it appeared. Normally a pairwise identifier, so it names the relationship rather than the person.";
387
+ };
388
+ readonly cardVersion: {
389
+ readonly type: "integer";
390
+ readonly minimum: 1;
391
+ readonly description: "The publisher's own monotonic counter, if they supplied one. Advisory: it orders the publisher's revisions relative to each other and MUST NOT be trusted to order them against anything else.";
392
+ };
393
+ readonly claims: {
394
+ readonly type: "array";
395
+ readonly maxItems: 256;
396
+ readonly items: {
397
+ readonly type: "object";
398
+ readonly additionalProperties: false;
399
+ readonly required: readonly ["type", "valueType", "value"];
400
+ readonly properties: {
401
+ readonly type: {
402
+ readonly $ref: "#/$defs/ClaimType";
403
+ };
404
+ readonly valueType: {
405
+ readonly $ref: "#/$defs/ValueType";
406
+ };
407
+ readonly value: {};
408
+ readonly provenance: {
409
+ readonly $ref: "#/$defs/Provenance";
410
+ readonly description: "As asserted by the publisher. A recipient MUST NOT treat a claimed credentialBacked provenance as verified — it is a statement about what the publisher says backs the claim, and verification is a separate act against the credential itself.";
411
+ };
412
+ };
413
+ };
414
+ };
415
+ };
416
+ };
417
+ readonly Provenance: {
418
+ readonly title: "Provenance";
419
+ readonly description: "Where a value comes from, and the member that makes this family worth building on a trust stack rather than in an address book. It survives to the verifier, so a recipient can tell — per field — what the holder typed from what an issuer attested.\n\n`selfAsserted` — the holder supplied it.\n\n`credentialBacked` — the value is derived from a credential in the vault at `claimPath`. The stored value is a CACHE FOR DISPLAY; the credential is the truth. A maintainer MUST re-derive it on read and MUST fail closed (never presenting a stale value) when the credential has been revoked, has expired, or has been archived or deleted.\n\n`generated` — the value is minted per verifier at disclosure time and recorded against that verifier, so every relying party receives a different one that routes back to the holder. This is the shape of the most widely adopted consumer privacy feature in this space; a maintainer need not operate a relay to conform, but the shape must exist, because retrofitting per-verifier values into a pool-of-values model is a migration rather than an addition.\n\n`derived` — the value was taken from a source the holder connected or supplied — a code-hosting profile, an uploaded CV — rather than typed by them or attested by an issuer. Nobody signed it: it is the holder's claim that the source said so, and a consumer MUST NOT present it as attested. It exists as its own kind because a derived value is neither of the others — the holder did not author it, and no one vouches for it — and a holder deciding whether to disclose deserves to know which of their values they typed.\n\nFor how strongly a disclosed value identifies the holder, the kinds rank `credentialBacked` above `derived` above `selfAsserted`; `generated` values are per-verifier and do not correlate.";
420
+ readonly type: "object";
421
+ readonly required: readonly ["kind"];
422
+ readonly oneOf: readonly [{
423
+ readonly additionalProperties: false;
424
+ readonly required: readonly ["kind"];
425
+ readonly properties: {
426
+ readonly kind: {
427
+ readonly const: "selfAsserted";
428
+ };
429
+ };
430
+ }, {
431
+ readonly additionalProperties: false;
432
+ readonly required: readonly ["kind", "credentialId", "claimPath"];
433
+ readonly properties: {
434
+ readonly kind: {
435
+ readonly const: "credentialBacked";
436
+ };
437
+ readonly credentialId: {
438
+ readonly type: "string";
439
+ readonly minLength: 1;
440
+ readonly description: "Vault identifier of the backing credential.";
441
+ };
442
+ readonly claimPath: {
443
+ readonly type: "string";
444
+ readonly pattern: "^(/[^/~]*(~[01][^/~]*)*)*$";
445
+ readonly description: "RFC 6901 JSON Pointer to the claim within the credential, e.g. `/credentialSubject/familyName`.";
446
+ };
447
+ readonly issuerDid: {
448
+ readonly type: "string";
449
+ readonly minLength: 1;
450
+ readonly description: "Issuer of the backing credential. Advisory: a consumer MUST verify the credential rather than trusting this member.";
451
+ };
452
+ readonly proof: {
453
+ readonly $ref: "#/$defs/ProofRung";
454
+ readonly description: "The disclosure rung this claim was, or will be, presented at.";
455
+ };
456
+ };
457
+ }, {
458
+ readonly additionalProperties: false;
459
+ readonly required: readonly ["kind", "generator"];
460
+ readonly properties: {
461
+ readonly kind: {
462
+ readonly const: "generated";
463
+ };
464
+ readonly generator: {
465
+ readonly type: "string";
466
+ readonly minLength: 1;
467
+ readonly maxLength: 64;
468
+ readonly description: "Names the minting scheme, e.g. `relayEmail`. Maintainer-defined.";
469
+ };
470
+ readonly perVerifier: {
471
+ readonly type: "boolean";
472
+ readonly default: true;
473
+ readonly description: "When true (the default and the only useful setting), a distinct value is minted for each verifier.";
474
+ };
475
+ };
476
+ }, {
477
+ readonly additionalProperties: false;
478
+ readonly required: readonly ["kind", "source", "derivedAt"];
479
+ readonly properties: {
480
+ readonly kind: {
481
+ readonly const: "derived";
482
+ };
483
+ readonly source: {
484
+ readonly type: "string";
485
+ readonly minLength: 1;
486
+ readonly maxLength: 64;
487
+ readonly pattern: "^[a-z][A-Za-z0-9.-]*$";
488
+ readonly description: "The KIND of source the value was taken from — `github`, `cvUpload`, `linkedIn` — never an account, handle or URL. Provenance survives to the verifier, so this member is disclosed with the claim; a handle here would disclose an identifier the holder never chose to share.";
489
+ };
490
+ readonly derivedAt: {
491
+ readonly type: "string";
492
+ readonly format: "date-time";
493
+ readonly description: "When the value was taken from the source. A derived value is a snapshot: the source may have changed since, and nothing re-derives it.";
494
+ };
495
+ };
496
+ }];
497
+ };
498
+ readonly ProofRung: {
499
+ readonly title: "ProofRung";
500
+ 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.";
501
+ readonly type: "string";
502
+ readonly enum: readonly ["predicate", "derived", "selectiveDisclosure", "whole"];
503
+ };
504
+ readonly ValueType: {
505
+ readonly title: "ValueType";
506
+ 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.";
507
+ readonly type: "string";
508
+ readonly enum: readonly ["string", "number", "boolean", "date", "object"];
509
+ };
510
+ };
511
+ };
512
+ /** As {@link PAYLOAD_SCHEMA}, for the success-response variant. */
513
+ export declare const RESPONSE_PAYLOAD_SCHEMA: {
514
+ readonly $schema: "https://json-schema.org/draft/2020-12/schema";
515
+ readonly $ref: "#/$defs/Response";
516
+ readonly $defs: {
517
+ readonly Response: {
518
+ readonly $anchor: "response";
519
+ readonly title: "Persona Contact Put — response payload";
520
+ readonly description: "Success response to persona/contact/put. Type https://trusttasks.org/spec/persona/contact/put/1.1#response. Identifiers, the current revision and what changed; no claim value and no annotation text is echoed.";
521
+ readonly type: "object";
522
+ readonly additionalProperties: false;
523
+ readonly required: readonly ["contactId", "rev", "created", "annotationsChanged"];
524
+ readonly properties: {
525
+ readonly contactId: {
526
+ readonly $ref: "#/$defs/Ulid";
527
+ };
528
+ readonly rev: {
529
+ readonly type: "integer";
530
+ readonly minimum: 1;
531
+ readonly description: "The contact's current revision: the one a filing just appended, or, for an annotating request, the revision that was already current. Annotations never move it.";
532
+ };
533
+ readonly created: {
534
+ readonly type: "boolean";
535
+ readonly description: "True when this is the first revision for the subject. Always false for an annotating request.";
536
+ };
537
+ readonly annotationsChanged: {
538
+ readonly type: "boolean";
539
+ readonly description: "True when any annotation now differs from what was stored. False when every annotation given already matched and every one named for removal was already absent — including a filing that named none.";
540
+ };
541
+ readonly changedClaims: {
542
+ readonly type: "array";
543
+ readonly maxItems: 256;
544
+ readonly items: {
545
+ readonly $ref: "#/$defs/ClaimType";
546
+ };
547
+ readonly description: "Claim types whose value differs from the previous revision. Present only on a filing that updated an existing contact.";
548
+ };
549
+ readonly ext: {
550
+ readonly $ref: "#/$defs/Ext";
551
+ };
552
+ };
553
+ };
554
+ readonly Ext: {
555
+ readonly title: "Ext";
556
+ 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.";
557
+ readonly type: "object";
558
+ readonly minProperties: 1;
559
+ readonly additionalProperties: true;
560
+ readonly propertyNames: {
561
+ readonly pattern: "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$";
562
+ };
563
+ };
564
+ readonly ClaimType: {
565
+ readonly title: "ClaimType";
566
+ 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.";
567
+ readonly type: "string";
568
+ readonly minLength: 1;
569
+ readonly maxLength: 128;
570
+ readonly pattern: "^(x:)?[a-z][a-zA-Z0-9]*(\\.[a-z][a-zA-Z0-9]*)*$";
571
+ };
572
+ readonly Ulid: {
573
+ readonly title: "Ulid";
574
+ 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.";
575
+ readonly type: "string";
576
+ readonly pattern: "^[0-9A-HJKMNP-TV-Z]{26}$";
577
+ };
578
+ readonly DirectoryRef: {
579
+ readonly title: "DirectoryRef";
580
+ readonly description: "Links a contact to the entry in a community's member directory it corresponds to, so the holder's own client can join that community's directory with the holder's address book — showing a star or a petname beside an entry — without either side telling the other. The community never learns the link exists; the contact never learns it either. A contact has at most one.";
581
+ readonly type: "object";
582
+ readonly additionalProperties: false;
583
+ readonly required: readonly ["vtcDid", "entryId"];
584
+ readonly properties: {
585
+ readonly vtcDid: {
586
+ readonly type: "string";
587
+ readonly minLength: 1;
588
+ readonly maxLength: 2048;
589
+ readonly pattern: "^did:[a-z0-9]+:";
590
+ readonly description: "The DID of the community whose directory holds the entry.";
591
+ };
592
+ readonly entryId: {
593
+ readonly $ref: "#/$defs/DirectoryEntryId";
594
+ readonly description: "The entry, as that community's directory identifies it.";
595
+ };
596
+ };
597
+ };
598
+ readonly DirectoryEntryId: {
599
+ readonly title: "DirectoryEntryId";
600
+ readonly description: "A community directory entry's identifier, exactly as that community's directory returned it. Opaque and community-scoped: the agent stores and compares it as a string, never parses it, and never treats the same value under two communities as the same entry.";
601
+ readonly type: "string";
602
+ readonly minLength: 1;
603
+ readonly maxLength: 128;
604
+ readonly pattern: "^[A-Za-z0-9_-]+$";
605
+ };
606
+ readonly ListIds: {
607
+ readonly title: "ListIds";
608
+ readonly description: "The lists a contact is on, as a set: order carries no meaning. A contact on no list has no `lists` member, never an empty array, so there is one way to say \"none\".";
609
+ readonly type: "array";
610
+ readonly minItems: 1;
611
+ readonly maxItems: 64;
612
+ readonly uniqueItems: true;
613
+ readonly items: {
614
+ readonly $ref: "#/$defs/ListId";
615
+ };
616
+ };
617
+ readonly ListId: {
618
+ readonly title: "ListId";
619
+ readonly description: "Identifier of one of the holder's contact lists: a ULID in Crockford base32, uppercase, assigned by the agent when the list is created. Meaningful only inside the context that holds the list; it is never sent to anyone but the holder's own clients.";
620
+ readonly type: "string";
621
+ readonly pattern: "^[0-9A-HJKMNP-TV-Z]{26}$";
622
+ };
623
+ readonly Petname: {
624
+ readonly title: "Petname";
625
+ readonly description: "The holder's private name for a contact, on one line: no control characters, line breaks included. A petname in Zooko's sense — chosen by the holder, meaningful to the holder, and unforgeable by anyone else, because nobody else can write it. Distinct from the contact's own disclosed `nickname` or display name, which the contact chose and may change. Compared exactly, as a string: an agent does not case-fold or normalise it.";
626
+ readonly type: "string";
627
+ readonly minLength: 1;
628
+ readonly maxLength: 64;
629
+ readonly pattern: "^[^\\u0000-\\u001F\\u007F]+$";
630
+ };
631
+ readonly ContactDocument: {
632
+ readonly title: "ContactDocument";
633
+ readonly description: "What a peer disclosed, as received. Structurally the same claim set a holder composes and presents — a profile and a contact card are one schema seen from two sides — which is why a maintainer validates both with the same code and a consumer renders both with the same view.";
634
+ readonly type: "object";
635
+ readonly additionalProperties: false;
636
+ readonly required: readonly ["claims"];
637
+ readonly properties: {
638
+ readonly publisher: {
639
+ readonly type: "string";
640
+ readonly maxLength: 2048;
641
+ readonly description: "The DID that published the document, as it appeared. Normally a pairwise identifier, so it names the relationship rather than the person.";
642
+ };
643
+ readonly cardVersion: {
644
+ readonly type: "integer";
645
+ readonly minimum: 1;
646
+ readonly description: "The publisher's own monotonic counter, if they supplied one. Advisory: it orders the publisher's revisions relative to each other and MUST NOT be trusted to order them against anything else.";
647
+ };
648
+ readonly claims: {
649
+ readonly type: "array";
650
+ readonly maxItems: 256;
651
+ readonly items: {
652
+ readonly type: "object";
653
+ readonly additionalProperties: false;
654
+ readonly required: readonly ["type", "valueType", "value"];
655
+ readonly properties: {
656
+ readonly type: {
657
+ readonly $ref: "#/$defs/ClaimType";
658
+ };
659
+ readonly valueType: {
660
+ readonly $ref: "#/$defs/ValueType";
661
+ };
662
+ readonly value: {};
663
+ readonly provenance: {
664
+ readonly $ref: "#/$defs/Provenance";
665
+ readonly description: "As asserted by the publisher. A recipient MUST NOT treat a claimed credentialBacked provenance as verified — it is a statement about what the publisher says backs the claim, and verification is a separate act against the credential itself.";
666
+ };
667
+ };
668
+ };
669
+ };
670
+ };
671
+ };
672
+ readonly Provenance: {
673
+ readonly title: "Provenance";
674
+ readonly description: "Where a value comes from, and the member that makes this family worth building on a trust stack rather than in an address book. It survives to the verifier, so a recipient can tell — per field — what the holder typed from what an issuer attested.\n\n`selfAsserted` — the holder supplied it.\n\n`credentialBacked` — the value is derived from a credential in the vault at `claimPath`. The stored value is a CACHE FOR DISPLAY; the credential is the truth. A maintainer MUST re-derive it on read and MUST fail closed (never presenting a stale value) when the credential has been revoked, has expired, or has been archived or deleted.\n\n`generated` — the value is minted per verifier at disclosure time and recorded against that verifier, so every relying party receives a different one that routes back to the holder. This is the shape of the most widely adopted consumer privacy feature in this space; a maintainer need not operate a relay to conform, but the shape must exist, because retrofitting per-verifier values into a pool-of-values model is a migration rather than an addition.\n\n`derived` — the value was taken from a source the holder connected or supplied — a code-hosting profile, an uploaded CV — rather than typed by them or attested by an issuer. Nobody signed it: it is the holder's claim that the source said so, and a consumer MUST NOT present it as attested. It exists as its own kind because a derived value is neither of the others — the holder did not author it, and no one vouches for it — and a holder deciding whether to disclose deserves to know which of their values they typed.\n\nFor how strongly a disclosed value identifies the holder, the kinds rank `credentialBacked` above `derived` above `selfAsserted`; `generated` values are per-verifier and do not correlate.";
675
+ readonly type: "object";
676
+ readonly required: readonly ["kind"];
677
+ readonly oneOf: readonly [{
678
+ readonly additionalProperties: false;
679
+ readonly required: readonly ["kind"];
680
+ readonly properties: {
681
+ readonly kind: {
682
+ readonly const: "selfAsserted";
683
+ };
684
+ };
685
+ }, {
686
+ readonly additionalProperties: false;
687
+ readonly required: readonly ["kind", "credentialId", "claimPath"];
688
+ readonly properties: {
689
+ readonly kind: {
690
+ readonly const: "credentialBacked";
691
+ };
692
+ readonly credentialId: {
693
+ readonly type: "string";
694
+ readonly minLength: 1;
695
+ readonly description: "Vault identifier of the backing credential.";
696
+ };
697
+ readonly claimPath: {
698
+ readonly type: "string";
699
+ readonly pattern: "^(/[^/~]*(~[01][^/~]*)*)*$";
700
+ readonly description: "RFC 6901 JSON Pointer to the claim within the credential, e.g. `/credentialSubject/familyName`.";
701
+ };
702
+ readonly issuerDid: {
703
+ readonly type: "string";
704
+ readonly minLength: 1;
705
+ readonly description: "Issuer of the backing credential. Advisory: a consumer MUST verify the credential rather than trusting this member.";
706
+ };
707
+ readonly proof: {
708
+ readonly $ref: "#/$defs/ProofRung";
709
+ readonly description: "The disclosure rung this claim was, or will be, presented at.";
710
+ };
711
+ };
712
+ }, {
713
+ readonly additionalProperties: false;
714
+ readonly required: readonly ["kind", "generator"];
715
+ readonly properties: {
716
+ readonly kind: {
717
+ readonly const: "generated";
718
+ };
719
+ readonly generator: {
720
+ readonly type: "string";
721
+ readonly minLength: 1;
722
+ readonly maxLength: 64;
723
+ readonly description: "Names the minting scheme, e.g. `relayEmail`. Maintainer-defined.";
724
+ };
725
+ readonly perVerifier: {
726
+ readonly type: "boolean";
727
+ readonly default: true;
728
+ readonly description: "When true (the default and the only useful setting), a distinct value is minted for each verifier.";
729
+ };
730
+ };
731
+ }, {
732
+ readonly additionalProperties: false;
733
+ readonly required: readonly ["kind", "source", "derivedAt"];
734
+ readonly properties: {
735
+ readonly kind: {
736
+ readonly const: "derived";
737
+ };
738
+ readonly source: {
739
+ readonly type: "string";
740
+ readonly minLength: 1;
741
+ readonly maxLength: 64;
742
+ readonly pattern: "^[a-z][A-Za-z0-9.-]*$";
743
+ readonly description: "The KIND of source the value was taken from — `github`, `cvUpload`, `linkedIn` — never an account, handle or URL. Provenance survives to the verifier, so this member is disclosed with the claim; a handle here would disclose an identifier the holder never chose to share.";
744
+ };
745
+ readonly derivedAt: {
746
+ readonly type: "string";
747
+ readonly format: "date-time";
748
+ readonly description: "When the value was taken from the source. A derived value is a snapshot: the source may have changed since, and nothing re-derives it.";
749
+ };
750
+ };
751
+ }];
752
+ };
753
+ readonly ProofRung: {
754
+ readonly title: "ProofRung";
755
+ 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.";
756
+ readonly type: "string";
757
+ readonly enum: readonly ["predicate", "derived", "selectiveDisclosure", "whole"];
758
+ };
759
+ readonly ValueType: {
760
+ readonly title: "ValueType";
761
+ 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.";
762
+ readonly type: "string";
763
+ readonly enum: readonly ["string", "number", "boolean", "date", "object"];
764
+ };
765
+ };
766
+ };
767
+ /**
768
+ * SPEC.md §7.2 policy for the request variant, from this specification's
769
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
770
+ * per-specification and cannot be derived from the document alone, and
771
+ * item 2 needs the schema this carries.
772
+ */
773
+ export declare const SPEC: {
774
+ readonly typeUri: "https://trusttasks.org/spec/persona/contact/put/1.1";
775
+ readonly isBearer: false;
776
+ readonly isProofRequired: true;
777
+ readonly isRecipientRequired: true;
778
+ readonly isIssuedAtRequired: true;
779
+ readonly payloadSchema: {
780
+ readonly $schema: "https://json-schema.org/draft/2020-12/schema";
781
+ readonly $id: "https://trusttasks.org/spec/persona/contact/put/1.1";
782
+ readonly title: "Persona Contact Put — payload";
783
+ readonly description: "File what a peer disclosed, or change the holder's own annotations on a contact, or both. Two forms. FILING (`subjectDid`, `knownByPersona`, `document`; no `contactId`) appends a revision, never overwrites, so a changed value is visible as a change rather than arriving silently — exactly as 1.0. ANNOTATING (`contactId`; no `subjectDid`, `knownByPersona`, `document` or `credentialRefs`) changes the holder's star, petname, lists, directory link or notes on an existing contact and appends no revision. In either form each annotation given replaces the stored one, each `removeX` removes one, and each annotation absent is unchanged. The outer document members are owned by the framework — SPEC §6.3.";
784
+ readonly type: "object";
785
+ readonly additionalProperties: false;
786
+ readonly required: readonly ["contextId"];
787
+ readonly oneOf: readonly [{
788
+ readonly required: readonly ["subjectDid", "knownByPersona", "document"];
789
+ readonly not: {
790
+ readonly required: readonly ["contactId"];
791
+ };
792
+ }, {
793
+ readonly required: readonly ["contactId"];
794
+ readonly not: {
795
+ readonly anyOf: readonly [{
796
+ readonly required: readonly ["subjectDid"];
797
+ }, {
798
+ readonly required: readonly ["knownByPersona"];
799
+ }, {
800
+ readonly required: readonly ["document"];
801
+ }, {
802
+ readonly required: readonly ["credentialRefs"];
803
+ }];
804
+ };
805
+ readonly anyOf: readonly [{
806
+ readonly required: readonly ["starred"];
807
+ }, {
808
+ readonly required: readonly ["petname"];
809
+ }, {
810
+ readonly required: readonly ["removePetname"];
811
+ }, {
812
+ readonly required: readonly ["lists"];
813
+ }, {
814
+ readonly required: readonly ["removeLists"];
815
+ }, {
816
+ readonly required: readonly ["directoryRef"];
817
+ }, {
818
+ readonly required: readonly ["removeDirectoryRef"];
819
+ }, {
820
+ readonly required: readonly ["notes"];
821
+ }, {
822
+ readonly required: readonly ["removeNotes"];
823
+ }];
824
+ }];
825
+ readonly dependentSchemas: {
826
+ readonly removePetname: {
827
+ readonly not: {
828
+ readonly required: readonly ["petname"];
829
+ };
830
+ };
831
+ readonly removeLists: {
832
+ readonly not: {
833
+ readonly required: readonly ["lists"];
834
+ };
835
+ };
836
+ readonly removeDirectoryRef: {
837
+ readonly not: {
838
+ readonly required: readonly ["directoryRef"];
839
+ };
840
+ };
841
+ readonly removeNotes: {
842
+ readonly not: {
843
+ readonly required: readonly ["notes"];
844
+ };
845
+ };
846
+ };
847
+ readonly properties: {
848
+ readonly contextId: {
849
+ readonly type: "string";
850
+ readonly minLength: 1;
851
+ };
852
+ readonly contactId: {
853
+ readonly $ref: "#/$defs/Ulid";
854
+ readonly description: "Annotating form only: the existing contact whose annotations change. A filing never names one — the agent keys a filing on (contextId, subjectDid, knownByPersona) as in 1.0.";
855
+ };
856
+ readonly subjectDid: {
857
+ readonly type: "string";
858
+ readonly minLength: 1;
859
+ readonly maxLength: 2048;
860
+ readonly description: "Filing form only. The DID the document is about, as disclosed. Normally pairwise, so it names this relationship and not the person across all of theirs.";
861
+ };
862
+ readonly knownByPersona: {
863
+ readonly type: "string";
864
+ readonly minLength: 1;
865
+ readonly maxLength: 2048;
866
+ readonly description: "Filing form only. Which of the holder's personas knows this contact. A contact belongs to the relationship, not to the holder at large — the same peer met through two personas is two contacts, and collapsing them would correlate the holder's own personas in their own address book.";
867
+ };
868
+ readonly document: {
869
+ readonly $ref: "#/$defs/ContactDocument";
870
+ };
871
+ readonly credentialRefs: {
872
+ readonly type: "array";
873
+ readonly maxItems: 256;
874
+ readonly items: {
875
+ readonly type: "string";
876
+ readonly minLength: 1;
877
+ };
878
+ readonly description: "Filing form only. Vault identifiers of credentials the peer presented alongside the document. The credentials themselves belong in the credential vault and the contact holds references.";
879
+ };
880
+ readonly starred: {
881
+ readonly type: "boolean";
882
+ readonly description: "Star or unstar the contact. Absent: unchanged. A boolean rather than a remove member because `false` is a value the holder chose, not an absence.";
883
+ };
884
+ readonly petname: {
885
+ readonly $ref: "#/$defs/Petname";
886
+ readonly description: "The holder's private name for the contact, replacing any they had. Absent: unchanged.";
887
+ };
888
+ readonly removePetname: {
889
+ readonly type: "boolean";
890
+ readonly const: true;
891
+ readonly description: "Remove the petname. Only `true` is meaningful, so only `true` is accepted. A separate member rather than `petname: null`, because a nullable optional member makes \"unchanged\" and \"remove\" the same value in libraries that map both to one absent option.";
892
+ };
893
+ readonly lists: {
894
+ readonly $ref: "#/$defs/ListIds";
895
+ readonly description: "The lists the contact is on, replacing the whole set. Every identifier MUST name a list in this context. Absent: unchanged. Take the contact off every list with `removeLists`.";
896
+ };
897
+ readonly removeLists: {
898
+ readonly type: "boolean";
899
+ readonly const: true;
900
+ readonly description: "Take the contact off every list. Only `true` is accepted.";
901
+ };
902
+ readonly directoryRef: {
903
+ readonly $ref: "#/$defs/DirectoryRef";
904
+ readonly description: "Link the contact to a community directory entry, replacing any link it had. Absent: unchanged.";
905
+ };
906
+ readonly removeDirectoryRef: {
907
+ readonly type: "boolean";
908
+ readonly const: true;
909
+ readonly description: "Remove the contact's directory link. Only `true` is accepted.";
910
+ };
911
+ readonly notes: {
912
+ readonly type: "string";
913
+ readonly minLength: 1;
914
+ readonly maxLength: 4096;
915
+ readonly description: "The holder's private note about this contact, replacing any they had. Absent: unchanged. Never disclosed to anyone, including the contact.";
916
+ };
917
+ readonly removeNotes: {
918
+ readonly type: "boolean";
919
+ readonly const: true;
920
+ readonly description: "Remove the note. Only `true` is accepted.";
921
+ };
922
+ readonly ext: {
923
+ readonly $ref: "#/$defs/Ext";
924
+ };
925
+ };
926
+ readonly $defs: {
927
+ readonly Response: {
928
+ readonly $anchor: "response";
929
+ readonly title: "Persona Contact Put — response payload";
930
+ readonly description: "Success response to persona/contact/put. Type https://trusttasks.org/spec/persona/contact/put/1.1#response. Identifiers, the current revision and what changed; no claim value and no annotation text is echoed.";
931
+ readonly type: "object";
932
+ readonly additionalProperties: false;
933
+ readonly required: readonly ["contactId", "rev", "created", "annotationsChanged"];
934
+ readonly properties: {
935
+ readonly contactId: {
936
+ readonly $ref: "#/$defs/Ulid";
937
+ };
938
+ readonly rev: {
939
+ readonly type: "integer";
940
+ readonly minimum: 1;
941
+ readonly description: "The contact's current revision: the one a filing just appended, or, for an annotating request, the revision that was already current. Annotations never move it.";
942
+ };
943
+ readonly created: {
944
+ readonly type: "boolean";
945
+ readonly description: "True when this is the first revision for the subject. Always false for an annotating request.";
946
+ };
947
+ readonly annotationsChanged: {
948
+ readonly type: "boolean";
949
+ readonly description: "True when any annotation now differs from what was stored. False when every annotation given already matched and every one named for removal was already absent — including a filing that named none.";
950
+ };
951
+ readonly changedClaims: {
952
+ readonly type: "array";
953
+ readonly maxItems: 256;
954
+ readonly items: {
955
+ readonly $ref: "#/$defs/ClaimType";
956
+ };
957
+ readonly description: "Claim types whose value differs from the previous revision. Present only on a filing that updated an existing contact.";
958
+ };
959
+ readonly ext: {
960
+ readonly $ref: "#/$defs/Ext";
961
+ };
962
+ };
963
+ };
964
+ readonly Ext: {
965
+ readonly title: "Ext";
966
+ 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.";
967
+ readonly type: "object";
968
+ readonly minProperties: 1;
969
+ readonly additionalProperties: true;
970
+ readonly propertyNames: {
971
+ readonly pattern: "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$";
972
+ };
973
+ };
974
+ readonly ClaimType: {
975
+ readonly title: "ClaimType";
976
+ 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.";
977
+ readonly type: "string";
978
+ readonly minLength: 1;
979
+ readonly maxLength: 128;
980
+ readonly pattern: "^(x:)?[a-z][a-zA-Z0-9]*(\\.[a-z][a-zA-Z0-9]*)*$";
981
+ };
982
+ readonly Ulid: {
983
+ readonly title: "Ulid";
984
+ 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.";
985
+ readonly type: "string";
986
+ readonly pattern: "^[0-9A-HJKMNP-TV-Z]{26}$";
987
+ };
988
+ readonly DirectoryRef: {
989
+ readonly title: "DirectoryRef";
990
+ readonly description: "Links a contact to the entry in a community's member directory it corresponds to, so the holder's own client can join that community's directory with the holder's address book — showing a star or a petname beside an entry — without either side telling the other. The community never learns the link exists; the contact never learns it either. A contact has at most one.";
991
+ readonly type: "object";
992
+ readonly additionalProperties: false;
993
+ readonly required: readonly ["vtcDid", "entryId"];
994
+ readonly properties: {
995
+ readonly vtcDid: {
996
+ readonly type: "string";
997
+ readonly minLength: 1;
998
+ readonly maxLength: 2048;
999
+ readonly pattern: "^did:[a-z0-9]+:";
1000
+ readonly description: "The DID of the community whose directory holds the entry.";
1001
+ };
1002
+ readonly entryId: {
1003
+ readonly $ref: "#/$defs/DirectoryEntryId";
1004
+ readonly description: "The entry, as that community's directory identifies it.";
1005
+ };
1006
+ };
1007
+ };
1008
+ readonly DirectoryEntryId: {
1009
+ readonly title: "DirectoryEntryId";
1010
+ readonly description: "A community directory entry's identifier, exactly as that community's directory returned it. Opaque and community-scoped: the agent stores and compares it as a string, never parses it, and never treats the same value under two communities as the same entry.";
1011
+ readonly type: "string";
1012
+ readonly minLength: 1;
1013
+ readonly maxLength: 128;
1014
+ readonly pattern: "^[A-Za-z0-9_-]+$";
1015
+ };
1016
+ readonly ListIds: {
1017
+ readonly title: "ListIds";
1018
+ readonly description: "The lists a contact is on, as a set: order carries no meaning. A contact on no list has no `lists` member, never an empty array, so there is one way to say \"none\".";
1019
+ readonly type: "array";
1020
+ readonly minItems: 1;
1021
+ readonly maxItems: 64;
1022
+ readonly uniqueItems: true;
1023
+ readonly items: {
1024
+ readonly $ref: "#/$defs/ListId";
1025
+ };
1026
+ };
1027
+ readonly ListId: {
1028
+ readonly title: "ListId";
1029
+ readonly description: "Identifier of one of the holder's contact lists: a ULID in Crockford base32, uppercase, assigned by the agent when the list is created. Meaningful only inside the context that holds the list; it is never sent to anyone but the holder's own clients.";
1030
+ readonly type: "string";
1031
+ readonly pattern: "^[0-9A-HJKMNP-TV-Z]{26}$";
1032
+ };
1033
+ readonly Petname: {
1034
+ readonly title: "Petname";
1035
+ readonly description: "The holder's private name for a contact, on one line: no control characters, line breaks included. A petname in Zooko's sense — chosen by the holder, meaningful to the holder, and unforgeable by anyone else, because nobody else can write it. Distinct from the contact's own disclosed `nickname` or display name, which the contact chose and may change. Compared exactly, as a string: an agent does not case-fold or normalise it.";
1036
+ readonly type: "string";
1037
+ readonly minLength: 1;
1038
+ readonly maxLength: 64;
1039
+ readonly pattern: "^[^\\u0000-\\u001F\\u007F]+$";
1040
+ };
1041
+ readonly ContactDocument: {
1042
+ readonly title: "ContactDocument";
1043
+ readonly description: "What a peer disclosed, as received. Structurally the same claim set a holder composes and presents — a profile and a contact card are one schema seen from two sides — which is why a maintainer validates both with the same code and a consumer renders both with the same view.";
1044
+ readonly type: "object";
1045
+ readonly additionalProperties: false;
1046
+ readonly required: readonly ["claims"];
1047
+ readonly properties: {
1048
+ readonly publisher: {
1049
+ readonly type: "string";
1050
+ readonly maxLength: 2048;
1051
+ readonly description: "The DID that published the document, as it appeared. Normally a pairwise identifier, so it names the relationship rather than the person.";
1052
+ };
1053
+ readonly cardVersion: {
1054
+ readonly type: "integer";
1055
+ readonly minimum: 1;
1056
+ readonly description: "The publisher's own monotonic counter, if they supplied one. Advisory: it orders the publisher's revisions relative to each other and MUST NOT be trusted to order them against anything else.";
1057
+ };
1058
+ readonly claims: {
1059
+ readonly type: "array";
1060
+ readonly maxItems: 256;
1061
+ readonly items: {
1062
+ readonly type: "object";
1063
+ readonly additionalProperties: false;
1064
+ readonly required: readonly ["type", "valueType", "value"];
1065
+ readonly properties: {
1066
+ readonly type: {
1067
+ readonly $ref: "#/$defs/ClaimType";
1068
+ };
1069
+ readonly valueType: {
1070
+ readonly $ref: "#/$defs/ValueType";
1071
+ };
1072
+ readonly value: {};
1073
+ readonly provenance: {
1074
+ readonly $ref: "#/$defs/Provenance";
1075
+ readonly description: "As asserted by the publisher. A recipient MUST NOT treat a claimed credentialBacked provenance as verified — it is a statement about what the publisher says backs the claim, and verification is a separate act against the credential itself.";
1076
+ };
1077
+ };
1078
+ };
1079
+ };
1080
+ };
1081
+ };
1082
+ readonly Provenance: {
1083
+ readonly title: "Provenance";
1084
+ readonly description: "Where a value comes from, and the member that makes this family worth building on a trust stack rather than in an address book. It survives to the verifier, so a recipient can tell — per field — what the holder typed from what an issuer attested.\n\n`selfAsserted` — the holder supplied it.\n\n`credentialBacked` — the value is derived from a credential in the vault at `claimPath`. The stored value is a CACHE FOR DISPLAY; the credential is the truth. A maintainer MUST re-derive it on read and MUST fail closed (never presenting a stale value) when the credential has been revoked, has expired, or has been archived or deleted.\n\n`generated` — the value is minted per verifier at disclosure time and recorded against that verifier, so every relying party receives a different one that routes back to the holder. This is the shape of the most widely adopted consumer privacy feature in this space; a maintainer need not operate a relay to conform, but the shape must exist, because retrofitting per-verifier values into a pool-of-values model is a migration rather than an addition.\n\n`derived` — the value was taken from a source the holder connected or supplied — a code-hosting profile, an uploaded CV — rather than typed by them or attested by an issuer. Nobody signed it: it is the holder's claim that the source said so, and a consumer MUST NOT present it as attested. It exists as its own kind because a derived value is neither of the others — the holder did not author it, and no one vouches for it — and a holder deciding whether to disclose deserves to know which of their values they typed.\n\nFor how strongly a disclosed value identifies the holder, the kinds rank `credentialBacked` above `derived` above `selfAsserted`; `generated` values are per-verifier and do not correlate.";
1085
+ readonly type: "object";
1086
+ readonly required: readonly ["kind"];
1087
+ readonly oneOf: readonly [{
1088
+ readonly additionalProperties: false;
1089
+ readonly required: readonly ["kind"];
1090
+ readonly properties: {
1091
+ readonly kind: {
1092
+ readonly const: "selfAsserted";
1093
+ };
1094
+ };
1095
+ }, {
1096
+ readonly additionalProperties: false;
1097
+ readonly required: readonly ["kind", "credentialId", "claimPath"];
1098
+ readonly properties: {
1099
+ readonly kind: {
1100
+ readonly const: "credentialBacked";
1101
+ };
1102
+ readonly credentialId: {
1103
+ readonly type: "string";
1104
+ readonly minLength: 1;
1105
+ readonly description: "Vault identifier of the backing credential.";
1106
+ };
1107
+ readonly claimPath: {
1108
+ readonly type: "string";
1109
+ readonly pattern: "^(/[^/~]*(~[01][^/~]*)*)*$";
1110
+ readonly description: "RFC 6901 JSON Pointer to the claim within the credential, e.g. `/credentialSubject/familyName`.";
1111
+ };
1112
+ readonly issuerDid: {
1113
+ readonly type: "string";
1114
+ readonly minLength: 1;
1115
+ readonly description: "Issuer of the backing credential. Advisory: a consumer MUST verify the credential rather than trusting this member.";
1116
+ };
1117
+ readonly proof: {
1118
+ readonly $ref: "#/$defs/ProofRung";
1119
+ readonly description: "The disclosure rung this claim was, or will be, presented at.";
1120
+ };
1121
+ };
1122
+ }, {
1123
+ readonly additionalProperties: false;
1124
+ readonly required: readonly ["kind", "generator"];
1125
+ readonly properties: {
1126
+ readonly kind: {
1127
+ readonly const: "generated";
1128
+ };
1129
+ readonly generator: {
1130
+ readonly type: "string";
1131
+ readonly minLength: 1;
1132
+ readonly maxLength: 64;
1133
+ readonly description: "Names the minting scheme, e.g. `relayEmail`. Maintainer-defined.";
1134
+ };
1135
+ readonly perVerifier: {
1136
+ readonly type: "boolean";
1137
+ readonly default: true;
1138
+ readonly description: "When true (the default and the only useful setting), a distinct value is minted for each verifier.";
1139
+ };
1140
+ };
1141
+ }, {
1142
+ readonly additionalProperties: false;
1143
+ readonly required: readonly ["kind", "source", "derivedAt"];
1144
+ readonly properties: {
1145
+ readonly kind: {
1146
+ readonly const: "derived";
1147
+ };
1148
+ readonly source: {
1149
+ readonly type: "string";
1150
+ readonly minLength: 1;
1151
+ readonly maxLength: 64;
1152
+ readonly pattern: "^[a-z][A-Za-z0-9.-]*$";
1153
+ readonly description: "The KIND of source the value was taken from — `github`, `cvUpload`, `linkedIn` — never an account, handle or URL. Provenance survives to the verifier, so this member is disclosed with the claim; a handle here would disclose an identifier the holder never chose to share.";
1154
+ };
1155
+ readonly derivedAt: {
1156
+ readonly type: "string";
1157
+ readonly format: "date-time";
1158
+ readonly description: "When the value was taken from the source. A derived value is a snapshot: the source may have changed since, and nothing re-derives it.";
1159
+ };
1160
+ };
1161
+ }];
1162
+ };
1163
+ readonly ProofRung: {
1164
+ readonly title: "ProofRung";
1165
+ 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.";
1166
+ readonly type: "string";
1167
+ readonly enum: readonly ["predicate", "derived", "selectiveDisclosure", "whole"];
1168
+ };
1169
+ readonly ValueType: {
1170
+ readonly title: "ValueType";
1171
+ 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.";
1172
+ readonly type: "string";
1173
+ readonly enum: readonly ["string", "number", "boolean", "date", "object"];
1174
+ };
1175
+ };
1176
+ };
1177
+ };
1178
+ /**
1179
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
1180
+ * tracks the *issuer* party's requirement because a response swaps the
1181
+ * parties (§7.3 item 5).
1182
+ */
1183
+ export declare const RESPONSE_SPEC: {
1184
+ readonly typeUri: "https://trusttasks.org/spec/persona/contact/put/1.1#response";
1185
+ readonly isBearer: false;
1186
+ readonly isProofRequired: true;
1187
+ readonly isRecipientRequired: true;
1188
+ readonly isIssuedAtRequired: true;
1189
+ readonly payloadSchema: {
1190
+ readonly $schema: "https://json-schema.org/draft/2020-12/schema";
1191
+ readonly $ref: "#/$defs/Response";
1192
+ readonly $defs: {
1193
+ readonly Response: {
1194
+ readonly $anchor: "response";
1195
+ readonly title: "Persona Contact Put — response payload";
1196
+ readonly description: "Success response to persona/contact/put. Type https://trusttasks.org/spec/persona/contact/put/1.1#response. Identifiers, the current revision and what changed; no claim value and no annotation text is echoed.";
1197
+ readonly type: "object";
1198
+ readonly additionalProperties: false;
1199
+ readonly required: readonly ["contactId", "rev", "created", "annotationsChanged"];
1200
+ readonly properties: {
1201
+ readonly contactId: {
1202
+ readonly $ref: "#/$defs/Ulid";
1203
+ };
1204
+ readonly rev: {
1205
+ readonly type: "integer";
1206
+ readonly minimum: 1;
1207
+ readonly description: "The contact's current revision: the one a filing just appended, or, for an annotating request, the revision that was already current. Annotations never move it.";
1208
+ };
1209
+ readonly created: {
1210
+ readonly type: "boolean";
1211
+ readonly description: "True when this is the first revision for the subject. Always false for an annotating request.";
1212
+ };
1213
+ readonly annotationsChanged: {
1214
+ readonly type: "boolean";
1215
+ readonly description: "True when any annotation now differs from what was stored. False when every annotation given already matched and every one named for removal was already absent — including a filing that named none.";
1216
+ };
1217
+ readonly changedClaims: {
1218
+ readonly type: "array";
1219
+ readonly maxItems: 256;
1220
+ readonly items: {
1221
+ readonly $ref: "#/$defs/ClaimType";
1222
+ };
1223
+ readonly description: "Claim types whose value differs from the previous revision. Present only on a filing that updated an existing contact.";
1224
+ };
1225
+ readonly ext: {
1226
+ readonly $ref: "#/$defs/Ext";
1227
+ };
1228
+ };
1229
+ };
1230
+ readonly Ext: {
1231
+ readonly title: "Ext";
1232
+ 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.";
1233
+ readonly type: "object";
1234
+ readonly minProperties: 1;
1235
+ readonly additionalProperties: true;
1236
+ readonly propertyNames: {
1237
+ readonly pattern: "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$";
1238
+ };
1239
+ };
1240
+ readonly ClaimType: {
1241
+ readonly title: "ClaimType";
1242
+ 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.";
1243
+ readonly type: "string";
1244
+ readonly minLength: 1;
1245
+ readonly maxLength: 128;
1246
+ readonly pattern: "^(x:)?[a-z][a-zA-Z0-9]*(\\.[a-z][a-zA-Z0-9]*)*$";
1247
+ };
1248
+ readonly Ulid: {
1249
+ readonly title: "Ulid";
1250
+ 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.";
1251
+ readonly type: "string";
1252
+ readonly pattern: "^[0-9A-HJKMNP-TV-Z]{26}$";
1253
+ };
1254
+ readonly DirectoryRef: {
1255
+ readonly title: "DirectoryRef";
1256
+ readonly description: "Links a contact to the entry in a community's member directory it corresponds to, so the holder's own client can join that community's directory with the holder's address book — showing a star or a petname beside an entry — without either side telling the other. The community never learns the link exists; the contact never learns it either. A contact has at most one.";
1257
+ readonly type: "object";
1258
+ readonly additionalProperties: false;
1259
+ readonly required: readonly ["vtcDid", "entryId"];
1260
+ readonly properties: {
1261
+ readonly vtcDid: {
1262
+ readonly type: "string";
1263
+ readonly minLength: 1;
1264
+ readonly maxLength: 2048;
1265
+ readonly pattern: "^did:[a-z0-9]+:";
1266
+ readonly description: "The DID of the community whose directory holds the entry.";
1267
+ };
1268
+ readonly entryId: {
1269
+ readonly $ref: "#/$defs/DirectoryEntryId";
1270
+ readonly description: "The entry, as that community's directory identifies it.";
1271
+ };
1272
+ };
1273
+ };
1274
+ readonly DirectoryEntryId: {
1275
+ readonly title: "DirectoryEntryId";
1276
+ readonly description: "A community directory entry's identifier, exactly as that community's directory returned it. Opaque and community-scoped: the agent stores and compares it as a string, never parses it, and never treats the same value under two communities as the same entry.";
1277
+ readonly type: "string";
1278
+ readonly minLength: 1;
1279
+ readonly maxLength: 128;
1280
+ readonly pattern: "^[A-Za-z0-9_-]+$";
1281
+ };
1282
+ readonly ListIds: {
1283
+ readonly title: "ListIds";
1284
+ readonly description: "The lists a contact is on, as a set: order carries no meaning. A contact on no list has no `lists` member, never an empty array, so there is one way to say \"none\".";
1285
+ readonly type: "array";
1286
+ readonly minItems: 1;
1287
+ readonly maxItems: 64;
1288
+ readonly uniqueItems: true;
1289
+ readonly items: {
1290
+ readonly $ref: "#/$defs/ListId";
1291
+ };
1292
+ };
1293
+ readonly ListId: {
1294
+ readonly title: "ListId";
1295
+ readonly description: "Identifier of one of the holder's contact lists: a ULID in Crockford base32, uppercase, assigned by the agent when the list is created. Meaningful only inside the context that holds the list; it is never sent to anyone but the holder's own clients.";
1296
+ readonly type: "string";
1297
+ readonly pattern: "^[0-9A-HJKMNP-TV-Z]{26}$";
1298
+ };
1299
+ readonly Petname: {
1300
+ readonly title: "Petname";
1301
+ readonly description: "The holder's private name for a contact, on one line: no control characters, line breaks included. A petname in Zooko's sense — chosen by the holder, meaningful to the holder, and unforgeable by anyone else, because nobody else can write it. Distinct from the contact's own disclosed `nickname` or display name, which the contact chose and may change. Compared exactly, as a string: an agent does not case-fold or normalise it.";
1302
+ readonly type: "string";
1303
+ readonly minLength: 1;
1304
+ readonly maxLength: 64;
1305
+ readonly pattern: "^[^\\u0000-\\u001F\\u007F]+$";
1306
+ };
1307
+ readonly ContactDocument: {
1308
+ readonly title: "ContactDocument";
1309
+ readonly description: "What a peer disclosed, as received. Structurally the same claim set a holder composes and presents — a profile and a contact card are one schema seen from two sides — which is why a maintainer validates both with the same code and a consumer renders both with the same view.";
1310
+ readonly type: "object";
1311
+ readonly additionalProperties: false;
1312
+ readonly required: readonly ["claims"];
1313
+ readonly properties: {
1314
+ readonly publisher: {
1315
+ readonly type: "string";
1316
+ readonly maxLength: 2048;
1317
+ readonly description: "The DID that published the document, as it appeared. Normally a pairwise identifier, so it names the relationship rather than the person.";
1318
+ };
1319
+ readonly cardVersion: {
1320
+ readonly type: "integer";
1321
+ readonly minimum: 1;
1322
+ readonly description: "The publisher's own monotonic counter, if they supplied one. Advisory: it orders the publisher's revisions relative to each other and MUST NOT be trusted to order them against anything else.";
1323
+ };
1324
+ readonly claims: {
1325
+ readonly type: "array";
1326
+ readonly maxItems: 256;
1327
+ readonly items: {
1328
+ readonly type: "object";
1329
+ readonly additionalProperties: false;
1330
+ readonly required: readonly ["type", "valueType", "value"];
1331
+ readonly properties: {
1332
+ readonly type: {
1333
+ readonly $ref: "#/$defs/ClaimType";
1334
+ };
1335
+ readonly valueType: {
1336
+ readonly $ref: "#/$defs/ValueType";
1337
+ };
1338
+ readonly value: {};
1339
+ readonly provenance: {
1340
+ readonly $ref: "#/$defs/Provenance";
1341
+ readonly description: "As asserted by the publisher. A recipient MUST NOT treat a claimed credentialBacked provenance as verified — it is a statement about what the publisher says backs the claim, and verification is a separate act against the credential itself.";
1342
+ };
1343
+ };
1344
+ };
1345
+ };
1346
+ };
1347
+ };
1348
+ readonly Provenance: {
1349
+ readonly title: "Provenance";
1350
+ readonly description: "Where a value comes from, and the member that makes this family worth building on a trust stack rather than in an address book. It survives to the verifier, so a recipient can tell — per field — what the holder typed from what an issuer attested.\n\n`selfAsserted` — the holder supplied it.\n\n`credentialBacked` — the value is derived from a credential in the vault at `claimPath`. The stored value is a CACHE FOR DISPLAY; the credential is the truth. A maintainer MUST re-derive it on read and MUST fail closed (never presenting a stale value) when the credential has been revoked, has expired, or has been archived or deleted.\n\n`generated` — the value is minted per verifier at disclosure time and recorded against that verifier, so every relying party receives a different one that routes back to the holder. This is the shape of the most widely adopted consumer privacy feature in this space; a maintainer need not operate a relay to conform, but the shape must exist, because retrofitting per-verifier values into a pool-of-values model is a migration rather than an addition.\n\n`derived` — the value was taken from a source the holder connected or supplied — a code-hosting profile, an uploaded CV — rather than typed by them or attested by an issuer. Nobody signed it: it is the holder's claim that the source said so, and a consumer MUST NOT present it as attested. It exists as its own kind because a derived value is neither of the others — the holder did not author it, and no one vouches for it — and a holder deciding whether to disclose deserves to know which of their values they typed.\n\nFor how strongly a disclosed value identifies the holder, the kinds rank `credentialBacked` above `derived` above `selfAsserted`; `generated` values are per-verifier and do not correlate.";
1351
+ readonly type: "object";
1352
+ readonly required: readonly ["kind"];
1353
+ readonly oneOf: readonly [{
1354
+ readonly additionalProperties: false;
1355
+ readonly required: readonly ["kind"];
1356
+ readonly properties: {
1357
+ readonly kind: {
1358
+ readonly const: "selfAsserted";
1359
+ };
1360
+ };
1361
+ }, {
1362
+ readonly additionalProperties: false;
1363
+ readonly required: readonly ["kind", "credentialId", "claimPath"];
1364
+ readonly properties: {
1365
+ readonly kind: {
1366
+ readonly const: "credentialBacked";
1367
+ };
1368
+ readonly credentialId: {
1369
+ readonly type: "string";
1370
+ readonly minLength: 1;
1371
+ readonly description: "Vault identifier of the backing credential.";
1372
+ };
1373
+ readonly claimPath: {
1374
+ readonly type: "string";
1375
+ readonly pattern: "^(/[^/~]*(~[01][^/~]*)*)*$";
1376
+ readonly description: "RFC 6901 JSON Pointer to the claim within the credential, e.g. `/credentialSubject/familyName`.";
1377
+ };
1378
+ readonly issuerDid: {
1379
+ readonly type: "string";
1380
+ readonly minLength: 1;
1381
+ readonly description: "Issuer of the backing credential. Advisory: a consumer MUST verify the credential rather than trusting this member.";
1382
+ };
1383
+ readonly proof: {
1384
+ readonly $ref: "#/$defs/ProofRung";
1385
+ readonly description: "The disclosure rung this claim was, or will be, presented at.";
1386
+ };
1387
+ };
1388
+ }, {
1389
+ readonly additionalProperties: false;
1390
+ readonly required: readonly ["kind", "generator"];
1391
+ readonly properties: {
1392
+ readonly kind: {
1393
+ readonly const: "generated";
1394
+ };
1395
+ readonly generator: {
1396
+ readonly type: "string";
1397
+ readonly minLength: 1;
1398
+ readonly maxLength: 64;
1399
+ readonly description: "Names the minting scheme, e.g. `relayEmail`. Maintainer-defined.";
1400
+ };
1401
+ readonly perVerifier: {
1402
+ readonly type: "boolean";
1403
+ readonly default: true;
1404
+ readonly description: "When true (the default and the only useful setting), a distinct value is minted for each verifier.";
1405
+ };
1406
+ };
1407
+ }, {
1408
+ readonly additionalProperties: false;
1409
+ readonly required: readonly ["kind", "source", "derivedAt"];
1410
+ readonly properties: {
1411
+ readonly kind: {
1412
+ readonly const: "derived";
1413
+ };
1414
+ readonly source: {
1415
+ readonly type: "string";
1416
+ readonly minLength: 1;
1417
+ readonly maxLength: 64;
1418
+ readonly pattern: "^[a-z][A-Za-z0-9.-]*$";
1419
+ readonly description: "The KIND of source the value was taken from — `github`, `cvUpload`, `linkedIn` — never an account, handle or URL. Provenance survives to the verifier, so this member is disclosed with the claim; a handle here would disclose an identifier the holder never chose to share.";
1420
+ };
1421
+ readonly derivedAt: {
1422
+ readonly type: "string";
1423
+ readonly format: "date-time";
1424
+ readonly description: "When the value was taken from the source. A derived value is a snapshot: the source may have changed since, and nothing re-derives it.";
1425
+ };
1426
+ };
1427
+ }];
1428
+ };
1429
+ readonly ProofRung: {
1430
+ readonly title: "ProofRung";
1431
+ 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.";
1432
+ readonly type: "string";
1433
+ readonly enum: readonly ["predicate", "derived", "selectiveDisclosure", "whole"];
1434
+ };
1435
+ readonly ValueType: {
1436
+ readonly title: "ValueType";
1437
+ 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.";
1438
+ readonly type: "string";
1439
+ readonly enum: readonly ["string", "number", "boolean", "date", "object"];
1440
+ };
1441
+ };
1442
+ };
1443
+ };
1444
+ //# sourceMappingURL=payload.d.ts.map