Shared types for the host-side administration of files in the data rooms a community hosts: the vtc/storage/configs/*, vtc/storage/credentials/set, vtc/rooms/get, vtc/rooms/limits/set, vtc/rooms/usage and vtc/rooms/storage/* tasks. A storage config is one named backend — a local directory, an S3-compatible bucket, a Google Cloud Storage bucket or Walrus — with its own account and credentials. Every room is assigned to exactly one config, which receives its new uploads; one config serves any number of rooms; every blob remembers the config it was written to, so reassigning a room strands nothing. Limits, usage and blob shapes come from rooms/_shared/0.1/blobs.schema.json. No member of any type here carries a secret: a credential is referred to by mode, account and fingerprint, never by value. Version 0.2 adds `roleArn` to `ambient` authentication (the IAM role an S3 config's ambient identity assumes), the `notAllowed` credential status for a mode the host no longer permits, and `SealedStorageCredential`, the cleartext a `sealed` credential is carried in; the rules for using an `ambient` or `sealed` credential are vtc/storage/configs/create/0.2's. Version 0.3 changes only `HostedRoom`: its instants `epochExpiresAt`, `createdAt` and `updatedAt` are RFC 3339 date-time strings rather than integer seconds, under the registry-wide convention that an instant is a string named `*At`. Not itself a Trust Task specification (the `_shared` folder is skipped by the registry build and the codegen).
https://trusttasks.org/spec/vtc/_shared/0.3/room-storageTrust 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.