Learn / Glossary
Routing, sync, mirrors, and agents
| Term | Meaning | Guide |
|---|---|---|
| Site | Tree of typed route nodes (foldkit-site) defining URLs, titles, and Surfaces. | Site |
| Mirror | Keeps a Model slice in sync with the URL, local storage, or a cookie. | Mirror |
| Replica | Client store in foldkit-sync holding local Messages and replaying pending edits. | Sync |
| Journal | Server log in foldkit-durable storing committed Sync operations in order. | Sync |
| Epoch | Identifies a document's server history; a mismatch makes an old Replica rebuild. | Sync |
| Read model | Database table updated as each Journal edit commits for fast queries. | Editing server data |
| Revision | Highest Journal sequence number applied to a row in a Read model. | Editing server data |
| Absorbed | Edit already written to the Read model so Replicas can drop it. | Editing server data |
| Held edit | Absorbed edit kept on the client until its cached row catches up. | Editing server data |
| Alchemy Domain | External @alchemy.run/domain event-sourcing library wired via Remote. | Event-sourced domains |
| Receipt | Stream and version token returned by a Domain command to avoid stale reads. | Event-sourced domains |
| Lowering | Turning a single-row declared write into a Domain Aggregate command. | Event-sourced domains |
| Agent contract | What an AI agent may read (Projection) and trigger (Message subset). | Agents |
may | Server hint on a row showing which guarded actions the current Principal can run. | Guard |