Tabulic

Glossary

Every Tabulic term, defined in one place.

Account: How an owner signs in on the hosted service: one email address, a plan, the workspaces it owns and its agents.

Actor: Whoever made a change: an agent, an app or the owner.

Agent: A named identity under which an AI tool acts, such as “Claude”. Belongs to the account, with its own scope and approval rules in each workspace.

App: A program an agent built that reads and writes the workspace’s data under its own name. Most have a page published in the workspace; others are scripts with a secret key or pages hosted elsewhere.

Approval: The owner’s decision to apply a pending changeset. Only the owner can give it; an agent can only request it.

Approval rule: A per-actor setting, for one kind of write, of whether it applies at once or waits.

Batch: One call carrying up to 100 inserts, updates and deletes that become one changeset, all or nothing.

Bulk write: One insert, update or delete that touches more rows than the actor’s bulk threshold (10 by default).

Cascade: Later agent changes that a rollback also reverses because they depend on what it removes.

Change: One recorded modification to one row or to the schema, with before and after values.

Changeset: A group of changes by one actor, reviewed and rolled back as a unit. Entirely applied or entirely pending.

Conflict: A cell a rollback would revert that the owner or an app has changed since. The owner chooses per cell.

Connection: One authorization through which a host acts as an agent, or a browser or script acts as an app.

Drop: Removing a table or column from view. Its data is kept until the history window passes.

Expired: A pending changeset that waited past the history window. Nothing of it applied.

Handle: The unique, permanent short name of a workspace, part of its address.

History window: How far back a workspace keeps changes that can be rolled back.

Owner: The single person a workspace belongs to; the only one who can approve or roll back.

Pending changeset: A changeset requested but not yet applied, waiting for approval. Its targets are fixed when requested.

Plan: What an account may use on the hosted service: workspaces, agents, apps, history window, monthly writes and size.

Purge: Erasing the values of changesets past the history window, keeping who changed what and when.

Rollback: Undoing an applied changeset by applying the reverse of each change. Itself a new changeset.

Scope: What an agent or app may touch: tables, columns, read or write, schema changes, publishing pages. Set only by the owner.

Workspace: One self-contained body of data: tables, rows, change history, apps and per-actor settings.