Agent memory is free-form text an agent stores in a VTA context so it can recall it across sessions. A memory item is addressed by the pair `(contextId, key)`; `MemoryRecord` is the shape every versioned task in the family hands back, defined once here because `list`, `get` and the conflict details of `put` and `delete` all return the same record and an inline copy per task would fork the moment one of them gained a member. The version counter is the family's load-bearing invariant and is described once, here, on the same terms as `vta/app-state/*`'s. `version` is a monotonically increasing integer maintained per `contextId`, NOT per item: every write in a context — a put or a delete — takes the next value of that context's counter, and an item's `version` is the counter value its most recent write took. One number therefore serves two purposes: it is the optimistic-concurrency token `expectedVersion` is compared against, and it is the watermark `sinceVersion` is compared against. A per-item counter could do the first but not the second, because two items' counters are not comparable and so no single number could mean "everything changed after this point". Consumers MUST treat version numbers as opaque and monotonic: an item's version can jump by any amount between two writes, because writes to other items in the context consumed the intervening values. The counter is per context because the context is the family's isolation boundary: memory has no namespace below it, and a counter spanning contexts would let a reader of one context observe how much traffic another carried. 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.1/memory-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.