@openvtc/trust-tasks 0.21.14 → 0.21.16

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 (32) hide show
  1. package/CHANGELOG.md +45 -0
  2. package/dist/index.d.ts +5 -0
  3. package/dist/index.d.ts.map +1 -1
  4. package/dist/index.js +5 -0
  5. package/dist/index.js.map +1 -1
  6. package/dist/vta/attestation/mnemonic-status/0.1/payload.d.ts +281 -0
  7. package/dist/vta/attestation/mnemonic-status/0.1/payload.d.ts.map +1 -0
  8. package/dist/vta/attestation/mnemonic-status/0.1/payload.js +157 -0
  9. package/dist/vta/attestation/mnemonic-status/0.1/payload.js.map +1 -0
  10. package/dist/vta/metrics/show/0.1/payload.d.ts +674 -0
  11. package/dist/vta/metrics/show/0.1/payload.d.ts.map +1 -0
  12. package/dist/vta/metrics/show/0.1/payload.js +387 -0
  13. package/dist/vta/metrics/show/0.1/payload.js.map +1 -0
  14. package/dist/vtc/relationships/revoke/0.2/payload.d.ts +287 -0
  15. package/dist/vtc/relationships/revoke/0.2/payload.d.ts.map +1 -0
  16. package/dist/vtc/relationships/revoke/0.2/payload.js +159 -0
  17. package/dist/vtc/relationships/revoke/0.2/payload.js.map +1 -0
  18. package/dist/vtc/vetting/hidden/publish/0.1/payload.d.ts +1385 -0
  19. package/dist/vtc/vetting/hidden/publish/0.1/payload.d.ts.map +1 -0
  20. package/dist/vtc/vetting/hidden/publish/0.1/payload.js +735 -0
  21. package/dist/vtc/vetting/hidden/publish/0.1/payload.js.map +1 -0
  22. package/dist/vtc/vetting/vetters/resend/0.2/payload.d.ts +254 -0
  23. package/dist/vtc/vetting/vetters/resend/0.2/payload.d.ts.map +1 -0
  24. package/dist/vtc/vetting/vetters/resend/0.2/payload.js +142 -0
  25. package/dist/vtc/vetting/vetters/resend/0.2/payload.js.map +1 -0
  26. package/package.json +1 -1
  27. package/src/index.ts +5 -0
  28. package/src/vta/attestation/mnemonic-status/0.1/payload.ts +203 -0
  29. package/src/vta/metrics/show/0.1/payload.ts +418 -0
  30. package/src/vtc/relationships/revoke/0.2/payload.ts +209 -0
  31. package/src/vtc/vetting/hidden/publish/0.1/payload.ts +905 -0
  32. package/src/vtc/vetting/vetters/resend/0.2/payload.ts +183 -0
@@ -0,0 +1,183 @@
1
+ /**
2
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
3
+ * Source: specs/vtc/vetting/vetters/resend/0.2/payload.schema.json
4
+ */
5
+
6
+ import type { Ext } from "../../../../../_shared/components.js";
7
+
8
+
9
+ /**
10
+ * A vetter asks the community to deliver their live vetter role credential again, over credential-exchange/issue, and an administrator may do the same on a named member's behalf. The community issues nothing new and returns the delivered credential's `id` and `validUntil`.
11
+ */
12
+ export interface VTCVettingVettersResendPayload {
13
+ /**
14
+ * The vetter to resend the live grant for, on an administrator's behalf. Requires the community-administrator capability. Absent: the request concerns the sender's own live grant, exactly as 0.1.
15
+ */
16
+ memberDid?: string;
17
+ ext?: Ext;
18
+ }
19
+ /**
20
+ * The credential the community delivered again.
21
+ */
22
+ export interface VTCVettingVettersResendResponsePayload {
23
+ /**
24
+ * The `id` of the vetter role credential delivered — the same `credentialId` vtc/vetting/vetters/grant returned.
25
+ */
26
+ credentialId: string;
27
+ /**
28
+ * That credential's `validUntil`.
29
+ */
30
+ validUntil: string;
31
+ }
32
+
33
+ /** Shared definitions this specification references, re-exported under the names it used to declare them with. */
34
+ export type { Ext };
35
+
36
+ /** Trust Task type URI. */
37
+ export const TYPE_URI = "https://trusttasks.org/spec/vtc/vetting/vetters/resend/0.2" as const;
38
+
39
+ /** Stable alias for this specification's request payload shape. */
40
+ export type Payload = VTCVettingVettersResendPayload;
41
+
42
+ /** Trust Task response type URI (request type URI + "#response"). */
43
+ export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/vtc/vetting/vetters/resend/0.2#response" as const;
44
+
45
+ /** Stable alias for this specification's success-response payload shape. */
46
+ export type Response = VTCVettingVettersResendResponsePayload;
47
+
48
+ /**
49
+ * This specification's payload schema, as a value.
50
+ *
51
+ * SPEC.md §7.2 item 2 is performed against this. It is shipped as data
52
+ * rather than only as a `.json` file because TypeScript types are erased
53
+ * at runtime: without a schema a consumer has nothing to validate, and
54
+ * every REQUIRED payload member is optional in practice. Cross-file
55
+ * `$ref`s are already inlined, so it needs no resolver.
56
+ */
57
+ export const PAYLOAD_SCHEMA = {
58
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
59
+ "$id": "https://trusttasks.org/spec/vtc/vetting/vetters/resend/0.2",
60
+ "title": "VTC Vetting — Vetters Resend — payload",
61
+ "description": "A vetter asks the community to deliver their live vetter role credential again, over credential-exchange/issue, and an administrator may do the same on a named member's behalf. The community issues nothing new and returns the delivered credential's `id` and `validUntil`.",
62
+ "type": "object",
63
+ "additionalProperties": false,
64
+ "properties": {
65
+ "memberDid": {
66
+ "type": "string",
67
+ "minLength": 1,
68
+ "description": "The vetter to resend the live grant for, on an administrator's behalf. Requires the community-administrator capability. Absent: the request concerns the sender's own live grant, exactly as 0.1."
69
+ },
70
+ "ext": {
71
+ "$ref": "#/$defs/Ext"
72
+ }
73
+ },
74
+ "$defs": {
75
+ "Response": {
76
+ "$anchor": "response",
77
+ "title": "VTC Vetting — Vetters Resend — response payload",
78
+ "description": "The credential the community delivered again.",
79
+ "type": "object",
80
+ "additionalProperties": false,
81
+ "required": [
82
+ "credentialId",
83
+ "validUntil"
84
+ ],
85
+ "properties": {
86
+ "credentialId": {
87
+ "type": "string",
88
+ "minLength": 1,
89
+ "maxLength": 512,
90
+ "pattern": "^[a-zA-Z][a-zA-Z0-9+.-]*:\\S+$",
91
+ "description": "The `id` of the vetter role credential delivered — the same `credentialId` vtc/vetting/vetters/grant returned."
92
+ },
93
+ "validUntil": {
94
+ "type": "string",
95
+ "format": "date-time",
96
+ "description": "That credential's `validUntil`."
97
+ }
98
+ }
99
+ },
100
+ "Ext": {
101
+ "title": "Ext",
102
+ "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.",
103
+ "type": "object",
104
+ "minProperties": 1,
105
+ "additionalProperties": true,
106
+ "propertyNames": {
107
+ "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
108
+ }
109
+ }
110
+ }
111
+ } as const;
112
+
113
+ /** As {@link PAYLOAD_SCHEMA}, for the success-response variant. */
114
+ export const RESPONSE_PAYLOAD_SCHEMA = {
115
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
116
+ "$ref": "#/$defs/Response",
117
+ "$defs": {
118
+ "Response": {
119
+ "$anchor": "response",
120
+ "title": "VTC Vetting — Vetters Resend — response payload",
121
+ "description": "The credential the community delivered again.",
122
+ "type": "object",
123
+ "additionalProperties": false,
124
+ "required": [
125
+ "credentialId",
126
+ "validUntil"
127
+ ],
128
+ "properties": {
129
+ "credentialId": {
130
+ "type": "string",
131
+ "minLength": 1,
132
+ "maxLength": 512,
133
+ "pattern": "^[a-zA-Z][a-zA-Z0-9+.-]*:\\S+$",
134
+ "description": "The `id` of the vetter role credential delivered — the same `credentialId` vtc/vetting/vetters/grant returned."
135
+ },
136
+ "validUntil": {
137
+ "type": "string",
138
+ "format": "date-time",
139
+ "description": "That credential's `validUntil`."
140
+ }
141
+ }
142
+ },
143
+ "Ext": {
144
+ "title": "Ext",
145
+ "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.",
146
+ "type": "object",
147
+ "minProperties": 1,
148
+ "additionalProperties": true,
149
+ "propertyNames": {
150
+ "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
151
+ }
152
+ }
153
+ }
154
+ } as const;
155
+
156
+ /**
157
+ * SPEC.md §7.2 policy for the request variant, from this specification's
158
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
159
+ * per-specification and cannot be derived from the document alone, and
160
+ * item 2 needs the schema this carries.
161
+ */
162
+ export const SPEC = {
163
+ typeUri: TYPE_URI,
164
+ isBearer: false,
165
+ isProofRequired: true,
166
+ isRecipientRequired: true,
167
+ isIssuedAtRequired: false,
168
+ payloadSchema: PAYLOAD_SCHEMA,
169
+ } as const;
170
+
171
+ /**
172
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
173
+ * tracks the *issuer* party's requirement because a response swaps the
174
+ * parties (§7.3 item 5).
175
+ */
176
+ export const RESPONSE_SPEC = {
177
+ typeUri: RESPONSE_TYPE_URI,
178
+ isBearer: false,
179
+ isProofRequired: true,
180
+ isRecipientRequired: true,
181
+ isIssuedAtRequired: false,
182
+ payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
183
+ } as const;