@openvtc/trust-tasks 0.27.3 → 0.27.5

package/dist/persona/local/profile/put/1.1/payload.d.ts

@@ -0,0 +1,587 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/persona/local/profile/put/1.1/payload.schema.json
+ */
+import type { ClaimType, ExpectedVersion_PersonaV0_1 as ExpectedVersion, Ext, Slot, Ulid, ValueType, Version_PersonaV0_1 as Version } from "../../../../../_shared/components.js";
+/**
+ * Compose a throwaway profile inside a context, from values supplied here rather than drawn from the holder's pool. Inline entries only: a reference is refused, and that refusal is what keeps the local surface pool-free.
+ */
+export interface PersonaLocalProfilePutPayload {
+    contextId: string;
+    profileId?: Ulid;
+    name: string;
+    /**
+     * @maxItems 64
+     */
+    entries: {
+        /**
+         * A value the holder keeps in this context and nowhere else.
+         *
+         * Deliberately NARROWER than a pool profile's inline entry, which also carries `provenance` and requires it. There is no `provenance` member here, and its absence is a rule rather than an omission: a `credentialBacked` provenance names a `credentialId` and a `claimPath`, and a value authored inside a context has nowhere to put either. So a context-local value is SELF-ASSERTED by construction, and a maintainer MUST present it as such.
+         *
+         * That is the same boundary the missing `ref`, pinned and override forms enforce, one member along. Those stop a context-authored object acquiring pool REACH; this stops it acquiring an issuer's AUTHORITY — asserting that a value is attested when no credential was ever checked, over a value the issuer never saw. A holder who needs a context to present an attested claim binds a pool profile, which is holder-authorized, rather than authoring one here.
+         *
+         * Adding a `provenance` member to this object would therefore be a privilege escalation dressed as a convenience, not a gap to fill.
+         */
+        inline: {
+            type: ClaimType;
+            valueType: ValueType;
+            value: unknown;
+            label?: string;
+        };
+        slot?: Slot;
+    }[];
+    expectedVersion?: ExpectedVersion;
+    ext?: Ext;
+}
+/**
+ * Success response to persona/local/profile/put. Type https://trusttasks.org/spec/persona/local/profile/put/1.1#response.
+ */
+export interface PersonaLocalProfilePutResponsePayload {
+    profileId: Ulid;
+    version: Version;
+    wasCreated: boolean;
+    /**
+     * 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. 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;
+    };
+    ext?: Ext;
+}
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { ClaimType, ExpectedVersion, Ext, Slot, Ulid, ValueType, Version };
+/** Trust Task type URI. */
+export declare const TYPE_URI: "https://trusttasks.org/spec/persona/local/profile/put/1.1";
+/** Stable alias for this specification's request payload shape. */
+export type Payload = PersonaLocalProfilePutPayload;
+/** Trust Task response type URI (request type URI + "#response"). */
+export declare const RESPONSE_TYPE_URI: "https://trusttasks.org/spec/persona/local/profile/put/1.1#response";
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = PersonaLocalProfilePutResponsePayload;
+/**
+ * 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 declare const PAYLOAD_SCHEMA: {
+    readonly $schema: "https://json-schema.org/draft/2020-12/schema";
+    readonly $id: "https://trusttasks.org/spec/persona/local/profile/put/1.1";
+    readonly title: "Persona Local Profile Put — payload";
+    readonly description: "Compose a throwaway profile inside a context, from values supplied here rather than drawn from the holder's pool. Inline entries only: a reference is refused, and that refusal is what keeps the local surface pool-free.";
+    readonly type: "object";
+    readonly additionalProperties: false;
+    readonly required: readonly ["contextId", "name", "entries"];
+    readonly properties: {
+        readonly contextId: {
+            readonly type: "string";
+            readonly minLength: 1;
+        };
+        readonly profileId: {
+            readonly $ref: "#/$defs/Ulid";
+        };
+        readonly name: {
+            readonly type: "string";
+            readonly minLength: 1;
+            readonly maxLength: 128;
+        };
+        readonly entries: {
+            readonly type: "array";
+            readonly maxItems: 64;
+            readonly items: {
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["inline"];
+                readonly description: "Inline entries only. The `ref`, pinned and override forms of a pool profile are absent from this schema deliberately — a context-local profile that could reference the pool would be a context-authored object acquiring pool reach, which is exactly what the boundary exists to prevent.";
+                readonly properties: {
+                    readonly inline: {
+                        readonly description: "A value the holder keeps in this context and nowhere else.\n\nDeliberately NARROWER than a pool profile's inline entry, which also carries `provenance` and requires it. There is no `provenance` member here, and its absence is a rule rather than an omission: a `credentialBacked` provenance names a `credentialId` and a `claimPath`, and a value authored inside a context has nowhere to put either. So a context-local value is SELF-ASSERTED by construction, and a maintainer MUST present it as such.\n\nThat is the same boundary the missing `ref`, pinned and override forms enforce, one member along. Those stop a context-authored object acquiring pool REACH; this stops it acquiring an issuer's AUTHORITY — asserting that a value is attested when no credential was ever checked, over a value the issuer never saw. A holder who needs a context to present an attested claim binds a pool profile, which is holder-authorized, rather than authoring one here.\n\nAdding a `provenance` member to this object would therefore be a privilege escalation dressed as a convenience, not a gap to fill.";
+                        readonly type: "object";
+                        readonly additionalProperties: false;
+                        readonly required: readonly ["type", "valueType", "value"];
+                        readonly properties: {
+                            readonly type: {
+                                readonly $ref: "#/$defs/ClaimType";
+                            };
+                            readonly valueType: {
+                                readonly $ref: "#/$defs/ValueType";
+                            };
+                            readonly value: {};
+                            readonly label: {
+                                readonly type: "string";
+                                readonly maxLength: 128;
+                            };
+                        };
+                    };
+                    readonly slot: {
+                        readonly $ref: "#/$defs/Slot";
+                    };
+                };
+            };
+        };
+        readonly expectedVersion: {
+            readonly $ref: "#/$defs/ExpectedVersion";
+        };
+        readonly ext: {
+            readonly $ref: "#/$defs/Ext";
+        };
+    };
+    readonly $defs: {
+        readonly Response: {
+            readonly $anchor: "response";
+            readonly title: "Persona Local Profile Put — response payload";
+            readonly description: "Success response to persona/local/profile/put. Type https://trusttasks.org/spec/persona/local/profile/put/1.1#response.";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["profileId", "version", "wasCreated"];
+            readonly properties: {
+                readonly profileId: {
+                    readonly $ref: "#/$defs/Ulid";
+                };
+                readonly version: {
+                    readonly $ref: "#/$defs/Version";
+                };
+                readonly wasCreated: {
+                    readonly type: "boolean";
+                };
+                readonly correlation: {
+                    readonly type: "object";
+                    readonly additionalProperties: false;
+                    readonly required: readonly ["severity"];
+                    readonly 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.";
+                    readonly properties: {
+                        readonly severity: {
+                            readonly type: "string";
+                            readonly enum: readonly ["none", "low", "high"];
+                        };
+                        readonly matchesPoolValue: {
+                            readonly type: "boolean";
+                            readonly 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.";
+                        };
+                    };
+                };
+                readonly ext: {
+                    readonly $ref: "#/$defs/Ext";
+                };
+            };
+        };
+        readonly Ext: {
+            readonly title: "Ext";
+            readonly description: "Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a reverse-DNS namespace; structure under each namespace is opaque to the framework.";
+            readonly type: "object";
+            readonly minProperties: 1;
+            readonly additionalProperties: true;
+            readonly propertyNames: {
+                readonly pattern: "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$";
+            };
+        };
+        readonly Version: {
+            readonly title: "Version";
+            readonly description: "A value of the store's monotonic write counter. Server-assigned; a producer never chooses one.";
+            readonly type: "integer";
+            readonly minimum: 1;
+        };
+        readonly Ulid: {
+            readonly title: "Ulid";
+            readonly description: "A ULID in Crockford base32, uppercase. Used for `attributeId` and `profileId`. Chosen over a UUID because the leading 48 bits are a timestamp, so a key-ordered scan of the store is also creation-ordered and a `list` needs no secondary sort. Server-assigned on create; a producer MAY supply one to make a create idempotent, and a maintainer MUST reject a supplied value that already exists rather than silently overwriting.";
+            readonly type: "string";
+            readonly pattern: "^[0-9A-HJKMNP-TV-Z]{26}$";
+        };
+        readonly ExpectedVersion: {
+            readonly title: "ExpectedVersion";
+            readonly description: "Optimistic-concurrency precondition. A positive value requires the record's current `version` to equal it exactly; zero means create-only and applies only when no live record exists at the address.";
+            readonly type: "integer";
+            readonly minimum: 0;
+        };
+        readonly Slot: {
+            readonly title: "Slot";
+            readonly type: "string";
+            readonly pattern: "^[a-z][A-Za-z0-9]{0,31}$";
+            readonly description: "A role a profile entry plays within its profile, so a consumer can find it without guessing from its claim type. A profile MAY hold several entries of one type — a legal name and a display name, two phone numbers — and only a slot says which answers a given question. Unique within a profile.\n\nWell-known slots:\n\n- `displayName` — what this face calls itself. The entry a consumer renders as the face's name to anyone it is shown to. Distinct from the profile's own `name`, which is the holder's private label and never disclosed.\n- `primaryEmail`, `primaryPhone`, `primaryAddress` — the entry to use where a counterparty asks for one of a kind and the profile holds several.\n- `avatar` — the image this face presents.\n\nOther values are the holder's or the producer's own and carry no meaning a maintainer interprets.";
+        };
+        readonly ValueType: {
+            readonly title: "ValueType";
+            readonly description: "The JSON shape of `value`, declared so that a consumer can render and compare without guessing. The maintainer validates that `value` agrees with this member and does nothing further: it does NOT validate a phone number against a phone-number grammar. That is a producer's affordance, and a store that grows opinions about the contents of its records eventually blocks its consumer's release.";
+            readonly type: "string";
+            readonly enum: readonly ["string", "number", "boolean", "date", "object"];
+        };
+        readonly ClaimType: {
+            readonly title: "ClaimType";
+            readonly description: "The vocabulary token naming what a value IS — `name.legal`, `phone.mobile`, `address.postal`, `person.birthDate`. Dotted, most-general segment first, so that a consumer with no knowledge of the specific token can still group by its prefix.\n\nThe token is the maintainer's own; no external vocabulary is primary. External vocabularies (vCard/jCard, OIDC standard claims, schema.org) are mappings applied at PRESENTATION by a renderer, not at rest, so that a query written in any of them can be matched without the store having to live inside any one of them.\n\nThe `x:` prefix is an open extension namespace and is not decoration. The closest prior art — Windows CardSpace's self-issued card — supported exactly fifteen predefined claim types with no extensibility, and that is the specific way it failed the requirement a holder actually has. An `x:` attribute stores, composes, binds and discloses exactly like a known one; it renders generically and matches only an explicit query.";
+            readonly type: "string";
+            readonly minLength: 1;
+            readonly maxLength: 128;
+            readonly pattern: "^(x:)?[a-z][a-zA-Z0-9]*(\\.[a-z][a-zA-Z0-9]*)*$";
+        };
+    };
+};
+/** As {@link PAYLOAD_SCHEMA}, for the success-response variant. */
+export declare const RESPONSE_PAYLOAD_SCHEMA: {
+    readonly $schema: "https://json-schema.org/draft/2020-12/schema";
+    readonly $ref: "#/$defs/Response";
+    readonly $defs: {
+        readonly Response: {
+            readonly $anchor: "response";
+            readonly title: "Persona Local Profile Put — response payload";
+            readonly description: "Success response to persona/local/profile/put. Type https://trusttasks.org/spec/persona/local/profile/put/1.1#response.";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["profileId", "version", "wasCreated"];
+            readonly properties: {
+                readonly profileId: {
+                    readonly $ref: "#/$defs/Ulid";
+                };
+                readonly version: {
+                    readonly $ref: "#/$defs/Version";
+                };
+                readonly wasCreated: {
+                    readonly type: "boolean";
+                };
+                readonly correlation: {
+                    readonly type: "object";
+                    readonly additionalProperties: false;
+                    readonly required: readonly ["severity"];
+                    readonly 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.";
+                    readonly properties: {
+                        readonly severity: {
+                            readonly type: "string";
+                            readonly enum: readonly ["none", "low", "high"];
+                        };
+                        readonly matchesPoolValue: {
+                            readonly type: "boolean";
+                            readonly 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.";
+                        };
+                    };
+                };
+                readonly ext: {
+                    readonly $ref: "#/$defs/Ext";
+                };
+            };
+        };
+        readonly Ext: {
+            readonly title: "Ext";
+            readonly description: "Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a reverse-DNS namespace; structure under each namespace is opaque to the framework.";
+            readonly type: "object";
+            readonly minProperties: 1;
+            readonly additionalProperties: true;
+            readonly propertyNames: {
+                readonly pattern: "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$";
+            };
+        };
+        readonly Version: {
+            readonly title: "Version";
+            readonly description: "A value of the store's monotonic write counter. Server-assigned; a producer never chooses one.";
+            readonly type: "integer";
+            readonly minimum: 1;
+        };
+        readonly Ulid: {
+            readonly title: "Ulid";
+            readonly description: "A ULID in Crockford base32, uppercase. Used for `attributeId` and `profileId`. Chosen over a UUID because the leading 48 bits are a timestamp, so a key-ordered scan of the store is also creation-ordered and a `list` needs no secondary sort. Server-assigned on create; a producer MAY supply one to make a create idempotent, and a maintainer MUST reject a supplied value that already exists rather than silently overwriting.";
+            readonly type: "string";
+            readonly pattern: "^[0-9A-HJKMNP-TV-Z]{26}$";
+        };
+        readonly ExpectedVersion: {
+            readonly title: "ExpectedVersion";
+            readonly description: "Optimistic-concurrency precondition. A positive value requires the record's current `version` to equal it exactly; zero means create-only and applies only when no live record exists at the address.";
+            readonly type: "integer";
+            readonly minimum: 0;
+        };
+        readonly Slot: {
+            readonly title: "Slot";
+            readonly type: "string";
+            readonly pattern: "^[a-z][A-Za-z0-9]{0,31}$";
+            readonly description: "A role a profile entry plays within its profile, so a consumer can find it without guessing from its claim type. A profile MAY hold several entries of one type — a legal name and a display name, two phone numbers — and only a slot says which answers a given question. Unique within a profile.\n\nWell-known slots:\n\n- `displayName` — what this face calls itself. The entry a consumer renders as the face's name to anyone it is shown to. Distinct from the profile's own `name`, which is the holder's private label and never disclosed.\n- `primaryEmail`, `primaryPhone`, `primaryAddress` — the entry to use where a counterparty asks for one of a kind and the profile holds several.\n- `avatar` — the image this face presents.\n\nOther values are the holder's or the producer's own and carry no meaning a maintainer interprets.";
+        };
+        readonly ValueType: {
+            readonly title: "ValueType";
+            readonly description: "The JSON shape of `value`, declared so that a consumer can render and compare without guessing. The maintainer validates that `value` agrees with this member and does nothing further: it does NOT validate a phone number against a phone-number grammar. That is a producer's affordance, and a store that grows opinions about the contents of its records eventually blocks its consumer's release.";
+            readonly type: "string";
+            readonly enum: readonly ["string", "number", "boolean", "date", "object"];
+        };
+        readonly ClaimType: {
+            readonly title: "ClaimType";
+            readonly description: "The vocabulary token naming what a value IS — `name.legal`, `phone.mobile`, `address.postal`, `person.birthDate`. Dotted, most-general segment first, so that a consumer with no knowledge of the specific token can still group by its prefix.\n\nThe token is the maintainer's own; no external vocabulary is primary. External vocabularies (vCard/jCard, OIDC standard claims, schema.org) are mappings applied at PRESENTATION by a renderer, not at rest, so that a query written in any of them can be matched without the store having to live inside any one of them.\n\nThe `x:` prefix is an open extension namespace and is not decoration. The closest prior art — Windows CardSpace's self-issued card — supported exactly fifteen predefined claim types with no extensibility, and that is the specific way it failed the requirement a holder actually has. An `x:` attribute stores, composes, binds and discloses exactly like a known one; it renders generically and matches only an explicit query.";
+            readonly type: "string";
+            readonly minLength: 1;
+            readonly maxLength: 128;
+            readonly pattern: "^(x:)?[a-z][a-zA-Z0-9]*(\\.[a-z][a-zA-Z0-9]*)*$";
+        };
+    };
+};
+/**
+ * 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 declare const SPEC: {
+    readonly typeUri: "https://trusttasks.org/spec/persona/local/profile/put/1.1";
+    readonly isBearer: false;
+    readonly isProofRequired: true;
+    readonly isRecipientRequired: true;
+    readonly isIssuedAtRequired: true;
+    readonly payloadSchema: {
+        readonly $schema: "https://json-schema.org/draft/2020-12/schema";
+        readonly $id: "https://trusttasks.org/spec/persona/local/profile/put/1.1";
+        readonly title: "Persona Local Profile Put — payload";
+        readonly description: "Compose a throwaway profile inside a context, from values supplied here rather than drawn from the holder's pool. Inline entries only: a reference is refused, and that refusal is what keeps the local surface pool-free.";
+        readonly type: "object";
+        readonly additionalProperties: false;
+        readonly required: readonly ["contextId", "name", "entries"];
+        readonly properties: {
+            readonly contextId: {
+                readonly type: "string";
+                readonly minLength: 1;
+            };
+            readonly profileId: {
+                readonly $ref: "#/$defs/Ulid";
+            };
+            readonly name: {
+                readonly type: "string";
+                readonly minLength: 1;
+                readonly maxLength: 128;
+            };
+            readonly entries: {
+                readonly type: "array";
+                readonly maxItems: 64;
+                readonly items: {
+                    readonly type: "object";
+                    readonly additionalProperties: false;
+                    readonly required: readonly ["inline"];
+                    readonly description: "Inline entries only. The `ref`, pinned and override forms of a pool profile are absent from this schema deliberately — a context-local profile that could reference the pool would be a context-authored object acquiring pool reach, which is exactly what the boundary exists to prevent.";
+                    readonly properties: {
+                        readonly inline: {
+                            readonly description: "A value the holder keeps in this context and nowhere else.\n\nDeliberately NARROWER than a pool profile's inline entry, which also carries `provenance` and requires it. There is no `provenance` member here, and its absence is a rule rather than an omission: a `credentialBacked` provenance names a `credentialId` and a `claimPath`, and a value authored inside a context has nowhere to put either. So a context-local value is SELF-ASSERTED by construction, and a maintainer MUST present it as such.\n\nThat is the same boundary the missing `ref`, pinned and override forms enforce, one member along. Those stop a context-authored object acquiring pool REACH; this stops it acquiring an issuer's AUTHORITY — asserting that a value is attested when no credential was ever checked, over a value the issuer never saw. A holder who needs a context to present an attested claim binds a pool profile, which is holder-authorized, rather than authoring one here.\n\nAdding a `provenance` member to this object would therefore be a privilege escalation dressed as a convenience, not a gap to fill.";
+                            readonly type: "object";
+                            readonly additionalProperties: false;
+                            readonly required: readonly ["type", "valueType", "value"];
+                            readonly properties: {
+                                readonly type: {
+                                    readonly $ref: "#/$defs/ClaimType";
+                                };
+                                readonly valueType: {
+                                    readonly $ref: "#/$defs/ValueType";
+                                };
+                                readonly value: {};
+                                readonly label: {
+                                    readonly type: "string";
+                                    readonly maxLength: 128;
+                                };
+                            };
+                        };
+                        readonly slot: {
+                            readonly $ref: "#/$defs/Slot";
+                        };
+                    };
+                };
+            };
+            readonly expectedVersion: {
+                readonly $ref: "#/$defs/ExpectedVersion";
+            };
+            readonly ext: {
+                readonly $ref: "#/$defs/Ext";
+            };
+        };
+        readonly $defs: {
+            readonly Response: {
+                readonly $anchor: "response";
+                readonly title: "Persona Local Profile Put — response payload";
+                readonly description: "Success response to persona/local/profile/put. Type https://trusttasks.org/spec/persona/local/profile/put/1.1#response.";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["profileId", "version", "wasCreated"];
+                readonly properties: {
+                    readonly profileId: {
+                        readonly $ref: "#/$defs/Ulid";
+                    };
+                    readonly version: {
+                        readonly $ref: "#/$defs/Version";
+                    };
+                    readonly wasCreated: {
+                        readonly type: "boolean";
+                    };
+                    readonly correlation: {
+                        readonly type: "object";
+                        readonly additionalProperties: false;
+                        readonly required: readonly ["severity"];
+                        readonly 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.";
+                        readonly properties: {
+                            readonly severity: {
+                                readonly type: "string";
+                                readonly enum: readonly ["none", "low", "high"];
+                            };
+                            readonly matchesPoolValue: {
+                                readonly type: "boolean";
+                                readonly 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.";
+                            };
+                        };
+                    };
+                    readonly ext: {
+                        readonly $ref: "#/$defs/Ext";
+                    };
+                };
+            };
+            readonly Ext: {
+                readonly title: "Ext";
+                readonly description: "Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a reverse-DNS namespace; structure under each namespace is opaque to the framework.";
+                readonly type: "object";
+                readonly minProperties: 1;
+                readonly additionalProperties: true;
+                readonly propertyNames: {
+                    readonly pattern: "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$";
+                };
+            };
+            readonly Version: {
+                readonly title: "Version";
+                readonly description: "A value of the store's monotonic write counter. Server-assigned; a producer never chooses one.";
+                readonly type: "integer";
+                readonly minimum: 1;
+            };
+            readonly Ulid: {
+                readonly title: "Ulid";
+                readonly description: "A ULID in Crockford base32, uppercase. Used for `attributeId` and `profileId`. Chosen over a UUID because the leading 48 bits are a timestamp, so a key-ordered scan of the store is also creation-ordered and a `list` needs no secondary sort. Server-assigned on create; a producer MAY supply one to make a create idempotent, and a maintainer MUST reject a supplied value that already exists rather than silently overwriting.";
+                readonly type: "string";
+                readonly pattern: "^[0-9A-HJKMNP-TV-Z]{26}$";
+            };
+            readonly ExpectedVersion: {
+                readonly title: "ExpectedVersion";
+                readonly description: "Optimistic-concurrency precondition. A positive value requires the record's current `version` to equal it exactly; zero means create-only and applies only when no live record exists at the address.";
+                readonly type: "integer";
+                readonly minimum: 0;
+            };
+            readonly Slot: {
+                readonly title: "Slot";
+                readonly type: "string";
+                readonly pattern: "^[a-z][A-Za-z0-9]{0,31}$";
+                readonly description: "A role a profile entry plays within its profile, so a consumer can find it without guessing from its claim type. A profile MAY hold several entries of one type — a legal name and a display name, two phone numbers — and only a slot says which answers a given question. Unique within a profile.\n\nWell-known slots:\n\n- `displayName` — what this face calls itself. The entry a consumer renders as the face's name to anyone it is shown to. Distinct from the profile's own `name`, which is the holder's private label and never disclosed.\n- `primaryEmail`, `primaryPhone`, `primaryAddress` — the entry to use where a counterparty asks for one of a kind and the profile holds several.\n- `avatar` — the image this face presents.\n\nOther values are the holder's or the producer's own and carry no meaning a maintainer interprets.";
+            };
+            readonly ValueType: {
+                readonly title: "ValueType";
+                readonly description: "The JSON shape of `value`, declared so that a consumer can render and compare without guessing. The maintainer validates that `value` agrees with this member and does nothing further: it does NOT validate a phone number against a phone-number grammar. That is a producer's affordance, and a store that grows opinions about the contents of its records eventually blocks its consumer's release.";
+                readonly type: "string";
+                readonly enum: readonly ["string", "number", "boolean", "date", "object"];
+            };
+            readonly ClaimType: {
+                readonly title: "ClaimType";
+                readonly description: "The vocabulary token naming what a value IS — `name.legal`, `phone.mobile`, `address.postal`, `person.birthDate`. Dotted, most-general segment first, so that a consumer with no knowledge of the specific token can still group by its prefix.\n\nThe token is the maintainer's own; no external vocabulary is primary. External vocabularies (vCard/jCard, OIDC standard claims, schema.org) are mappings applied at PRESENTATION by a renderer, not at rest, so that a query written in any of them can be matched without the store having to live inside any one of them.\n\nThe `x:` prefix is an open extension namespace and is not decoration. The closest prior art — Windows CardSpace's self-issued card — supported exactly fifteen predefined claim types with no extensibility, and that is the specific way it failed the requirement a holder actually has. An `x:` attribute stores, composes, binds and discloses exactly like a known one; it renders generically and matches only an explicit query.";
+                readonly type: "string";
+                readonly minLength: 1;
+                readonly maxLength: 128;
+                readonly pattern: "^(x:)?[a-z][a-zA-Z0-9]*(\\.[a-z][a-zA-Z0-9]*)*$";
+            };
+        };
+    };
+};
+/**
+ * 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 declare const RESPONSE_SPEC: {
+    readonly typeUri: "https://trusttasks.org/spec/persona/local/profile/put/1.1#response";
+    readonly isBearer: false;
+    readonly isProofRequired: true;
+    readonly isRecipientRequired: true;
+    readonly isIssuedAtRequired: true;
+    readonly payloadSchema: {
+        readonly $schema: "https://json-schema.org/draft/2020-12/schema";
+        readonly $ref: "#/$defs/Response";
+        readonly $defs: {
+            readonly Response: {
+                readonly $anchor: "response";
+                readonly title: "Persona Local Profile Put — response payload";
+                readonly description: "Success response to persona/local/profile/put. Type https://trusttasks.org/spec/persona/local/profile/put/1.1#response.";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["profileId", "version", "wasCreated"];
+                readonly properties: {
+                    readonly profileId: {
+                        readonly $ref: "#/$defs/Ulid";
+                    };
+                    readonly version: {
+                        readonly $ref: "#/$defs/Version";
+                    };
+                    readonly wasCreated: {
+                        readonly type: "boolean";
+                    };
+                    readonly correlation: {
+                        readonly type: "object";
+                        readonly additionalProperties: false;
+                        readonly required: readonly ["severity"];
+                        readonly 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.";
+                        readonly properties: {
+                            readonly severity: {
+                                readonly type: "string";
+                                readonly enum: readonly ["none", "low", "high"];
+                            };
+                            readonly matchesPoolValue: {
+                                readonly type: "boolean";
+                                readonly 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.";
+                            };
+                        };
+                    };
+                    readonly ext: {
+                        readonly $ref: "#/$defs/Ext";
+                    };
+                };
+            };
+            readonly Ext: {
+                readonly title: "Ext";
+                readonly description: "Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a reverse-DNS namespace; structure under each namespace is opaque to the framework.";
+                readonly type: "object";
+                readonly minProperties: 1;
+                readonly additionalProperties: true;
+                readonly propertyNames: {
+                    readonly pattern: "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$";
+                };
+            };
+            readonly Version: {
+                readonly title: "Version";
+                readonly description: "A value of the store's monotonic write counter. Server-assigned; a producer never chooses one.";
+                readonly type: "integer";
+                readonly minimum: 1;
+            };
+            readonly Ulid: {
+                readonly title: "Ulid";
+                readonly description: "A ULID in Crockford base32, uppercase. Used for `attributeId` and `profileId`. Chosen over a UUID because the leading 48 bits are a timestamp, so a key-ordered scan of the store is also creation-ordered and a `list` needs no secondary sort. Server-assigned on create; a producer MAY supply one to make a create idempotent, and a maintainer MUST reject a supplied value that already exists rather than silently overwriting.";
+                readonly type: "string";
+                readonly pattern: "^[0-9A-HJKMNP-TV-Z]{26}$";
+            };
+            readonly ExpectedVersion: {
+                readonly title: "ExpectedVersion";
+                readonly description: "Optimistic-concurrency precondition. A positive value requires the record's current `version` to equal it exactly; zero means create-only and applies only when no live record exists at the address.";
+                readonly type: "integer";
+                readonly minimum: 0;
+            };
+            readonly Slot: {
+                readonly title: "Slot";
+                readonly type: "string";
+                readonly pattern: "^[a-z][A-Za-z0-9]{0,31}$";
+                readonly description: "A role a profile entry plays within its profile, so a consumer can find it without guessing from its claim type. A profile MAY hold several entries of one type — a legal name and a display name, two phone numbers — and only a slot says which answers a given question. Unique within a profile.\n\nWell-known slots:\n\n- `displayName` — what this face calls itself. The entry a consumer renders as the face's name to anyone it is shown to. Distinct from the profile's own `name`, which is the holder's private label and never disclosed.\n- `primaryEmail`, `primaryPhone`, `primaryAddress` — the entry to use where a counterparty asks for one of a kind and the profile holds several.\n- `avatar` — the image this face presents.\n\nOther values are the holder's or the producer's own and carry no meaning a maintainer interprets.";
+            };
+            readonly ValueType: {
+                readonly title: "ValueType";
+                readonly description: "The JSON shape of `value`, declared so that a consumer can render and compare without guessing. The maintainer validates that `value` agrees with this member and does nothing further: it does NOT validate a phone number against a phone-number grammar. That is a producer's affordance, and a store that grows opinions about the contents of its records eventually blocks its consumer's release.";
+                readonly type: "string";
+                readonly enum: readonly ["string", "number", "boolean", "date", "object"];
+            };
+            readonly ClaimType: {
+                readonly title: "ClaimType";
+                readonly description: "The vocabulary token naming what a value IS — `name.legal`, `phone.mobile`, `address.postal`, `person.birthDate`. Dotted, most-general segment first, so that a consumer with no knowledge of the specific token can still group by its prefix.\n\nThe token is the maintainer's own; no external vocabulary is primary. External vocabularies (vCard/jCard, OIDC standard claims, schema.org) are mappings applied at PRESENTATION by a renderer, not at rest, so that a query written in any of them can be matched without the store having to live inside any one of them.\n\nThe `x:` prefix is an open extension namespace and is not decoration. The closest prior art — Windows CardSpace's self-issued card — supported exactly fifteen predefined claim types with no extensibility, and that is the specific way it failed the requirement a holder actually has. An `x:` attribute stores, composes, binds and discloses exactly like a known one; it renders generically and matches only an explicit query.";
+                readonly type: "string";
+                readonly minLength: 1;
+                readonly maxLength: 128;
+                readonly pattern: "^(x:)?[a-z][a-zA-Z0-9]*(\\.[a-z][a-zA-Z0-9]*)*$";
+            };
+        };
+    };
+};
+//# sourceMappingURL=payload.d.ts.map

package/dist/persona/local/profile/put/1.1/payload.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"payload.d.ts","sourceRoot":"","sources":["../../../../../../src/persona/local/profile/put/1.1/payload.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,OAAO,KAAK,EAAE,SAAS,EAAE,2BAA2B,IAAI,eAAe,EAAE,GAAG,EAAE,IAAI,EAAE,IAAI,EAAE,SAAS,EAAE,mBAAmB,IAAI,OAAO,EAAE,MAAM,sCAAsC,CAAC;AAGlL;;GAEG;AACH,MAAM,WAAW,6BAA6B;IAC5C,SAAS,EAAE,MAAM,CAAC;IAClB,SAAS,CAAC,EAAE,IAAI,CAAC;IACjB,IAAI,EAAE,MAAM,CAAC;IACb;;OAEG;IACH,OAAO,EAAE;QACP;;;;;;;;WAQG;QACH,MAAM,EAAE;YACN,IAAI,EAAE,SAAS,CAAC;YAChB,SAAS,EAAE,SAAS,CAAC;YACrB,KAAK,EAAE,OAAO,CAAC;YACf,KAAK,CAAC,EAAE,MAAM,CAAC;SAChB,CAAC;QACF,IAAI,CAAC,EAAE,IAAI,CAAC;KACb,EAAE,CAAC;IACJ,eAAe,CAAC,EAAE,eAAe,CAAC;IAClC,GAAG,CAAC,EAAE,GAAG,CAAC;CACX;AACD;;GAEG;AACH,MAAM,WAAW,qCAAqC;IACpD,SAAS,EAAE,IAAI,CAAC;IAChB,OAAO,EAAE,OAAO,CAAC;IACjB,UAAU,EAAE,OAAO,CAAC;IACpB;;OAEG;IACH,WAAW,CAAC,EAAE;QACZ,QAAQ,EAAE,MAAM,GAAG,KAAK,GAAG,MAAM,CAAC;QAClC;;WAEG;QACH,gBAAgB,CAAC,EAAE,OAAO,CAAC;KAC5B,CAAC;IACF,GAAG,CAAC,EAAE,GAAG,CAAC;CACX;AAED,kHAAkH;AAClH,YAAY,EAAE,SAAS,EAAE,eAAe,EAAE,GAAG,EAAE,IAAI,EAAE,IAAI,EAAE,SAAS,EAAE,OAAO,EAAE,CAAC;AAEhF,2BAA2B;AAC3B,eAAO,MAAM,QAAQ,EAAG,2DAAoE,CAAC;AAE7F,mEAAmE;AACnE,MAAM,MAAM,OAAO,GAAG,6BAA6B,CAAC;AAEpD,qEAAqE;AACrE,eAAO,MAAM,iBAAiB,EAAG,oEAA6E,CAAC;AAE/G,4EAA4E;AAC5E,MAAM,MAAM,QAAQ,GAAG,qCAAqC,CAAC;AAE7D;;;;;;;;GAQG;AACH,eAAO,MAAM,cAAc;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAgLjB,CAAC;AAEX,mEAAmE;AACnE,eAAO,MAAM,uBAAuB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA2G1B,CAAC;AAEX;;;;;GAKG;AACH,eAAO,MAAM,IAAI;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAOP,CAAC;AAEX;;;;GAIG;AACH,eAAO,MAAM,aAAa;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAOhB,CAAC"}