Skip to content

Schemas

PersonaRecord — shared definitions for the persona/* spec family

The persona store holds the identity information a holder keeps about themselves, and the contact records peers disclose to them. It is a distinct store from the credential vault (`vault/*`, which holds verifiable credentials) and from application state (`vta/app-state/*`, which is schema-agnostic and never interpreted). The distinction is not filing: disclosure control is the point of this family, and a maintainer that cannot read a record cannot decide which of its members may leave, cannot audit which ones did, and cannot answer "what have I shared with whom". Two scopes, and the split is normative. The **attribute pool and profiles are agent-scoped** — one person, one set of facts about themselves, above every trust context. **Bindings, contacts and disclosure records are context-scoped**, because a persona lives in a context and so do its counterparties. A maintainer MUST NOT allow a context-scoped caller to read the pool: the direction is a control, not a convenience, and §Authorization of each task states which side it falls on. An access-control failure over a readable pool discloses everything; a pool no context can address has nothing to disclose. Attributes are values and profiles are projections. A profile references pool attributes rather than copying them, so a holder who changes a phone number changes it once. The four entry forms (`ProfileEntry`) are the whole of that flexibility: reference live, reference pinned, reference with an override, or supply a profile-local value. Omission is exclusion — a profile is a whitelist, because a blacklist over a growing pool leaks by default the first time an attribute is added. The version counter follows the `vta/app-state` precedent exactly and for the same reason: monotonic per store rather than per record, so that one number serves as both the optimistic-concurrency token and the change-feed watermark. Consumers MUST treat versions as opaque and monotonic; a record's version can jump by any amount between two writes because its neighbours consumed the intervening values.

Schema ID
https://trusttasks.org/spec/persona/_shared/0.1/persona-record
Kind
shared
Used by
154 specification versions

Trust Tasks — the registry of Trust Task specifications.

Loading the registry… If this message stays, the page's scripts could not load or run. The site needs JavaScript and access to unpkg.com.

Every specification is also on GitHub: trustoverip/dtgwg-trust-tasks-tf/specs, and the framework specification at /SPEC.md.