Schema for the cleartext secret payload of a vault entry. Documents the shape both sides of a vault/release/0.1 transfer code-generate against. The secret payload is NEVER transmitted as plaintext JSON on the wire: vault/release/0.1 returns it inside an HPKE-sealed envelope (see SealedSecret in the vault/release payload schema). This shared schema is the authoritative description of the bytes inside that envelope. Sensitive fields (`password`, `privateKey`, `refreshToken`, `secureNotes`, etc.) MUST be zeroised by consumers as soon as their use is complete. Consumers MUST NOT log, persist beyond cache lifetime, or transmit the cleartext outside the release-time scope. Discriminated by `kind`, which mirrors VaultEntry.secretKind on the metadata side. The `kind` value MUST equal the metadata view's `secretKind` for the same entry.
https://trusttasks.org/spec/vault/_shared/0.2/vault-secretTrust 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.