Canonical metadata view of a single vault entry — a credential the holder has stored for use against a third-party site, mobile app, or DID-identified relying party. Referenced by every vault/* specification that returns entry metadata (vault/list, vault/get, vault/upsert response, vault/sync, vault/usage). This definition is the metadata-only view: it deliberately does NOT include secret material. Secrets are released only via vault/release/0.1, and even then are carried inside HPKE-sealed envelopes that the vault Trust Task itself does not parse. The `_shared` folder is skipped by the registry build and by the codegen. Timestamp invariants (SHOULD-level, prose — not expressible in JSON Schema): when both `createdAt` and `updatedAt` are present, `updatedAt >= createdAt`; when `lastUsedAt` is present, `lastUsedAt >= createdAt`; when `expiresAt` is present, `expiresAt > createdAt`. Consumers SHOULD reject documents that violate any of these.
https://trusttasks.org/spec/vault/_shared/0.1/vault-entryTrust 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.