A Database table defines runtime records and saved View, Insert, Update, or Delete actions with typed fields and access rules.
Property: Identity · Current behavior: database/*, except protected Users
Property: Recommended creation · Current behavior: below database/tables/
Property: Workspace · Current behavior: Model, Data, Actions, and Column/Record/View Inspector
Property: Component use · Current behavior: saved Views via mount-view; write actions through logic
Property: MCP · Current behavior: extensive table-* schema, row, action, identity, preview, execution family
Property: Shipping · Current behavior: backend/runtime integration required
Columns support applicable primary, required, unique, computed, secret, default, format, and relation options. Data supports record entry, selection, copy/paste, deletion, filtering, and Preview identity. Saved actions configure kind-specific returned/writable/default fields, parameters, filtering, sorting, grouping, aggregates, caps/pagination, and public/signed-in/role access.
Secret columns are excluded from readable shapes and conditions. Access fails closed when identity or role cannot be resolved.
Use table-get; column/row mutation operations; View/action/aggregate operations; table-set-identity; table-preview-view; and explicitly authorized table-run-action. Read the connected schemas because valid fields differ by action kind.
Column migration can transform or clear incompatible existing values. Relations must point to compatible tables. Preview is an in-project model, while a shipped app requires a working backend and secure environment.
Definitions and records use table transactions. Running an external/runtime write action is a separate side effect and cannot be reversed by undoing its definition. The current public backend action executor is not production-ready.