Application state is versioned, namespaced JSON that an application owns and the VTA stores without interpreting. A record is addressed by the triple `(contextId, namespace, key)`; `AppStateRecord` is the shape every task in the family hands back, defined once here because `get`, `list`, `get-many` and the conflict details of `put` and `put-many` all return the same record and an inline copy per task would fork the moment one of them gained a member. The store is deliberately schema-agnostic: `value` is any JSON, and the maintainer never validates, migrates, or interprets it. It is also deliberately NOT a secret store — the vault (`vault/*`) is where secret material belongs, and a maintainer SHOULD surface application state in operator tooling on that understanding. The version counter is the family's load-bearing invariant and is described once, here. `version` is a monotonically increasing integer maintained per `(contextId, namespace)` pair, NOT per record: every write in a namespace takes the next value of that namespace's counter, and a record's `version` is the counter value its most recent write took. One number therefore serves two purposes that would otherwise need two — it is the optimistic-concurrency token `expectedVersion` is compared against, and it is the watermark `sinceVersion` is compared against. A per-record counter could do the first but not the second, because two records' counters are not comparable to each other and so no single number can mean "everything changed after this point". Consumers MUST treat version numbers as opaque and monotonic: a record's version can jump by any amount between two writes, because writes to its neighbours consumed the intervening values. Timestamp invariants (SHOULD-level, prose — not expressible in JSON Schema): when `createdAt` is present, `updatedAt >= createdAt`; when `deletedAt` is present, `deleted` is true and `deletedAt >= createdAt`. Consumers SHOULD reject documents that violate either.
https://trusttasks.org/spec/vta/_shared/0.7/app-state-recordTrust 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.