How Tabulic works
The model behind Tabulic in one page, for advanced users and AI agents.
Tabulic is a data store that AI agents read and write on a person’s behalf, where every change an agent makes can be seen, approved and undone.
The model
Account (you, signed in by email)
├── Agents one per AI you connect: "Claude", "ChatGPT", "Claude Code"…
└── Workspaces each one a self-contained set of tables
├── Tables → Columns (typed) → Rows
├── Apps programs your agents built, acting as themselves
├── Per-agent and per-app settings: Scope + Approval rules
└── Change log append-only; every Change, grouped into Changesets- An actor is whoever made a change: an agent, an app, or you, the owner.
- Every write by an actor becomes one or more changes (one per row or schema object, with before and after values), grouped into a changeset.
- A changeset is either applied or pending. It’s pending when the actor’s approval rules say that kind of write waits. Only the owner can approve.
- Any applied changeset can be rolled back within the workspace’s history window. The rollback is a new changeset by the owner.
- What an actor can see and write is its scope, set only by the owner.
Principles
- The change log is the source of truth. Tables are the result of applying it. Rollback applies the reverse of each change.
- The owner decides; agents ask. Approving, rejecting, rolling back and changing scopes or rules are never available to agents as tools. An agent can request approval but can’t grant it.
- Nothing is silently lost. Dropped tables and columns are hidden and kept until the history window passes. A rollback never overwrites a later human or app edit without asking.
- Every actor is named. Agents and apps act under their own name, across reconnections, so the history always says who did what.