A VTA can act as the hidden-vetting (PCS) engine of its principal: it holds the principal's PCS secret keys, and runs every member-side PCS operation — a vetter's enrolment, token drip and attestation, and an applicant's receipt of attestations and its proof — so that the client carrying the messages never holds a PCS key. These definitions describe the inputs the engine takes and the wire forms it produces. The normative rules (custody, one key per vetter and community, authorization, audit) are in CONVENTIONS.md beside this file. Not itself a Trust Task specification: the `_shared` folder is skipped by the registry build and the codegen.
https://trusttasks.org/spec/vta/_shared/0.4/pcs-engineTrust 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.