Supabase Storage
Private bucket · per-user prefix · RLS
OBJECTIVE-FIRST AI OPERATING SYSTEM
Restoring workspace
I°
Loading...
MACHINE-READABLE DISK PROTOCOL
Durable state is stored as portable, versioned files that you own. Aya reads and writes them through one provider-neutral contract. Databases and embeddings are derived indexes—not the source of truth.
JSON + JSON Schema on the mounted disk
One contract across storage providers
Search, embeddings, cache, and UI state
Canonical layout
/aya/ manifest.json profile/profile.json preferences/preferences.json conversations/<id>.json memories/<id>.json projects/<id>.json decisions/<id>.json skills/<id>.json
Every file carries
Adapter contract
Consumers call read, write, list, delete, move, and stat. Provider IDs, eTags, revisions, and resource URIs remain opaque metadata.
Private bucket · per-user prefix · RLS
Drive IDs · revisions · OAuth
Graph API · eTags · OAuth
Revisions · content hashes · OAuth
Resource URIs · server capabilities
Private objects are scoped to the authenticated owner's prefix. Aya cannot silently cross ownership boundaries.
Expected revisions prevent silent last-write-wins. External edits are detected before overwrite.
Working memory, vectors, and search indexes can be reconstructed from canonical disk files.
Published JSON Schemas
Runtime writes are validated with the matching Zod schemas before a provider receives bytes. Future versions migrate sequentially and preserve namespaced extension fields.