@openvtc/trust-tasks 0.19.22 → 0.20.1

package/src/persona/correlation/analyze/1.1/payload.ts

@@ -0,0 +1,514 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/persona/correlation/analyze/1.1/payload.schema.json
+ */
+
+import type { ClaimType, Ext, Ulid, ValueType } from "../../../../_shared/components.js";
+
+
+/**
+ * Report where the holder's identities link to one another, and what can be done about each link. The findings task behind the counts the write tasks return.
+ */
+export interface PersonaCorrelationAnalyzePayload {
+  /**
+   * Analyse one attribute. Omit to analyse the whole pool.
+   */
+  attributeId?: Ulid;
+  /**
+   * Analyse one composition — what would this profile link if bound.
+   */
+  profileId?: Ulid;
+  /**
+   * Analyse a value the holder is CONSIDERING but has not written. This is what lets a builder warn before the mistake rather than after it, which is the difference between a guard and a report. A maintainer MUST NOT store a candidate.
+   */
+  candidate?: {
+    type: ClaimType;
+    valueType: ValueType;
+    value: unknown;
+  };
+  ext?: Ext;
+}
+/**
+ * Success response to persona/correlation/analyze. Type https://trusttasks.org/spec/persona/correlation/analyze/1.0#response.
+ */
+export interface PersonaCorrelationAnalyzeResponsePayload {
+  /**
+   * @maxItems 256
+   */
+  findings: {
+    attributeId?: Ulid;
+    severity: "low" | "high";
+    /**
+     * Where else this value appears, and where it has actually gone. Identifiers ARE returned here, unlike the counts the write tasks give back — this task is holder-authorized and its whole purpose is to let the holder act, which they cannot do on a number.
+     *
+     * @maxItems 128
+     */
+    sharedWith?: {
+      profileId?: Ulid;
+      contextId?: string;
+      personaDid?: string;
+      /**
+       * @maxItems 64
+       */
+      disclosedTo?: string[];
+      /**
+       * The world the profile at this location belongs to. Absent where it belongs to none, which is a real and common state rather than a gap — most profiles are unarranged until someone arranges them, and a consumer MUST NOT read absence as a world of its own.
+       */
+      worldId?: Ulid;
+    }[];
+    /**
+     * Plain-language cause. A severity with no explanation is a warning a holder learns to dismiss.
+     */
+    why: string;
+    /**
+     * What the holder can actually do. Naming reissueCredentialToThisDid matters more than it looks: without it, a holder told 'this links your personas' has no action but to abandon the attribute, and the honest fix — a credential re-issued against the persona actually using it — stays invisible unless the analysis names it.
+     *
+     * @maxItems 8
+     */
+    remedies:
+      | []
+      | ["useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord"]
+      | [
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord"
+        ]
+      | [
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord"
+        ]
+      | [
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord"
+        ]
+      | [
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord"
+        ]
+      | [
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord"
+        ]
+      | [
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord"
+        ]
+      | [
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord",
+          "useDifferentValue" | "reissueCredentialToThisDid" | "correlateDeliberately" | "proceedAndRecord"
+        ];
+    /**
+     * Whether this linkage spans two or more of the holder's worlds — parts of their life they have said belong apart. **A second axis, not a restatement of `severity`.** `severity` says how strongly a disclosure would link the holder, which is a fact about provenance and proof rung and is true whatever the holder intended; this says whether the holder would mind. A value shared between two profiles in the SAME world is linkage the holder arranged on purpose — a work email in every work profile — and a consumer that alarmed on it teaches people to dismiss the alarm. A value shared ACROSS worlds is the finding worth raising. True only when two or more DISTINCT worlds appear among `sharedWith`: a profile belonging to no world is unarranged, not a second world, and contributes nothing here. Absent when the maintainer does not implement worlds.
+     */
+    crossesWorlds?: boolean;
+    /**
+     * The distinct worlds this linkage touches, so a consumer can name them — "Work and Home share your mobile number" is a sentence a holder can act on, where "a value is shared" is not. Identifiers rather than names, on the same reasoning as every other member here: the caller already holds the world records and a name repeated on the wire is a second copy to keep correct.
+     *
+     * @maxItems 64
+     */
+    worldIds?: Ulid[];
+  }[];
+  ext?: Ext;
+}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { ClaimType, Ext, Ulid, ValueType };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/persona/correlation/analyze/1.1" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = PersonaCorrelationAnalyzePayload;
+
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/persona/correlation/analyze/1.1#response" as const;
+
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = PersonaCorrelationAnalyzeResponsePayload;
+
+/**
+ * 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/persona/correlation/analyze/1.1",
+  "title": "Persona Correlation Analyze — payload",
+  "description": "Report where the holder's identities link to one another, and what can be done about each link. The findings task behind the counts the write tasks return.",
+  "type": "object",
+  "additionalProperties": false,
+  "properties": {
+    "attributeId": {
+      "$ref": "#/$defs/Ulid",
+      "description": "Analyse one attribute. Omit to analyse the whole pool."
+    },
+    "profileId": {
+      "$ref": "#/$defs/Ulid",
+      "description": "Analyse one composition — what would this profile link if bound."
+    },
+    "candidate": {
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "type",
+        "valueType",
+        "value"
+      ],
+      "description": "Analyse a value the holder is CONSIDERING but has not written. This is what lets a builder warn before the mistake rather than after it, which is the difference between a guard and a report. A maintainer MUST NOT store a candidate.",
+      "properties": {
+        "type": {
+          "$ref": "#/$defs/ClaimType"
+        },
+        "valueType": {
+          "$ref": "#/$defs/ValueType"
+        },
+        "value": {}
+      }
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext"
+    }
+  },
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "Persona Correlation Analyze — response payload",
+      "description": "Success response to persona/correlation/analyze. Type https://trusttasks.org/spec/persona/correlation/analyze/1.0#response.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "findings"
+      ],
+      "properties": {
+        "findings": {
+          "type": "array",
+          "maxItems": 256,
+          "items": {
+            "type": "object",
+            "additionalProperties": false,
+            "required": [
+              "severity",
+              "why",
+              "remedies"
+            ],
+            "properties": {
+              "attributeId": {
+                "$ref": "#/$defs/Ulid"
+              },
+              "severity": {
+                "type": "string",
+                "enum": [
+                  "low",
+                  "high"
+                ]
+              },
+              "sharedWith": {
+                "type": "array",
+                "maxItems": 128,
+                "description": "Where else this value appears, and where it has actually gone. Identifiers ARE returned here, unlike the counts the write tasks give back — this task is holder-authorized and its whole purpose is to let the holder act, which they cannot do on a number.",
+                "items": {
+                  "type": "object",
+                  "additionalProperties": false,
+                  "properties": {
+                    "profileId": {
+                      "$ref": "#/$defs/Ulid"
+                    },
+                    "contextId": {
+                      "type": "string"
+                    },
+                    "personaDid": {
+                      "type": "string"
+                    },
+                    "disclosedTo": {
+                      "type": "array",
+                      "maxItems": 64,
+                      "items": {
+                        "type": "string"
+                      }
+                    },
+                    "worldId": {
+                      "$ref": "#/$defs/Ulid",
+                      "description": "The world the profile at this location belongs to. Absent where it belongs to none, which is a real and common state rather than a gap — most profiles are unarranged until someone arranges them, and a consumer MUST NOT read absence as a world of its own."
+                    }
+                  }
+                }
+              },
+              "why": {
+                "type": "string",
+                "maxLength": 1024,
+                "description": "Plain-language cause. A severity with no explanation is a warning a holder learns to dismiss."
+              },
+              "remedies": {
+                "type": "array",
+                "maxItems": 8,
+                "items": {
+                  "type": "string",
+                  "enum": [
+                    "useDifferentValue",
+                    "reissueCredentialToThisDid",
+                    "correlateDeliberately",
+                    "proceedAndRecord"
+                  ]
+                },
+                "description": "What the holder can actually do. Naming reissueCredentialToThisDid matters more than it looks: without it, a holder told 'this links your personas' has no action but to abandon the attribute, and the honest fix — a credential re-issued against the persona actually using it — stays invisible unless the analysis names it."
+              },
+              "crossesWorlds": {
+                "type": "boolean",
+                "description": "Whether this linkage spans two or more of the holder's worlds — parts of their life they have said belong apart. **A second axis, not a restatement of `severity`.** `severity` says how strongly a disclosure would link the holder, which is a fact about provenance and proof rung and is true whatever the holder intended; this says whether the holder would mind. A value shared between two profiles in the SAME world is linkage the holder arranged on purpose — a work email in every work profile — and a consumer that alarmed on it teaches people to dismiss the alarm. A value shared ACROSS worlds is the finding worth raising. True only when two or more DISTINCT worlds appear among `sharedWith`: a profile belonging to no world is unarranged, not a second world, and contributes nothing here. Absent when the maintainer does not implement worlds."
+              },
+              "worldIds": {
+                "type": "array",
+                "maxItems": 64,
+                "uniqueItems": true,
+                "items": {
+                  "$ref": "#/$defs/Ulid"
+                },
+                "description": "The distinct worlds this linkage touches, so a consumer can name them — \"Work and Home share your mobile number\" is a sentence a holder can act on, where \"a value is shared\" is not. Identifiers rather than names, on the same reasoning as every other member here: the caller already holds the world records and a name repeated on the wire is a second copy to keep correct."
+              }
+            }
+          }
+        },
+        "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-]+)+$"
+      }
+    },
+    "Ulid": {
+      "title": "Ulid",
+      "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.",
+      "type": "string",
+      "pattern": "^[0-9A-HJKMNP-TV-Z]{26}$"
+    },
+    "ValueType": {
+      "title": "ValueType",
+      "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.",
+      "type": "string",
+      "enum": [
+        "string",
+        "number",
+        "boolean",
+        "date",
+        "object"
+      ]
+    },
+    "ClaimType": {
+      "title": "ClaimType",
+      "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.",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 128,
+      "pattern": "^(x:)?[a-z][a-zA-Z0-9]*(\\.[a-z][a-zA-Z0-9]*)*$"
+    }
+  }
+} 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": "Persona Correlation Analyze — response payload",
+      "description": "Success response to persona/correlation/analyze. Type https://trusttasks.org/spec/persona/correlation/analyze/1.0#response.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "findings"
+      ],
+      "properties": {
+        "findings": {
+          "type": "array",
+          "maxItems": 256,
+          "items": {
+            "type": "object",
+            "additionalProperties": false,
+            "required": [
+              "severity",
+              "why",
+              "remedies"
+            ],
+            "properties": {
+              "attributeId": {
+                "$ref": "#/$defs/Ulid"
+              },
+              "severity": {
+                "type": "string",
+                "enum": [
+                  "low",
+                  "high"
+                ]
+              },
+              "sharedWith": {
+                "type": "array",
+                "maxItems": 128,
+                "description": "Where else this value appears, and where it has actually gone. Identifiers ARE returned here, unlike the counts the write tasks give back — this task is holder-authorized and its whole purpose is to let the holder act, which they cannot do on a number.",
+                "items": {
+                  "type": "object",
+                  "additionalProperties": false,
+                  "properties": {
+                    "profileId": {
+                      "$ref": "#/$defs/Ulid"
+                    },
+                    "contextId": {
+                      "type": "string"
+                    },
+                    "personaDid": {
+                      "type": "string"
+                    },
+                    "disclosedTo": {
+                      "type": "array",
+                      "maxItems": 64,
+                      "items": {
+                        "type": "string"
+                      }
+                    },
+                    "worldId": {
+                      "$ref": "#/$defs/Ulid",
+                      "description": "The world the profile at this location belongs to. Absent where it belongs to none, which is a real and common state rather than a gap — most profiles are unarranged until someone arranges them, and a consumer MUST NOT read absence as a world of its own."
+                    }
+                  }
+                }
+              },
+              "why": {
+                "type": "string",
+                "maxLength": 1024,
+                "description": "Plain-language cause. A severity with no explanation is a warning a holder learns to dismiss."
+              },
+              "remedies": {
+                "type": "array",
+                "maxItems": 8,
+                "items": {
+                  "type": "string",
+                  "enum": [
+                    "useDifferentValue",
+                    "reissueCredentialToThisDid",
+                    "correlateDeliberately",
+                    "proceedAndRecord"
+                  ]
+                },
+                "description": "What the holder can actually do. Naming reissueCredentialToThisDid matters more than it looks: without it, a holder told 'this links your personas' has no action but to abandon the attribute, and the honest fix — a credential re-issued against the persona actually using it — stays invisible unless the analysis names it."
+              },
+              "crossesWorlds": {
+                "type": "boolean",
+                "description": "Whether this linkage spans two or more of the holder's worlds — parts of their life they have said belong apart. **A second axis, not a restatement of `severity`.** `severity` says how strongly a disclosure would link the holder, which is a fact about provenance and proof rung and is true whatever the holder intended; this says whether the holder would mind. A value shared between two profiles in the SAME world is linkage the holder arranged on purpose — a work email in every work profile — and a consumer that alarmed on it teaches people to dismiss the alarm. A value shared ACROSS worlds is the finding worth raising. True only when two or more DISTINCT worlds appear among `sharedWith`: a profile belonging to no world is unarranged, not a second world, and contributes nothing here. Absent when the maintainer does not implement worlds."
+              },
+              "worldIds": {
+                "type": "array",
+                "maxItems": 64,
+                "uniqueItems": true,
+                "items": {
+                  "$ref": "#/$defs/Ulid"
+                },
+                "description": "The distinct worlds this linkage touches, so a consumer can name them — \"Work and Home share your mobile number\" is a sentence a holder can act on, where \"a value is shared\" is not. Identifiers rather than names, on the same reasoning as every other member here: the caller already holds the world records and a name repeated on the wire is a second copy to keep correct."
+              }
+            }
+          }
+        },
+        "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-]+)+$"
+      }
+    },
+    "Ulid": {
+      "title": "Ulid",
+      "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.",
+      "type": "string",
+      "pattern": "^[0-9A-HJKMNP-TV-Z]{26}$"
+    },
+    "ValueType": {
+      "title": "ValueType",
+      "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.",
+      "type": "string",
+      "enum": [
+        "string",
+        "number",
+        "boolean",
+        "date",
+        "object"
+      ]
+    },
+    "ClaimType": {
+      "title": "ClaimType",
+      "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.",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 128,
+      "pattern": "^(x:)?[a-z][a-zA-Z0-9]*(\\.[a-z][a-zA-Z0-9]*)*$"
+    }
+  }
+} 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: false,
+  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: true,
+  isRecipientRequired: true,
+  isIssuedAtRequired: false,
+  payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
+} as const;

package/src/persona/facet/list/1.0/payload.ts

@@ -212,7 +212,7 @@ export const PAYLOAD_SCHEMA = {
     },
     "FacetColour": {
       "title": "FacetColour",
-      "description": "A colour **name**, resolved by each consumer against its own palette — never a hex value or any other literal. Two reasons, and both are about the consumer rather than the holder. A literal cannot be legible in a terminal, in a light theme and in a dark one at once, so a stored `#8B0000` is a colour that is wrong somewhere and the holder has no way to know where. And a consumer that reserves colours to mean something — an error, a warning, an irreversible act — must be able to keep a holder's decorative choice out of that channel; it cannot do that with an arbitrary value, and it can do it trivially with a closed set it maps itself. The eight members are chosen to be distinguishable from one another and deliberately carry no status connotation: none is named for success, warning or danger.",
+      "description": "**Superseded by `WorldColour`** — the same set, under the name the rest of the family now uses. Retained because `persona/facet/*` is retired in favour of `persona/world/*`, and a retired specification's schema is frozen, so the definition it references has to stay. New work references `WorldColour`. A colour **name**, resolved by each consumer against its own palette — never a hex value or any other literal. Two reasons, and both are about the consumer rather than the holder. A literal cannot be legible in a terminal, in a light theme and in a dark one at once, so a stored `#8B0000` is a colour that is wrong somewhere and the holder has no way to know where. And a consumer that reserves colours to mean something — an error, a warning, an irreversible act — must be able to keep a holder's decorative choice out of that channel; it cannot do that with an arbitrary value, and it can do it trivially with a closed set it maps itself. The eight members are chosen to be distinguishable from one another and deliberately carry no status connotation: none is named for success, warning or danger.",
       "type": "string",
       "enum": [
         "slate",
@@ -346,7 +346,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
     },
     "FacetColour": {
       "title": "FacetColour",
-      "description": "A colour **name**, resolved by each consumer against its own palette — never a hex value or any other literal. Two reasons, and both are about the consumer rather than the holder. A literal cannot be legible in a terminal, in a light theme and in a dark one at once, so a stored `#8B0000` is a colour that is wrong somewhere and the holder has no way to know where. And a consumer that reserves colours to mean something — an error, a warning, an irreversible act — must be able to keep a holder's decorative choice out of that channel; it cannot do that with an arbitrary value, and it can do it trivially with a closed set it maps itself. The eight members are chosen to be distinguishable from one another and deliberately carry no status connotation: none is named for success, warning or danger.",
+      "description": "**Superseded by `WorldColour`** — the same set, under the name the rest of the family now uses. Retained because `persona/facet/*` is retired in favour of `persona/world/*`, and a retired specification's schema is frozen, so the definition it references has to stay. New work references `WorldColour`. A colour **name**, resolved by each consumer against its own palette — never a hex value or any other literal. Two reasons, and both are about the consumer rather than the holder. A literal cannot be legible in a terminal, in a light theme and in a dark one at once, so a stored `#8B0000` is a colour that is wrong somewhere and the holder has no way to know where. And a consumer that reserves colours to mean something — an error, a warning, an irreversible act — must be able to keep a holder's decorative choice out of that channel; it cannot do that with an arbitrary value, and it can do it trivially with a closed set it maps itself. The eight members are chosen to be distinguishable from one another and deliberately carry no status connotation: none is named for success, warning or danger.",
       "type": "string",
       "enum": [
         "slate",

package/src/persona/facet/put/1.0/payload.ts

@@ -206,7 +206,7 @@ export const PAYLOAD_SCHEMA = {
     },
     "FacetColour": {
       "title": "FacetColour",
-      "description": "A colour **name**, resolved by each consumer against its own palette — never a hex value or any other literal. Two reasons, and both are about the consumer rather than the holder. A literal cannot be legible in a terminal, in a light theme and in a dark one at once, so a stored `#8B0000` is a colour that is wrong somewhere and the holder has no way to know where. And a consumer that reserves colours to mean something — an error, a warning, an irreversible act — must be able to keep a holder's decorative choice out of that channel; it cannot do that with an arbitrary value, and it can do it trivially with a closed set it maps itself. The eight members are chosen to be distinguishable from one another and deliberately carry no status connotation: none is named for success, warning or danger.",
+      "description": "**Superseded by `WorldColour`** — the same set, under the name the rest of the family now uses. Retained because `persona/facet/*` is retired in favour of `persona/world/*`, and a retired specification's schema is frozen, so the definition it references has to stay. New work references `WorldColour`. A colour **name**, resolved by each consumer against its own palette — never a hex value or any other literal. Two reasons, and both are about the consumer rather than the holder. A literal cannot be legible in a terminal, in a light theme and in a dark one at once, so a stored `#8B0000` is a colour that is wrong somewhere and the holder has no way to know where. And a consumer that reserves colours to mean something — an error, a warning, an irreversible act — must be able to keep a holder's decorative choice out of that channel; it cannot do that with an arbitrary value, and it can do it trivially with a closed set it maps itself. The eight members are chosen to be distinguishable from one another and deliberately carry no status connotation: none is named for success, warning or danger.",
       "type": "string",
       "enum": [
         "slate",
@@ -293,7 +293,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
     },
     "FacetColour": {
       "title": "FacetColour",
-      "description": "A colour **name**, resolved by each consumer against its own palette — never a hex value or any other literal. Two reasons, and both are about the consumer rather than the holder. A literal cannot be legible in a terminal, in a light theme and in a dark one at once, so a stored `#8B0000` is a colour that is wrong somewhere and the holder has no way to know where. And a consumer that reserves colours to mean something — an error, a warning, an irreversible act — must be able to keep a holder's decorative choice out of that channel; it cannot do that with an arbitrary value, and it can do it trivially with a closed set it maps itself. The eight members are chosen to be distinguishable from one another and deliberately carry no status connotation: none is named for success, warning or danger.",
+      "description": "**Superseded by `WorldColour`** — the same set, under the name the rest of the family now uses. Retained because `persona/facet/*` is retired in favour of `persona/world/*`, and a retired specification's schema is frozen, so the definition it references has to stay. New work references `WorldColour`. A colour **name**, resolved by each consumer against its own palette — never a hex value or any other literal. Two reasons, and both are about the consumer rather than the holder. A literal cannot be legible in a terminal, in a light theme and in a dark one at once, so a stored `#8B0000` is a colour that is wrong somewhere and the holder has no way to know where. And a consumer that reserves colours to mean something — an error, a warning, an irreversible act — must be able to keep a holder's decorative choice out of that channel; it cannot do that with an arbitrary value, and it can do it trivially with a closed set it maps itself. The eight members are chosen to be distinguishable from one another and deliberately carry no status connotation: none is named for success, warning or danger.",
       "type": "string",
       "enum": [
         "slate",

package/src/persona/local/profile/put/1.0/payload.ts

@@ -45,12 +45,12 @@ export interface PersonaLocalProfilePutResponsePayload {
   version: Version;
   created: boolean;
   /**
-   * Local profiles ARE correlation-indexed, and the naive implementation that skips them loses the guard exactly where a human most needs it: a throwaway identity is precisely where somebody reuses a real value. Indexing them is not a leak — the index is above the boundary, is keyed by a hash, and only the holder can query it.
+   * A correlation assessment of what was just written, and it is **conditional**: a maintainer MUST include it only for a caller authorized to read across the holder's contexts, and MUST omit it entirely otherwise. Local profiles ARE correlation-indexed, and the naive implementation that skips them loses the guard exactly where a human most needs it: a throwaway identity is precisely where somebody reuses a real value. But the index is answerable only to the holder, and returning its answer to a context-scoped caller hands that caller a yes/no oracle on any value it cares to guess — one guess per write, against the whole pool. No value leaves either way; a confirmed guess at a low-entropy value (a name, an address, a date of birth) is disclosure all the same.
    */
   correlation?: {
     severity: "none" | "low" | "high";
     /**
-     * True when a value here also appears in the holder's pool. The signal that a throwaway is not throwaway.
+     * True when a value here also appears in the holder's pool — the signal that a throwaway is not throwaway. Present only under the condition on `correlation` itself: this member is the oracle, and a maintainer that omits `correlation` for a context-scoped caller has omitted this.
      */
     matchesPoolValue?: boolean;
   };
@@ -181,7 +181,7 @@ export const PAYLOAD_SCHEMA = {
           "required": [
             "severity"
           ],
-          "description": "Local profiles ARE correlation-indexed, and the naive implementation that skips them loses the guard exactly where a human most needs it: a throwaway identity is precisely where somebody reuses a real value. Indexing them is not a leak — the index is above the boundary, is keyed by a hash, and only the holder can query it.",
+          "description": "A correlation assessment of what was just written, and it is **conditional**: a maintainer MUST include it only for a caller authorized to read across the holder's contexts, and MUST omit it entirely otherwise. Local profiles ARE correlation-indexed, and the naive implementation that skips them loses the guard exactly where a human most needs it: a throwaway identity is precisely where somebody reuses a real value. But the index is answerable only to the holder, and returning its answer to a context-scoped caller hands that caller a yes/no oracle on any value it cares to guess — one guess per write, against the whole pool. No value leaves either way; a confirmed guess at a low-entropy value (a name, an address, a date of birth) is disclosure all the same.",
           "properties": {
             "severity": {
               "type": "string",
@@ -193,7 +193,7 @@ export const PAYLOAD_SCHEMA = {
             },
             "matchesPoolValue": {
               "type": "boolean",
-              "description": "True when a value here also appears in the holder's pool. The signal that a throwaway is not throwaway."
+              "description": "True when a value here also appears in the holder's pool — the signal that a throwaway is not throwaway. Present only under the condition on `correlation` itself: this member is the oracle, and a maintainer that omits `correlation` for a context-scoped caller has omitted this."
             }
           }
         },
@@ -291,7 +291,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
           "required": [
             "severity"
           ],
-          "description": "Local profiles ARE correlation-indexed, and the naive implementation that skips them loses the guard exactly where a human most needs it: a throwaway identity is precisely where somebody reuses a real value. Indexing them is not a leak — the index is above the boundary, is keyed by a hash, and only the holder can query it.",
+          "description": "A correlation assessment of what was just written, and it is **conditional**: a maintainer MUST include it only for a caller authorized to read across the holder's contexts, and MUST omit it entirely otherwise. Local profiles ARE correlation-indexed, and the naive implementation that skips them loses the guard exactly where a human most needs it: a throwaway identity is precisely where somebody reuses a real value. But the index is answerable only to the holder, and returning its answer to a context-scoped caller hands that caller a yes/no oracle on any value it cares to guess — one guess per write, against the whole pool. No value leaves either way; a confirmed guess at a low-entropy value (a name, an address, a date of birth) is disclosure all the same.",
           "properties": {
             "severity": {
               "type": "string",
@@ -303,7 +303,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
             },
             "matchesPoolValue": {
               "type": "boolean",
-              "description": "True when a value here also appears in the holder's pool. The signal that a throwaway is not throwaway."
+              "description": "True when a value here also appears in the holder's pool — the signal that a throwaway is not throwaway. Present only under the condition on `correlation` itself: this member is the oracle, and a maintainer that omits `correlation` for a context-scoped caller has omitted this."
             }
           }
         },