@openvtc/trust-tasks 0.19.11 → 0.19.13

package/src/persona/disclosure/history/1.0/payload.ts

@@ -53,6 +53,12 @@ export interface PersonaDisclosureHistoryResponsePayload {
      * @maxItems 128
      */
     rungs?: ProofRung[];
+    /**
+     * Positionally aligned with claimTypes: whether the value the verifier received is still what this persona presents in this context. `current` — it is. `changed` — the persona now presents a different value of that type, so the verifier holds an outdated copy; this is what a re-present list is built from. `removed` — the persona no longer presents that type at all; the verifier still holds what it received, because a disclosure cannot be recalled. `unknown` — the maintainer cannot tell, as for a record made before it began fingerprinting disclosed values. Computed at read time by comparing a keyed hash of the disclosed value with the persona's current projection in the same context: no value is stored and nothing above the context boundary is read.
+     *
+     * @maxItems 128
+     */
+    claimCurrency?: ("current" | "changed" | "removed" | "unknown")[];
     purpose?: string;
     renderer?: string;
     /**
@@ -189,6 +195,20 @@ export const PAYLOAD_SCHEMA = {
                 },
                 "description": "Positionally aligned with claimTypes. A holder reviewing history needs to know not only what went but how strongly it was hidden — the same claim type at two rungs is two very different disclosures."
               },
+              "claimCurrency": {
+                "type": "array",
+                "maxItems": 128,
+                "items": {
+                  "type": "string",
+                  "enum": [
+                    "current",
+                    "changed",
+                    "removed",
+                    "unknown"
+                  ]
+                },
+                "description": "Positionally aligned with claimTypes: whether the value the verifier received is still what this persona presents in this context. `current` — it is. `changed` — the persona now presents a different value of that type, so the verifier holds an outdated copy; this is what a re-present list is built from. `removed` — the persona no longer presents that type at all; the verifier still holds what it received, because a disclosure cannot be recalled. `unknown` — the maintainer cannot tell, as for a record made before it began fingerprinting disclosed values. Computed at read time by comparing a keyed hash of the disclosed value with the persona's current projection in the same context: no value is stored and nothing above the context boundary is read."
+              },
               "purpose": {
                 "type": "string",
                 "maxLength": 512
@@ -319,6 +339,20 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
                 },
                 "description": "Positionally aligned with claimTypes. A holder reviewing history needs to know not only what went but how strongly it was hidden — the same claim type at two rungs is two very different disclosures."
               },
+              "claimCurrency": {
+                "type": "array",
+                "maxItems": 128,
+                "items": {
+                  "type": "string",
+                  "enum": [
+                    "current",
+                    "changed",
+                    "removed",
+                    "unknown"
+                  ]
+                },
+                "description": "Positionally aligned with claimTypes: whether the value the verifier received is still what this persona presents in this context. `current` — it is. `changed` — the persona now presents a different value of that type, so the verifier holds an outdated copy; this is what a re-present list is built from. `removed` — the persona no longer presents that type at all; the verifier still holds what it received, because a disclosure cannot be recalled. `unknown` — the maintainer cannot tell, as for a record made before it began fingerprinting disclosed values. Computed at read time by comparing a keyed hash of the disclosed value with the persona's current projection in the same context: no value is stored and nothing above the context boundary is read."
+              },
               "purpose": {
                 "type": "string",
                 "maxLength": 512

package/src/persona/local/binding/set/1.0/payload.ts

@@ -16,6 +16,10 @@ export interface PersonaLocalBindingSetPayload {
    * A LOCAL profile, or null to clear. A maintainer MUST refuse an identifier that names a pool profile: honouring it would let a context-scoped caller bind the holder's composition, which is the one escalation the whole boundary exists to prevent.
    */
   profileId?: Ulid | null;
+  /**
+   * What this context may call the face the persona wears here, chosen by the holder for this context. Returned by persona/binding/get and persona/binding/list in place of the holder's own name for the face, which is theirs and may say far more than they would tell a context ('the divorce'). Omit to give the context no name at all.
+   */
+  label?: string;
   expectedVersion?: ExpectedVersion;
   ext?: Ext;
 }
@@ -86,6 +90,12 @@ export const PAYLOAD_SCHEMA = {
       ],
       "description": "A LOCAL profile, or null to clear. A maintainer MUST refuse an identifier that names a pool profile: honouring it would let a context-scoped caller bind the holder's composition, which is the one escalation the whole boundary exists to prevent."
     },
+    "label": {
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 128,
+      "description": "What this context may call the face the persona wears here, chosen by the holder for this context. Returned by persona/binding/get and persona/binding/list in place of the holder's own name for the face, which is theirs and may say far more than they would tell a context ('the divorce'). Omit to give the context no name at all."
+    },
     "expectedVersion": {
       "$ref": "#/$defs/ExpectedVersion"
     },

package/src/vtc/join-requests/supplement/0.1/payload.ts

@@ -0,0 +1,369 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vtc/join-requests/supplement/0.1/payload.schema.json
+ */
+
+import type { Ext, Verdict, VerdictEffect, VerdictWith } from "../../../../_shared/components.js";
+
+
+/**
+ * The evidence an applicant offers in answer to a community's request for more, against the join request they already have open. The outer document members (id, type, issuer, recipient, issuedAt, expiresAt, proof) are owned by the framework — SPEC §6.3.
+ */
+export interface VTCJoinRequestsSupplementPayload {
+  /**
+   * The Verifiable Presentation satisfying the `presentationDefinition` the community returned when it deferred. It REPLACES the presentation on the request rather than adding to it, so it carries everything the community requires and not only the shortfall — see the spec's Definitions.
+   */
+  vp: {};
+  /**
+   * The request to supplement. OPTIONAL: an applicant whose submit response was lost never received one, and the consumer then resolves the request from the authenticated applicant. A consumer given this value MUST prefer it over inferring the request from the caller.
+   */
+  requestId?: string;
+  /**
+   * An opaque bag the community stores verbatim and this task does not interpret. Replaces the bag on the request on the same terms as `vp`.
+   */
+  extensions?: {};
+  ext?: Ext;
+}
+/**
+ * The community's fresh decision on the re-presented evidence. Failures use trust-task-error, not this shape.
+ */
+export interface VTCJoinRequestsSupplementResponsePayload {
+  /**
+   * The request that was re-decided (a UUID). Returned even when the request omitted it, so an applicant who used the id-less form learns which request they answered.
+   */
+  requestId: string;
+  /**
+   * What the community decided on the new evidence, in the same shape `vtc/join-requests/submit` returns. MAY be any outcome a submission can produce, including a further request for more evidence and including a refusal.
+   */
+  verdict: Verdict;
+  ext?: Ext;
+}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { Ext, Verdict, VerdictEffect, VerdictWith };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/vtc/join-requests/supplement/0.1" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = VTCJoinRequestsSupplementPayload;
+
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/vtc/join-requests/supplement/0.1#response" as const;
+
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = VTCJoinRequestsSupplementResponsePayload;
+
+/**
+ * This specification's payload schema, as a value.
+ *
+ * SPEC.md §7.2 item 2 is performed against this. It is shipped as data
+ * rather than only as a `.json` file because TypeScript types are erased
+ * at runtime: without a schema a consumer has nothing to validate, and
+ * every REQUIRED payload member is optional in practice. Cross-file
+ * `$ref`s are already inlined, so it needs no resolver.
+ */
+export const PAYLOAD_SCHEMA = {
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://trusttasks.org/spec/vtc/join-requests/supplement/0.1",
+  "title": "VTC Join-Requests Supplement — payload",
+  "description": "The evidence an applicant offers in answer to a community's request for more, against the join request they already have open. The outer document members (id, type, issuer, recipient, issuedAt, expiresAt, proof) are owned by the framework — SPEC §6.3.",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "vp"
+  ],
+  "properties": {
+    "vp": {
+      "type": "object",
+      "description": "The Verifiable Presentation satisfying the `presentationDefinition` the community returned when it deferred. It REPLACES the presentation on the request rather than adding to it, so it carries everything the community requires and not only the shortfall — see the spec's Definitions."
+    },
+    "requestId": {
+      "type": "string",
+      "minLength": 1,
+      "description": "The request to supplement. OPTIONAL: an applicant whose submit response was lost never received one, and the consumer then resolves the request from the authenticated applicant. A consumer given this value MUST prefer it over inferring the request from the caller."
+    },
+    "extensions": {
+      "type": "object",
+      "description": "An opaque bag the community stores verbatim and this task does not interpret. Replaces the bag on the request on the same terms as `vp`."
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext"
+    }
+  },
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "VTC Join-Requests Supplement — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "requestId",
+        "verdict"
+      ],
+      "description": "The community's fresh decision on the re-presented evidence. Failures use trust-task-error, not this shape.",
+      "properties": {
+        "requestId": {
+          "type": "string",
+          "minLength": 1,
+          "description": "The request that was re-decided (a UUID). Returned even when the request omitted it, so an applicant who used the id-less form learns which request they answered."
+        },
+        "verdict": {
+          "$ref": "#/$defs/Verdict",
+          "description": "What the community decided on the new evidence, in the same shape `vtc/join-requests/submit` returns. MAY be any outcome a submission can produce, including a further request for more evidence and including a refusal."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext"
+        }
+      }
+    },
+    "Ext": {
+      "title": "Ext",
+      "description": "Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a reverse-DNS namespace; structure under each namespace is opaque to the framework.",
+      "type": "object",
+      "minProperties": 1,
+      "additionalProperties": true,
+      "propertyNames": {
+        "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
+      }
+    },
+    "Verdict": {
+      "$anchor": "verdict",
+      "title": "Verdict",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "effect",
+        "with"
+      ],
+      "description": "A ceremony decision: the effect, plus its effect-dependent detail.",
+      "properties": {
+        "effect": {
+          "$ref": "#/$defs/VerdictEffect"
+        },
+        "with": {
+          "$ref": "#/$defs/VerdictWith"
+        }
+      }
+    },
+    "VerdictWith": {
+      "$anchor": "verdictWith",
+      "title": "VerdictWith",
+      "type": "object",
+      "additionalProperties": false,
+      "description": "The effect-dependent detail of a verdict.\n\nEvery member is optional at the schema level and which ones are meaningful depends on `effect`: `role` / `obligations` / `bundleRef` on `allow`, `code` / `reason` on `deny`, `queue` / `reason` on `refer`, `needs` / `presentationDefinition` on `requestMore`. The dependency is stated here rather than enforced by `if`/`then` per effect, so that the shape stays a single flat object a generated type can carry without a discriminated union per family — a deliberate trade of schema strictness for implementability, and the reason a consumer MUST branch on `effect` rather than on which members happen to be present.",
+      "properties": {
+        "role": {
+          "type": "string",
+          "minLength": 1,
+          "description": "The granted local role. `allow` only."
+        },
+        "obligations": {
+          "type": "object",
+          "description": "Conditions attached to the grant. `allow` only."
+        },
+        "bundleRef": {
+          "type": "object",
+          "description": "Pointer to a sealed credential bundle, added by the community where issuance occurred rather than emitted by the policy. `allow` only."
+        },
+        "code": {
+          "type": "string",
+          "minLength": 1,
+          "description": "Stable refusal code, safe to branch on. `deny` only."
+        },
+        "reason": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "maxLength": 1024,
+          "description": "Elaboration in prose, when the decider gave one. `deny` and `refer`."
+        },
+        "queue": {
+          "type": "string",
+          "minLength": 1,
+          "description": "Which review queue the decision was parked in, so an applicant can be told who now holds it. `refer` only."
+        },
+        "needs": {
+          "type": "array",
+          "items": {
+            "type": "string",
+            "minLength": 1
+          },
+          "description": "What further evidence is required, named so the applicant can act without a support conversation. `requestMore` only."
+        },
+        "presentationDefinition": {
+          "type": "object",
+          "description": "A machine-readable statement of the same request, so a wallet can satisfy it without a human reading `needs`. `requestMore` only."
+        }
+      }
+    },
+    "VerdictEffect": {
+      "$anchor": "verdictEffect",
+      "title": "VerdictEffect",
+      "type": "string",
+      "enum": [
+        "allow",
+        "deny",
+        "refer",
+        "requestMore"
+      ],
+      "description": "What the policy decided.\n\n`allow` — admitted. `deny` — refused, terminally for this submission. `refer` — parked for a human or quorum decision; the applicant is neither in nor out. `requestMore` — the policy cannot decide yet and names what further evidence it needs.\n\nThe four are not reducible to a pending/decided pair. `refer` and `requestMore` are both 'not decided', but they place the next action with different parties: `refer` waits on the community, `requestMore` waits on the applicant. A consumer that cannot tell them apart cannot tell a user whether to wait or to act."
+    }
+  }
+} as const;
+
+/** As {@link PAYLOAD_SCHEMA}, for the success-response variant. */
+export const RESPONSE_PAYLOAD_SCHEMA = {
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$ref": "#/$defs/Response",
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "VTC Join-Requests Supplement — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "requestId",
+        "verdict"
+      ],
+      "description": "The community's fresh decision on the re-presented evidence. Failures use trust-task-error, not this shape.",
+      "properties": {
+        "requestId": {
+          "type": "string",
+          "minLength": 1,
+          "description": "The request that was re-decided (a UUID). Returned even when the request omitted it, so an applicant who used the id-less form learns which request they answered."
+        },
+        "verdict": {
+          "$ref": "#/$defs/Verdict",
+          "description": "What the community decided on the new evidence, in the same shape `vtc/join-requests/submit` returns. MAY be any outcome a submission can produce, including a further request for more evidence and including a refusal."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext"
+        }
+      }
+    },
+    "Ext": {
+      "title": "Ext",
+      "description": "Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a reverse-DNS namespace; structure under each namespace is opaque to the framework.",
+      "type": "object",
+      "minProperties": 1,
+      "additionalProperties": true,
+      "propertyNames": {
+        "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
+      }
+    },
+    "Verdict": {
+      "$anchor": "verdict",
+      "title": "Verdict",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "effect",
+        "with"
+      ],
+      "description": "A ceremony decision: the effect, plus its effect-dependent detail.",
+      "properties": {
+        "effect": {
+          "$ref": "#/$defs/VerdictEffect"
+        },
+        "with": {
+          "$ref": "#/$defs/VerdictWith"
+        }
+      }
+    },
+    "VerdictWith": {
+      "$anchor": "verdictWith",
+      "title": "VerdictWith",
+      "type": "object",
+      "additionalProperties": false,
+      "description": "The effect-dependent detail of a verdict.\n\nEvery member is optional at the schema level and which ones are meaningful depends on `effect`: `role` / `obligations` / `bundleRef` on `allow`, `code` / `reason` on `deny`, `queue` / `reason` on `refer`, `needs` / `presentationDefinition` on `requestMore`. The dependency is stated here rather than enforced by `if`/`then` per effect, so that the shape stays a single flat object a generated type can carry without a discriminated union per family — a deliberate trade of schema strictness for implementability, and the reason a consumer MUST branch on `effect` rather than on which members happen to be present.",
+      "properties": {
+        "role": {
+          "type": "string",
+          "minLength": 1,
+          "description": "The granted local role. `allow` only."
+        },
+        "obligations": {
+          "type": "object",
+          "description": "Conditions attached to the grant. `allow` only."
+        },
+        "bundleRef": {
+          "type": "object",
+          "description": "Pointer to a sealed credential bundle, added by the community where issuance occurred rather than emitted by the policy. `allow` only."
+        },
+        "code": {
+          "type": "string",
+          "minLength": 1,
+          "description": "Stable refusal code, safe to branch on. `deny` only."
+        },
+        "reason": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "maxLength": 1024,
+          "description": "Elaboration in prose, when the decider gave one. `deny` and `refer`."
+        },
+        "queue": {
+          "type": "string",
+          "minLength": 1,
+          "description": "Which review queue the decision was parked in, so an applicant can be told who now holds it. `refer` only."
+        },
+        "needs": {
+          "type": "array",
+          "items": {
+            "type": "string",
+            "minLength": 1
+          },
+          "description": "What further evidence is required, named so the applicant can act without a support conversation. `requestMore` only."
+        },
+        "presentationDefinition": {
+          "type": "object",
+          "description": "A machine-readable statement of the same request, so a wallet can satisfy it without a human reading `needs`. `requestMore` only."
+        }
+      }
+    },
+    "VerdictEffect": {
+      "$anchor": "verdictEffect",
+      "title": "VerdictEffect",
+      "type": "string",
+      "enum": [
+        "allow",
+        "deny",
+        "refer",
+        "requestMore"
+      ],
+      "description": "What the policy decided.\n\n`allow` — admitted. `deny` — refused, terminally for this submission. `refer` — parked for a human or quorum decision; the applicant is neither in nor out. `requestMore` — the policy cannot decide yet and names what further evidence it needs.\n\nThe four are not reducible to a pending/decided pair. `refer` and `requestMore` are both 'not decided', but they place the next action with different parties: `refer` waits on the community, `requestMore` waits on the applicant. A consumer that cannot tell them apart cannot tell a user whether to wait or to act."
+    }
+  }
+} as const;
+
+/**
+ * SPEC.md §7.2 policy for the request variant, from this specification's
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
+ * per-specification and cannot be derived from the document alone, and
+ * item 2 needs the schema this carries.
+ */
+export const SPEC = {
+  typeUri: TYPE_URI,
+  isBearer: false,
+  isProofRequired: true,
+  isRecipientRequired: true,
+  isIssuedAtRequired: true,
+  payloadSchema: PAYLOAD_SCHEMA,
+} as const;
+
+/**
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
+ * tracks the *issuer* party's requirement because a response swaps the
+ * parties (§7.3 item 5).
+ */
+export const RESPONSE_SPEC = {
+  typeUri: RESPONSE_TYPE_URI,
+  isBearer: false,
+  isProofRequired: false,
+  isRecipientRequired: true,
+  isIssuedAtRequired: true,
+  payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
+} as const;