mirror of
https://github.com/block/buzz.git
synced 2026-11-16 06:11:34 +00:00
Memory read/write graduates from a deferred operation into v1. A keyless agent
could address an encrypted-memory record (storage.address) but not read or
write one, so a keyless runtime stays amnesiac across wakes.
Both actions are slug-addressed and mirror the existing nine:
- storage.get { slug } -> { value? } (value absent = no record, not an error)
- storage.put { slug, value } -> EventPublished
The host derives the address, encrypts on put, and decrypts on get, so the
secret never leaves the key holder -- the same reason storage.address routes
through the interface. value is non-empty and bounded by MAX_CONTENT_BYTES. No
patch/rm: a client composes those from read-modify-write, as profile.set
already does for partial updates.
storage.address is left in place; whether get/put make it redundant is an open
question for review.
Contract crate only. buzz-cli's exhaustive matches gain the two variants when
the keyless-client branch rebases onto this.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: Joel Robotham <jrobotham@squareup.com>