The shapes that describe how an encrypted backup bundle moves between an operator and an agent. Defined once because `initiate-export` and `initiate-import` return the same descriptor, `initiate-import` and the descriptor carry the same chunk manifest, and `get-chunk` and `put-chunk` carry the same chunk — an inline copy per task would fork the moment one of them gained a member. Two transfer algorithms are defined. `stream` moves the whole bundle in one HTTPS request against a recipient-published address, authorized by a bearer token. `chunkedTrustTask` moves it as a sequence of Trust Task documents over whatever transport already carries the family's control-plane tasks, which is what makes a backup possible for an agent that speaks only DIDComm or TSP and has no HTTPS address to publish. The normative account of `chunkedTrustTask` — the chunk-size bound and why, ordering, resume and expiry — is in the `vta/backup/initiate-export/1.1` specification's Chunked transfer section; these definitions carry its shape.
https://trusttasks.org/spec/vta/_shared/0.1/backup-transferTrust 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.