@openvtc/trust-tasks 0.6.1 → 0.6.3

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 (41) hide show
  1. package/dist/index.d.ts +7 -0
  2. package/dist/index.d.ts.map +1 -1
  3. package/dist/index.js +7 -0
  4. package/dist/index.js.map +1 -1
  5. package/dist/vrc/relationships/issue/0.1/payload.d.ts +69 -0
  6. package/dist/vrc/relationships/issue/0.1/payload.d.ts.map +1 -0
  7. package/dist/vrc/relationships/issue/0.1/payload.js +31 -0
  8. package/dist/vrc/relationships/issue/0.1/payload.js.map +1 -0
  9. package/dist/vrc/relationships/propose/0.1/payload.d.ts +77 -0
  10. package/dist/vrc/relationships/propose/0.1/payload.d.ts.map +1 -0
  11. package/dist/vrc/relationships/propose/0.1/payload.js +31 -0
  12. package/dist/vrc/relationships/propose/0.1/payload.js.map +1 -0
  13. package/dist/vtc/relationships/list/0.2/payload.d.ts +70 -0
  14. package/dist/vtc/relationships/list/0.2/payload.d.ts.map +1 -0
  15. package/dist/vtc/relationships/list/0.2/payload.js +31 -0
  16. package/dist/vtc/relationships/list/0.2/payload.js.map +1 -0
  17. package/dist/vtc/relationships/publish/0.2/payload.d.ts +62 -0
  18. package/dist/vtc/relationships/publish/0.2/payload.d.ts.map +1 -0
  19. package/dist/vtc/relationships/publish/0.2/payload.js +31 -0
  20. package/dist/vtc/relationships/publish/0.2/payload.js.map +1 -0
  21. package/dist/vtc/relationships/request/0.2/payload.d.ts +66 -0
  22. package/dist/vtc/relationships/request/0.2/payload.d.ts.map +1 -0
  23. package/dist/vtc/relationships/request/0.2/payload.js +31 -0
  24. package/dist/vtc/relationships/request/0.2/payload.js.map +1 -0
  25. package/dist/witness/session/0.1/payload.d.ts +68 -0
  26. package/dist/witness/session/0.1/payload.d.ts.map +1 -0
  27. package/dist/witness/session/0.1/payload.js +31 -0
  28. package/dist/witness/session/0.1/payload.js.map +1 -0
  29. package/dist/witness/session/submit/0.1/payload.d.ts +66 -0
  30. package/dist/witness/session/submit/0.1/payload.d.ts.map +1 -0
  31. package/dist/witness/session/submit/0.1/payload.js +31 -0
  32. package/dist/witness/session/submit/0.1/payload.js.map +1 -0
  33. package/package.json +1 -1
  34. package/src/index.ts +7 -0
  35. package/src/vrc/relationships/issue/0.1/payload.ts +76 -0
  36. package/src/vrc/relationships/propose/0.1/payload.ts +83 -0
  37. package/src/vtc/relationships/list/0.2/payload.ts +77 -0
  38. package/src/vtc/relationships/publish/0.2/payload.ts +69 -0
  39. package/src/vtc/relationships/request/0.2/payload.ts +73 -0
  40. package/src/witness/session/0.1/payload.ts +74 -0
  41. package/src/witness/session/submit/0.1/payload.ts +73 -0
@@ -0,0 +1,31 @@
1
+ /**
2
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
3
+ * Source: specs/vtc/relationships/publish/0.2/payload.schema.json
4
+ */
5
+ /** Trust Task type URI. */
6
+ export const TYPE_URI = "https://trusttasks.org/spec/vtc/relationships/publish/0.2";
7
+ /** Trust Task response type URI (request type URI + "#response"). */
8
+ export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/vtc/relationships/publish/0.2#response";
9
+ /**
10
+ * SPEC.md §7.2 policy for the request variant, from this specification's
11
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
12
+ * per-specification and cannot be derived from the document alone.
13
+ */
14
+ export const SPEC = {
15
+ typeUri: TYPE_URI,
16
+ isBearer: false,
17
+ isProofRequired: true,
18
+ isRecipientRequired: true,
19
+ };
20
+ /**
21
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
22
+ * tracks the *issuer* party's requirement because a response swaps the
23
+ * parties (§7.3 item 5).
24
+ */
25
+ export const RESPONSE_SPEC = {
26
+ typeUri: RESPONSE_TYPE_URI,
27
+ isBearer: false,
28
+ isProofRequired: true,
29
+ isRecipientRequired: true,
30
+ };
31
+ //# sourceMappingURL=payload.js.map
@@ -0,0 +1 @@
1
+ {"version":3,"file":"payload.js","sourceRoot":"","sources":["../../../../../src/vtc/relationships/publish/0.2/payload.ts"],"names":[],"mappings":"AAAA;;;GAGG;AA+BH,2BAA2B;AAC3B,MAAM,CAAC,MAAM,QAAQ,GAAG,2DAAoE,CAAC;AAK7F,qEAAqE;AACrE,MAAM,CAAC,MAAM,iBAAiB,GAAG,oEAA6E,CAAC;AAK/G;;;;GAIG;AACH,MAAM,CAAC,MAAM,IAAI,GAAG;IAClB,OAAO,EAAE,QAAQ;IACjB,QAAQ,EAAE,KAAK;IACf,eAAe,EAAE,IAAI;IACrB,mBAAmB,EAAE,IAAI;CACjB,CAAC;AAEX;;;;GAIG;AACH,MAAM,CAAC,MAAM,aAAa,GAAG;IAC3B,OAAO,EAAE,iBAAiB;IAC1B,QAAQ,EAAE,KAAK;IACf,eAAe,EAAE,IAAI;IACrB,mBAAmB,EAAE,IAAI;CACjB,CAAC"}
@@ -0,0 +1,66 @@
1
+ /**
2
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
3
+ * Source: specs/vtc/relationships/request/0.2/payload.schema.json
4
+ */
5
+ /**
6
+ * Digest over the RFC 8785 canonicalization of the returned VRC, for out-of-band integrity checks. Matches the digest `vtc/relationships/publish` reports once the credential is lodged, so the two can be tied together without re-hashing — which requires both ends to canonicalize the same way, and is why the canonicalization is named here rather than assumed.
7
+ */
8
+ export type DigestMultibase = string;
9
+ /**
10
+ * A member asks another member to issue them a Verifiable Relationship Credential. Everything here is a hint: the issuing member decides, and declines with a trust-task-error carrying `vtc/relationships/request:declined` rather than a bespoke rejection message.
11
+ */
12
+ export interface VTCRelationshipsRequestPayload {
13
+ /**
14
+ * Why the requester is asking, in their own words, for the issuing member to weigh. A hint and not a term — the issuing member is under no obligation to honour it, and MUST NOT treat its absence as a defect. Free text reaching a human, so a producer SHOULD keep it to what it is willing to have quoted back.
15
+ */
16
+ reason?: string;
17
+ ext?: Ext;
18
+ }
19
+ /**
20
+ * 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.
21
+ */
22
+ export interface Ext {
23
+ [k: string]: unknown | undefined;
24
+ }
25
+ /**
26
+ * The issued credential. Returned only where the issuing member agreed; a decline is a trust-task-error, not a response with an empty field.
27
+ */
28
+ export interface VTCRelationshipsRequestResponsePayload {
29
+ /**
30
+ * A signed W3C Verifiable Relationship Credential (opaque here). Its issuer MUST be the issuing member — the party that signed this response — and its credentialSubject.id MUST name the requester. The same shape `vtc/relationships/publish` accepts, so a requester can lodge it with the community unchanged.
31
+ */
32
+ vrc: {};
33
+ vrcDigestMultibase?: DigestMultibase;
34
+ ext?: Ext;
35
+ }
36
+ /** Trust Task type URI. */
37
+ export declare const TYPE_URI: "https://trusttasks.org/spec/vtc/relationships/request/0.2";
38
+ /** Stable alias for this specification's request payload shape. */
39
+ export type Payload = DigestMultibase;
40
+ /** Trust Task response type URI (request type URI + "#response"). */
41
+ export declare const RESPONSE_TYPE_URI: "https://trusttasks.org/spec/vtc/relationships/request/0.2#response";
42
+ /** Stable alias for this specification's success-response payload shape. */
43
+ export type Response = VTCRelationshipsRequestResponsePayload;
44
+ /**
45
+ * SPEC.md §7.2 policy for the request variant, from this specification's
46
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
47
+ * per-specification and cannot be derived from the document alone.
48
+ */
49
+ export declare const SPEC: {
50
+ readonly typeUri: "https://trusttasks.org/spec/vtc/relationships/request/0.2";
51
+ readonly isBearer: false;
52
+ readonly isProofRequired: true;
53
+ readonly isRecipientRequired: true;
54
+ };
55
+ /**
56
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
57
+ * tracks the *issuer* party's requirement because a response swaps the
58
+ * parties (§7.3 item 5).
59
+ */
60
+ export declare const RESPONSE_SPEC: {
61
+ readonly typeUri: "https://trusttasks.org/spec/vtc/relationships/request/0.2#response";
62
+ readonly isBearer: false;
63
+ readonly isProofRequired: true;
64
+ readonly isRecipientRequired: true;
65
+ };
66
+ //# sourceMappingURL=payload.d.ts.map
@@ -0,0 +1 @@
1
+ {"version":3,"file":"payload.d.ts","sourceRoot":"","sources":["../../../../../src/vtc/relationships/request/0.2/payload.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH;;GAEG;AACH,MAAM,MAAM,eAAe,GAAG,MAAM,CAAC;AAErC;;GAEG;AACH,MAAM,WAAW,8BAA8B;IAC7C;;OAEG;IACH,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,GAAG,CAAC,EAAE,GAAG,CAAC;CACX;AACD;;GAEG;AACH,MAAM,WAAW,GAAG;IAClB,CAAC,CAAC,EAAE,MAAM,GAAG,OAAO,GAAG,SAAS,CAAC;CAClC;AACD;;GAEG;AACH,MAAM,WAAW,sCAAsC;IACrD;;OAEG;IACH,GAAG,EAAE,EAAE,CAAC;IACR,kBAAkB,CAAC,EAAE,eAAe,CAAC;IACrC,GAAG,CAAC,EAAE,GAAG,CAAC;CACX;AAED,2BAA2B;AAC3B,eAAO,MAAM,QAAQ,EAAG,2DAAoE,CAAC;AAE7F,mEAAmE;AACnE,MAAM,MAAM,OAAO,GAAG,eAAe,CAAC;AAEtC,qEAAqE;AACrE,eAAO,MAAM,iBAAiB,EAAG,oEAA6E,CAAC;AAE/G,4EAA4E;AAC5E,MAAM,MAAM,QAAQ,GAAG,sCAAsC,CAAC;AAE9D;;;;GAIG;AACH,eAAO,MAAM,IAAI;;;;;CAKP,CAAC;AAEX;;;;GAIG;AACH,eAAO,MAAM,aAAa;;;;;CAKhB,CAAC"}
@@ -0,0 +1,31 @@
1
+ /**
2
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
3
+ * Source: specs/vtc/relationships/request/0.2/payload.schema.json
4
+ */
5
+ /** Trust Task type URI. */
6
+ export const TYPE_URI = "https://trusttasks.org/spec/vtc/relationships/request/0.2";
7
+ /** Trust Task response type URI (request type URI + "#response"). */
8
+ export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/vtc/relationships/request/0.2#response";
9
+ /**
10
+ * SPEC.md §7.2 policy for the request variant, from this specification's
11
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
12
+ * per-specification and cannot be derived from the document alone.
13
+ */
14
+ export const SPEC = {
15
+ typeUri: TYPE_URI,
16
+ isBearer: false,
17
+ isProofRequired: true,
18
+ isRecipientRequired: true,
19
+ };
20
+ /**
21
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
22
+ * tracks the *issuer* party's requirement because a response swaps the
23
+ * parties (§7.3 item 5).
24
+ */
25
+ export const RESPONSE_SPEC = {
26
+ typeUri: RESPONSE_TYPE_URI,
27
+ isBearer: false,
28
+ isProofRequired: true,
29
+ isRecipientRequired: true,
30
+ };
31
+ //# sourceMappingURL=payload.js.map
@@ -0,0 +1 @@
1
+ {"version":3,"file":"payload.js","sourceRoot":"","sources":["../../../../../src/vtc/relationships/request/0.2/payload.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAmCH,2BAA2B;AAC3B,MAAM,CAAC,MAAM,QAAQ,GAAG,2DAAoE,CAAC;AAK7F,qEAAqE;AACrE,MAAM,CAAC,MAAM,iBAAiB,GAAG,oEAA6E,CAAC;AAK/G;;;;GAIG;AACH,MAAM,CAAC,MAAM,IAAI,GAAG;IAClB,OAAO,EAAE,QAAQ;IACjB,QAAQ,EAAE,KAAK;IACf,eAAe,EAAE,IAAI;IACrB,mBAAmB,EAAE,IAAI;CACjB,CAAC;AAEX;;;;GAIG;AACH,MAAM,CAAC,MAAM,aAAa,GAAG;IAC3B,OAAO,EAAE,iBAAiB;IAC1B,QAAQ,EAAE,KAAK;IACf,eAAe,EAAE,IAAI;IACrB,mBAAmB,EAAE,IAAI;CACjB,CAAC"}
@@ -0,0 +1,68 @@
1
+ /**
2
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
3
+ * Source: specs/witness/session/0.1/payload.schema.json
4
+ */
5
+ /**
6
+ * Opens one participating party's witness session as its own exchange, nested in a relationship exchange via parentThreadId. A session is bilateral — a witnessed exchange between two parties runs two sessions with the same witness, each naming the same parties pair. The response issues the session challenge; the request document's id is the value that party's VWC later carries as taskContext.
7
+ */
8
+ export interface WitnessSessionPayload {
9
+ /**
10
+ * The relationship DIDs of the exchange to be witnessed — the pairwise values the relationship proposal exchanged, in either order.
11
+ *
12
+ * @minItems 2
13
+ * @maxItems 2
14
+ */
15
+ parties: [string, string];
16
+ ext?: Ext;
17
+ }
18
+ /**
19
+ * 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.
20
+ */
21
+ export interface Ext {
22
+ [k: string]: unknown | undefined;
23
+ }
24
+ /**
25
+ * The session challenge, issued under the REQUIRED proof. The presentation under witness/session/submit binds to {challenge, domain}. It reaches only the party that opened this session — which is why each party opens its own.
26
+ */
27
+ export interface WitnessSessionResponsePayload {
28
+ /**
29
+ * A fresh, unpredictable, single-use value this session's presentation binds to. A witness MUST NOT reuse a challenge across sessions — including across the two sessions of one witnessed exchange, where a shared value would let either party's presentation satisfy the other's session.
30
+ */
31
+ challenge: string;
32
+ /**
33
+ * The domain the presentations bind alongside the challenge, identifying this witness's verification context.
34
+ */
35
+ domain: string;
36
+ ext?: Ext;
37
+ }
38
+ /** Trust Task type URI. */
39
+ export declare const TYPE_URI: "https://trusttasks.org/spec/witness/session/0.1";
40
+ /** Stable alias for this specification's request payload shape. */
41
+ export type Payload = WitnessSessionPayload;
42
+ /** Trust Task response type URI (request type URI + "#response"). */
43
+ export declare const RESPONSE_TYPE_URI: "https://trusttasks.org/spec/witness/session/0.1#response";
44
+ /** Stable alias for this specification's success-response payload shape. */
45
+ export type Response = WitnessSessionResponsePayload;
46
+ /**
47
+ * SPEC.md §7.2 policy for the request variant, from this specification's
48
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
49
+ * per-specification and cannot be derived from the document alone.
50
+ */
51
+ export declare const SPEC: {
52
+ readonly typeUri: "https://trusttasks.org/spec/witness/session/0.1";
53
+ readonly isBearer: false;
54
+ readonly isProofRequired: false;
55
+ readonly isRecipientRequired: true;
56
+ };
57
+ /**
58
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
59
+ * tracks the *issuer* party's requirement because a response swaps the
60
+ * parties (§7.3 item 5).
61
+ */
62
+ export declare const RESPONSE_SPEC: {
63
+ readonly typeUri: "https://trusttasks.org/spec/witness/session/0.1#response";
64
+ readonly isBearer: false;
65
+ readonly isProofRequired: true;
66
+ readonly isRecipientRequired: true;
67
+ };
68
+ //# sourceMappingURL=payload.d.ts.map
@@ -0,0 +1 @@
1
+ {"version":3,"file":"payload.d.ts","sourceRoot":"","sources":["../../../../src/witness/session/0.1/payload.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH;;GAEG;AACH,MAAM,WAAW,qBAAqB;IACpC;;;;;OAKG;IACH,OAAO,EAAE,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IAC1B,GAAG,CAAC,EAAE,GAAG,CAAC;CACX;AACD;;GAEG;AACH,MAAM,WAAW,GAAG;IAClB,CAAC,CAAC,EAAE,MAAM,GAAG,OAAO,GAAG,SAAS,CAAC;CAClC;AACD;;GAEG;AACH,MAAM,WAAW,6BAA6B;IAC5C;;OAEG;IACH,SAAS,EAAE,MAAM,CAAC;IAClB;;OAEG;IACH,MAAM,EAAE,MAAM,CAAC;IACf,GAAG,CAAC,EAAE,GAAG,CAAC;CACX;AAED,2BAA2B;AAC3B,eAAO,MAAM,QAAQ,EAAG,iDAA0D,CAAC;AAEnF,mEAAmE;AACnE,MAAM,MAAM,OAAO,GAAG,qBAAqB,CAAC;AAE5C,qEAAqE;AACrE,eAAO,MAAM,iBAAiB,EAAG,0DAAmE,CAAC;AAErG,4EAA4E;AAC5E,MAAM,MAAM,QAAQ,GAAG,6BAA6B,CAAC;AAErD;;;;GAIG;AACH,eAAO,MAAM,IAAI;;;;;CAKP,CAAC;AAEX;;;;GAIG;AACH,eAAO,MAAM,aAAa;;;;;CAKhB,CAAC"}
@@ -0,0 +1,31 @@
1
+ /**
2
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
3
+ * Source: specs/witness/session/0.1/payload.schema.json
4
+ */
5
+ /** Trust Task type URI. */
6
+ export const TYPE_URI = "https://trusttasks.org/spec/witness/session/0.1";
7
+ /** Trust Task response type URI (request type URI + "#response"). */
8
+ export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/witness/session/0.1#response";
9
+ /**
10
+ * SPEC.md §7.2 policy for the request variant, from this specification's
11
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
12
+ * per-specification and cannot be derived from the document alone.
13
+ */
14
+ export const SPEC = {
15
+ typeUri: TYPE_URI,
16
+ isBearer: false,
17
+ isProofRequired: false,
18
+ isRecipientRequired: true,
19
+ };
20
+ /**
21
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
22
+ * tracks the *issuer* party's requirement because a response swaps the
23
+ * parties (§7.3 item 5).
24
+ */
25
+ export const RESPONSE_SPEC = {
26
+ typeUri: RESPONSE_TYPE_URI,
27
+ isBearer: false,
28
+ isProofRequired: true,
29
+ isRecipientRequired: true,
30
+ };
31
+ //# sourceMappingURL=payload.js.map
@@ -0,0 +1 @@
1
+ {"version":3,"file":"payload.js","sourceRoot":"","sources":["../../../../src/witness/session/0.1/payload.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAoCH,2BAA2B;AAC3B,MAAM,CAAC,MAAM,QAAQ,GAAG,iDAA0D,CAAC;AAKnF,qEAAqE;AACrE,MAAM,CAAC,MAAM,iBAAiB,GAAG,0DAAmE,CAAC;AAKrG;;;;GAIG;AACH,MAAM,CAAC,MAAM,IAAI,GAAG;IAClB,OAAO,EAAE,QAAQ;IACjB,QAAQ,EAAE,KAAK;IACf,eAAe,EAAE,KAAK;IACtB,mBAAmB,EAAE,IAAI;CACjB,CAAC;AAEX;;;;GAIG;AACH,MAAM,CAAC,MAAM,aAAa,GAAG;IAC3B,OAAO,EAAE,iBAAiB;IAC1B,QAAQ,EAAE,KAAK;IACf,eAAe,EAAE,IAAI;IACrB,mBAAmB,EAAE,IAAI;CACjB,CAAC"}
@@ -0,0 +1,66 @@
1
+ /**
2
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
3
+ * Source: specs/witness/session/submit/0.1/payload.schema.json
4
+ */
5
+ /**
6
+ * Digest over the RFC 8785 canonicalization of the delivered credential, computed by the witness. It binds this evidence to one specific credential rather than to the session alone, so a verifier pairing a presented VWC with this response can check it is the credential this session issued and not another the same witness signed.
7
+ */
8
+ export type DigestMultibase = string;
9
+ /**
10
+ * A participating party submits its presentation bound to its session challenge; the witness's mandatory response delivers the Verifiable Witness Credential and its digest. The response is the outcome evidence a VWC presentation must ship.
11
+ */
12
+ export interface WitnessSessionSubmitPayload {
13
+ /**
14
+ * A W3C Verifiable Presentation of the submitting party's own relationship credential material (opaque here), bound to the session's challenge and domain. A presentation not bound to this session is rejected with witness/session/submit:challengeMismatch.
15
+ */
16
+ vp: {};
17
+ ext?: Ext;
18
+ }
19
+ /**
20
+ * 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.
21
+ */
22
+ export interface Ext {
23
+ [k: string]: unknown | undefined;
24
+ }
25
+ /**
26
+ * The Verifiable Witness Credential and its digest, delivered under the REQUIRED proof. This document is the session's terminal success form and the outcome evidence a VWC presentation must ship.
27
+ */
28
+ export interface WitnessSessionSubmitResponsePayload {
29
+ /**
30
+ * A signed Verifiable Witness Credential (opaque here; its schema belongs to DTG Core Credentials). Its taskContext MUST equal the id of the witness/session document that opened this session — the innermost exchange that attests the witnessing (SPEC.md §4.9.1).
31
+ */
32
+ vwc: {};
33
+ vwcDigestMultibase: DigestMultibase;
34
+ ext?: Ext;
35
+ }
36
+ /** Trust Task type URI. */
37
+ export declare const TYPE_URI: "https://trusttasks.org/spec/witness/session/submit/0.1";
38
+ /** Stable alias for this specification's request payload shape. */
39
+ export type Payload = DigestMultibase;
40
+ /** Trust Task response type URI (request type URI + "#response"). */
41
+ export declare const RESPONSE_TYPE_URI: "https://trusttasks.org/spec/witness/session/submit/0.1#response";
42
+ /** Stable alias for this specification's success-response payload shape. */
43
+ export type Response = WitnessSessionSubmitResponsePayload;
44
+ /**
45
+ * SPEC.md §7.2 policy for the request variant, from this specification's
46
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
47
+ * per-specification and cannot be derived from the document alone.
48
+ */
49
+ export declare const SPEC: {
50
+ readonly typeUri: "https://trusttasks.org/spec/witness/session/submit/0.1";
51
+ readonly isBearer: false;
52
+ readonly isProofRequired: true;
53
+ readonly isRecipientRequired: true;
54
+ };
55
+ /**
56
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
57
+ * tracks the *issuer* party's requirement because a response swaps the
58
+ * parties (§7.3 item 5).
59
+ */
60
+ export declare const RESPONSE_SPEC: {
61
+ readonly typeUri: "https://trusttasks.org/spec/witness/session/submit/0.1#response";
62
+ readonly isBearer: false;
63
+ readonly isProofRequired: true;
64
+ readonly isRecipientRequired: true;
65
+ };
66
+ //# sourceMappingURL=payload.d.ts.map
@@ -0,0 +1 @@
1
+ {"version":3,"file":"payload.d.ts","sourceRoot":"","sources":["../../../../../src/witness/session/submit/0.1/payload.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH;;GAEG;AACH,MAAM,MAAM,eAAe,GAAG,MAAM,CAAC;AAErC;;GAEG;AACH,MAAM,WAAW,2BAA2B;IAC1C;;OAEG;IACH,EAAE,EAAE,EAAE,CAAC;IACP,GAAG,CAAC,EAAE,GAAG,CAAC;CACX;AACD;;GAEG;AACH,MAAM,WAAW,GAAG;IAClB,CAAC,CAAC,EAAE,MAAM,GAAG,OAAO,GAAG,SAAS,CAAC;CAClC;AACD;;GAEG;AACH,MAAM,WAAW,mCAAmC;IAClD;;OAEG;IACH,GAAG,EAAE,EAAE,CAAC;IACR,kBAAkB,EAAE,eAAe,CAAC;IACpC,GAAG,CAAC,EAAE,GAAG,CAAC;CACX;AAED,2BAA2B;AAC3B,eAAO,MAAM,QAAQ,EAAG,wDAAiE,CAAC;AAE1F,mEAAmE;AACnE,MAAM,MAAM,OAAO,GAAG,eAAe,CAAC;AAEtC,qEAAqE;AACrE,eAAO,MAAM,iBAAiB,EAAG,iEAA0E,CAAC;AAE5G,4EAA4E;AAC5E,MAAM,MAAM,QAAQ,GAAG,mCAAmC,CAAC;AAE3D;;;;GAIG;AACH,eAAO,MAAM,IAAI;;;;;CAKP,CAAC;AAEX;;;;GAIG;AACH,eAAO,MAAM,aAAa;;;;;CAKhB,CAAC"}
@@ -0,0 +1,31 @@
1
+ /**
2
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
3
+ * Source: specs/witness/session/submit/0.1/payload.schema.json
4
+ */
5
+ /** Trust Task type URI. */
6
+ export const TYPE_URI = "https://trusttasks.org/spec/witness/session/submit/0.1";
7
+ /** Trust Task response type URI (request type URI + "#response"). */
8
+ export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/witness/session/submit/0.1#response";
9
+ /**
10
+ * SPEC.md §7.2 policy for the request variant, from this specification's
11
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
12
+ * per-specification and cannot be derived from the document alone.
13
+ */
14
+ export const SPEC = {
15
+ typeUri: TYPE_URI,
16
+ isBearer: false,
17
+ isProofRequired: true,
18
+ isRecipientRequired: true,
19
+ };
20
+ /**
21
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
22
+ * tracks the *issuer* party's requirement because a response swaps the
23
+ * parties (§7.3 item 5).
24
+ */
25
+ export const RESPONSE_SPEC = {
26
+ typeUri: RESPONSE_TYPE_URI,
27
+ isBearer: false,
28
+ isProofRequired: true,
29
+ isRecipientRequired: true,
30
+ };
31
+ //# sourceMappingURL=payload.js.map
@@ -0,0 +1 @@
1
+ {"version":3,"file":"payload.js","sourceRoot":"","sources":["../../../../../src/witness/session/submit/0.1/payload.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAmCH,2BAA2B;AAC3B,MAAM,CAAC,MAAM,QAAQ,GAAG,wDAAiE,CAAC;AAK1F,qEAAqE;AACrE,MAAM,CAAC,MAAM,iBAAiB,GAAG,iEAA0E,CAAC;AAK5G;;;;GAIG;AACH,MAAM,CAAC,MAAM,IAAI,GAAG;IAClB,OAAO,EAAE,QAAQ;IACjB,QAAQ,EAAE,KAAK;IACf,eAAe,EAAE,IAAI;IACrB,mBAAmB,EAAE,IAAI;CACjB,CAAC;AAEX;;;;GAIG;AACH,MAAM,CAAC,MAAM,aAAa,GAAG;IAC3B,OAAO,EAAE,iBAAiB;IAC1B,QAAQ,EAAE,KAAK;IACf,eAAe,EAAE,IAAI;IACrB,mBAAmB,EAAE,IAAI;CACjB,CAAC"}
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@openvtc/trust-tasks",
3
- "version": "0.6.1",
3
+ "version": "0.6.3",
4
4
  "description": "Generated TypeScript bindings for the Trust Tasks framework registry.",
5
5
  "type": "module",
6
6
  "main": "./dist/index.js",
package/src/index.ts CHANGED
@@ -236,6 +236,8 @@ export * as VaultUpsert_v0_1 from "./vault/upsert/0.1/payload.js";
236
236
  export * as VaultUpsert_v0_2 from "./vault/upsert/0.2/payload.js";
237
237
  export * as VaultUsage_v0_1 from "./vault/usage/0.1/payload.js";
238
238
  export * as VaultUsage_v0_2 from "./vault/usage/0.2/payload.js";
239
+ export * as VrcRelationshipsIssue_v0_1 from "./vrc/relationships/issue/0.1/payload.js";
240
+ export * as VrcRelationshipsPropose_v0_1 from "./vrc/relationships/propose/0.1/payload.js";
239
241
  export * as DidTemplateShared_v0_1 from "./vta/_shared/0.1/did-template.js";
240
242
  export * as PasskeyVmShared_v0_1 from "./vta/_shared/0.1/passkey-vm.js";
241
243
  export * as VtaContextsDidTemplatesCreate_v1_0 from "./vta/contexts/did-templates/create/1.0/payload.js";
@@ -337,8 +339,11 @@ export * as VtcRecognitionCheck_v0_1 from "./vtc/recognition/check/0.1/payload.j
337
339
  export * as VtcRegistryDiagnostics_v0_1 from "./vtc/registry/diagnostics/0.1/payload.js";
338
340
  export * as VtcRelationshipsGraph_v0_1 from "./vtc/relationships/graph/0.1/payload.js";
339
341
  export * as VtcRelationshipsList_v0_1 from "./vtc/relationships/list/0.1/payload.js";
342
+ export * as VtcRelationshipsList_v0_2 from "./vtc/relationships/list/0.2/payload.js";
340
343
  export * as VtcRelationshipsPublish_v0_1 from "./vtc/relationships/publish/0.1/payload.js";
344
+ export * as VtcRelationshipsPublish_v0_2 from "./vtc/relationships/publish/0.2/payload.js";
341
345
  export * as VtcRelationshipsRequest_v0_1 from "./vtc/relationships/request/0.1/payload.js";
346
+ export * as VtcRelationshipsRequest_v0_2 from "./vtc/relationships/request/0.2/payload.js";
342
347
  export * as VtcRelationshipsRevoke_v0_1 from "./vtc/relationships/revoke/0.1/payload.js";
343
348
  export * as VtcWebsiteFilesDelete_v0_1 from "./vtc/website/files/delete/0.1/payload.js";
344
349
  export * as VtcWebsiteFilesList_v0_1 from "./vtc/website/files/list/0.1/payload.js";
@@ -347,3 +352,5 @@ export * as VtcWebsiteRollback_v0_1 from "./vtc/website/rollback/0.1/payload.js"
347
352
  export * as WebvhSyncDelete_v0_1 from "./webvh/sync/delete/0.1/payload.js";
348
353
  export * as WebvhSyncUpdate_v0_1 from "./webvh/sync/update/0.1/payload.js";
349
354
  export * as WebvhWitnessPublish_v0_1 from "./webvh/witness/publish/0.1/payload.js";
355
+ export * as WitnessSession_v0_1 from "./witness/session/0.1/payload.js";
356
+ export * as WitnessSessionSubmit_v0_1 from "./witness/session/submit/0.1/payload.js";
@@ -0,0 +1,76 @@
1
+ /**
2
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
3
+ * Source: specs/vrc/relationships/issue/0.1/payload.schema.json
4
+ */
5
+
6
+ /**
7
+ * Digest over the RFC 8785 canonicalization of the credential, so the delivery can be tied to later references to it without re-hashing. A producer SHOULD set it; the receipt's own digest is what makes the round trip checkable, so a producer that omits it can still verify the delivery against the credential it holds.
8
+ */
9
+ export type DigestMultibase = string;
10
+ /**
11
+ * Digest over the RFC 8785 canonicalization of the credential AS STORED, computed by the receiving party rather than copied from the request. Computing it is the point: a copied value attests nothing, while a recomputed one makes a mismatch between what was sent and what was stored detectable in-band, and identifies which delivery this receipt answers.
12
+ */
13
+ export type DigestMultibase1 = string;
14
+
15
+ /**
16
+ * Delivers one party's signed Verifiable Relationship Credential to the other within an accepted relationship exchange. Performed once in each direction; the response is a delivery receipt naming what was stored, and does not echo the credential back.
17
+ */
18
+ export interface VRCRelationshipsIssuePayload {
19
+ /**
20
+ * A signed W3C Verifiable Relationship Credential (opaque here). Its issuer MUST be the issuing party's relationship DID and its credential subject MUST name the receiving party's relationship DID — the values the accepted proposal exchanged.
21
+ */
22
+ vrc: {};
23
+ vrcDigestMultibase?: DigestMultibase;
24
+ ext?: Ext;
25
+ }
26
+ /**
27
+ * 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.
28
+ */
29
+ export interface Ext {
30
+ [k: string]: unknown | undefined;
31
+ }
32
+ /**
33
+ * The delivery receipt: the receiving party accepted and stored the credential, and names which one. A refusal is a trust-task-error, never a receipt reporting failure.
34
+ *
35
+ * The receipt names the stored artifact rather than merely asserting that something arrived, following the delivery idiom of vtc/members/vmc and vtc/join-requests/accept. It has to: both directions of this exchange share one threadId, and a #response carries no inResponseTo, so the digest is what tells a party which of its two deliveries a receipt answers.
36
+ */
37
+ export interface VRCRelationshipsIssueResponsePayload {
38
+ vrcDigestMultibase: DigestMultibase1;
39
+ ext?: Ext;
40
+ }
41
+
42
+ /** Trust Task type URI. */
43
+ export const TYPE_URI = "https://trusttasks.org/spec/vrc/relationships/issue/0.1" as const;
44
+
45
+ /** Stable alias for this specification's request payload shape. */
46
+ export type Payload = DigestMultibase;
47
+
48
+ /** Trust Task response type URI (request type URI + "#response"). */
49
+ export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/vrc/relationships/issue/0.1#response" as const;
50
+
51
+ /** Stable alias for this specification's success-response payload shape. */
52
+ export type Response = VRCRelationshipsIssueResponsePayload;
53
+
54
+ /**
55
+ * SPEC.md §7.2 policy for the request variant, from this specification's
56
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
57
+ * per-specification and cannot be derived from the document alone.
58
+ */
59
+ export const SPEC = {
60
+ typeUri: TYPE_URI,
61
+ isBearer: false,
62
+ isProofRequired: true,
63
+ isRecipientRequired: true,
64
+ } as const;
65
+
66
+ /**
67
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
68
+ * tracks the *issuer* party's requirement because a response swaps the
69
+ * parties (§7.3 item 5).
70
+ */
71
+ export const RESPONSE_SPEC = {
72
+ typeUri: RESPONSE_TYPE_URI,
73
+ isBearer: false,
74
+ isProofRequired: false,
75
+ isRecipientRequired: true,
76
+ } as const;
@@ -0,0 +1,83 @@
1
+ /**
2
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
3
+ * Source: specs/vrc/relationships/propose/0.1/payload.schema.json
4
+ */
5
+
6
+ /**
7
+ * One person proposes a peer-to-peer relationship to another, naming the pairwise DID they will use for it. The counterparty accepts or declines; a decline is a trust-task-error carrying `vrc/relationships/propose:declined`.
8
+ */
9
+ export interface VRCRelationshipsProposePayload {
10
+ /**
11
+ * The pairwise DID the proposing party will use for this relationship. Minted for this relationship — a producer MUST NOT carry a long-term identifier here, which would make every later presentation of the resulting credentials linkable.
12
+ */
13
+ relationshipDid: string;
14
+ /**
15
+ * Whether the proposing party asks that the exchange be witnessed. A request, not a fact: it is answered by the same member on the response, and which witness and on what terms is settled under the witness/* specifications, as a separate exchange nested via parentThreadId. Absent means unwitnessed.
16
+ */
17
+ witnessed?: boolean;
18
+ /**
19
+ * Why the proposing party is asking, in their own words. A hint reaching a human; the counterparty is under no obligation to honour it and MUST NOT treat its absence as a defect.
20
+ */
21
+ reason?: string;
22
+ ext?: Ext;
23
+ }
24
+ /**
25
+ * 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.
26
+ */
27
+ export interface Ext {
28
+ [k: string]: unknown | undefined;
29
+ }
30
+ /**
31
+ * The counterparty's acceptance, and its answer on witnessing. A decline is a trust-task-error, never a response with accept: false.
32
+ */
33
+ export interface VRCRelationshipsProposeResponsePayload {
34
+ /**
35
+ * Always true: a decline travels as a trust-task-error so that refusals share one path and one set of routing rules (SPEC.md §8.1). Present so the acceptance is explicit rather than inferred from the response's existence.
36
+ */
37
+ accept: true;
38
+ /**
39
+ * The pairwise DID the counterparty will use for this relationship, under the same non-linkability obligation as the request's.
40
+ */
41
+ relationshipDid: string;
42
+ /**
43
+ * The counterparty's answer to the request's `witnessed`: true where it agrees the exchange will be witnessed. Absent or false accepts an UNWITNESSED exchange, whatever the request asked for — a counterparty unwilling to proceed unwitnessed declines instead, since this specification defines no renegotiation.
44
+ */
45
+ witnessed?: boolean;
46
+ ext?: Ext;
47
+ }
48
+
49
+ /** Trust Task type URI. */
50
+ export const TYPE_URI = "https://trusttasks.org/spec/vrc/relationships/propose/0.1" as const;
51
+
52
+ /** Stable alias for this specification's request payload shape. */
53
+ export type Payload = VRCRelationshipsProposePayload;
54
+
55
+ /** Trust Task response type URI (request type URI + "#response"). */
56
+ export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/vrc/relationships/propose/0.1#response" as const;
57
+
58
+ /** Stable alias for this specification's success-response payload shape. */
59
+ export type Response = VRCRelationshipsProposeResponsePayload;
60
+
61
+ /**
62
+ * SPEC.md §7.2 policy for the request variant, from this specification's
63
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
64
+ * per-specification and cannot be derived from the document alone.
65
+ */
66
+ export const SPEC = {
67
+ typeUri: TYPE_URI,
68
+ isBearer: false,
69
+ isProofRequired: false,
70
+ isRecipientRequired: true,
71
+ } as const;
72
+
73
+ /**
74
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
75
+ * tracks the *issuer* party's requirement because a response swaps the
76
+ * parties (§7.3 item 5).
77
+ */
78
+ export const RESPONSE_SPEC = {
79
+ typeUri: RESPONSE_TYPE_URI,
80
+ isBearer: false,
81
+ isProofRequired: false,
82
+ isRecipientRequired: true,
83
+ } as const;
@@ -0,0 +1,77 @@
1
+ /**
2
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
3
+ * Source: specs/vtc/relationships/list/0.2/payload.schema.json
4
+ */
5
+
6
+ /**
7
+ * Digest over the RFC 8785 canonicalization of the stored VRC — the value vtc/relationships/publish returned when this entry was lodged.
8
+ */
9
+ export type DigestMultibase = string;
10
+
11
+ export interface VTCRelationshipsListPayload {
12
+ /**
13
+ * The member whose relationships to list.
14
+ */
15
+ did: string;
16
+ cursor?: string;
17
+ limit?: number;
18
+ ext?: Ext;
19
+ }
20
+ /**
21
+ * 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.
22
+ */
23
+ export interface Ext {
24
+ [k: string]: unknown | undefined;
25
+ }
26
+ export interface VTCRelationshipsListResponsePayload {
27
+ items: {
28
+ id: string;
29
+ issuerDid: string;
30
+ subjectDid: string;
31
+ /**
32
+ * The relationship credential as JSON-LD (opaque here).
33
+ */
34
+ vrcJsonld: {};
35
+ vrcDigestMultibase: DigestMultibase;
36
+ createdAt: string;
37
+ }[];
38
+ nextCursor?: string | null;
39
+ totalEstimate?: number | null;
40
+ ext?: Ext;
41
+ }
42
+
43
+ /** Trust Task type URI. */
44
+ export const TYPE_URI = "https://trusttasks.org/spec/vtc/relationships/list/0.2" as const;
45
+
46
+ /** Stable alias for this specification's request payload shape. */
47
+ export type Payload = DigestMultibase;
48
+
49
+ /** Trust Task response type URI (request type URI + "#response"). */
50
+ export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/vtc/relationships/list/0.2#response" as const;
51
+
52
+ /** Stable alias for this specification's success-response payload shape. */
53
+ export type Response = VTCRelationshipsListResponsePayload;
54
+
55
+ /**
56
+ * SPEC.md §7.2 policy for the request variant, from this specification's
57
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
58
+ * per-specification and cannot be derived from the document alone.
59
+ */
60
+ export const SPEC = {
61
+ typeUri: TYPE_URI,
62
+ isBearer: false,
63
+ isProofRequired: false,
64
+ isRecipientRequired: true,
65
+ } as const;
66
+
67
+ /**
68
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
69
+ * tracks the *issuer* party's requirement because a response swaps the
70
+ * parties (§7.3 item 5).
71
+ */
72
+ export const RESPONSE_SPEC = {
73
+ typeUri: RESPONSE_TYPE_URI,
74
+ isBearer: false,
75
+ isProofRequired: false,
76
+ isRecipientRequired: true,
77
+ } as const;