Reference
Glossary
Short definitions, in roughly the order you meet them. Each links to the page that explains the concept in full.
Data model
| Term | Definition |
|---|---|
| Space | The unit of sharing and encryption: a set of objects with one ACL and one read key, replicated between the members' devices through sync nodes that never hold the key. — Spaces |
| Tech space | The per-account private space that holds the account's own bookkeeping — the space list, profile, settings, devices, identities directory — synced only between your devices. — Space list |
| Object | A CRDT tree inside a space: one row of property values in the space's objects collection plus any per-object datasets (blocks, messages, runtime records). — Objects |
| Dataset | A named collection of records that lives on an object — chat_messages, editor_blocks, or a runtime-defined one — read through /query and written through /modify. — Runtime datasets |
| Record | One document in a dataset, addressed by id, mutated by per-path $set / $unset ops and tombstoned rather than erased. — Writing data |
| Change / ChangeId | One signed, content-addressed entry in an object's DAG; every write returns its changeId, which doubles as a version handle on every peer. — Version history |
| Version | A point in an object's causal history named by a ChangeId — "everything this change could see", not a wall-clock moment. — Version history |
| Head-sync | The periodic diff round in which a device exchanges tree heads with the responsible nodes and pulls what it lacks; POST …/sync forces one now. — Sync status |
| CRDT | The merge discipline that lets every device write offline and converge on the same state without a server deciding — per-path last-writer-wins on the DAG order. — CRDT and consistency |
| Derived object / space | An object or space whose id is a pure function of a seed (and the space or account keys), so every device computes it offline and none can fork it — at the price of permanence. — Derived objects, Derived spaces |
| Bundle | One installed thing in a space — a chat, an app's setup — registered under a permanent versioned id with a root object and derived children, so devices converge on one install. — Bundles |
| Type | A named schema attached to objects (any.types), owning property definitions and datasets; resolved by xKey, stored by id. — Types and properties |
| xKey | A type's stable programmatic handle, chosen by the client (pages), unique per space, unaffected by display-name renames. — Types and properties |
| propId | The content-addressed id of a property definition; values are stored and validated at record[typeId][propId], never by xKey. — Types and properties |
| nav | The virtual built-in stamped on every object — nav.type, nav.parentId, nav.pos — that gives a space its tree. — System fields |
| Scope (field) | Where a value lives and who sees it: synced (every member), account (your devices), local (this device), derived (computed by a handler). — System fields |
Search
| Term | Definition |
|---|---|
| Chunker | A per-dataset adapter that turns records into index entries — editor blocks, chat text, property values, runtime-schema records — and streams deletions as tombstones. — Indexing |
| Scope (index) | An open slug (basic, chat, props, agent, …) each index entry lands under, so a search can be narrowed to one kind of content. — Indexing |
| Embedder | The model that turns text into vectors for semantic recall — local llama.cpp, Ollama, or an OpenAI-compatible API; optional, FTS works without it. — Embedders |
Identity and network
| Term | Definition |
|---|---|
| Account / identity | The key pair derived from a BIP-39 mnemonic; its public key is the identity that signs changes and appears in ACLs. — Accounts |
| Device | One installation of an account, with its own device key and peerId; the tech-space devices dataset lists them. — Devices |
| peerId | The network identity of one device, derived from its device key — what the sync nodes and LAN peers see. — Devices |
| Nodeconf | The YAML describing a sync network — coordinator, sync and file nodes and the network id; the binary embeds production, and one setting points elsewhere. — Networks |
| Coordinator | The network node that brokers space registration, deletion, invites and the inbox — it sees metadata, never content. — Networks |
| ACL | A space's access-control log: a signed chain of records granting, changing and revoking member permissions and rotating the read key. — ACL |
| Invite / guest key | A share token a joiner pastes back to request membership; a guest key is the same shape for public read-only access. — Invites |
| One-to-one space | A direct space between exactly two identities, derived from both keys, with no invite handshake. — One-to-one |
Programs and agents
| Term | Definition |
|---|---|
| Program | A Python module (name@vN) run inside the anyrt sandbox; it reaches the world only through recorded effects. — Writing a program |
| Effect | One host syscall a program makes — an HTTP call, time.now, config.get — recorded in the trace with its kind and capability. — Effects |
| Overlay | A repo space that supplies programs and skills under an alias (agent:, std:), joined read-only; the working space can shadow any of them by name. — Modules and overlays |
| Trace | The append-only record of one run — every effect, cell and model turn — from which the run replays bit-exactly. — Traces and replay |
| Cell | One execution step inside a run — a unit of guest code the trace attributes effects and fuel to. — Traces and replay |
| Trigger | A record that fires a program on a cron schedule, once at a time, or on a chat event, pinned to one of your devices. — Trigger schema |
| Process | A live progress view over the event bus for long-running work, with heartbeat, staleness expiry and cancel. — Processes |
Wire-level details for everything above: HTTP API, SSE streams, Errors.