contact, product, task, project, website — modules as record types plus a surface.
Updated
Several modules are not separate storage systems — they are record types with a purpose-built surface and a module key gating it:
| Module | Record type(s) | Status column usage |
|---|---|---|
| contacts | contact | new → contacted → closed |
| inventory | product, category | draft → active (only active is ever served to a site) |
| planner | task | planned / doing / done / discarded |
| projects | project | lifecycle statuses (discovery, in-build, live…) |
| websites | website | live / staging / in-build / paused |
| forms | form (+ submissions) | — |
| calendar | schedule_event (+ a settings singleton) | requested / confirmed / completed / cancelled |
dash.records.list("contact") — the module surfaces add scoping, alerts and site integration, they don't replace the engine.source field to contacts, a strain field to products) without waiting on anyone.client_locations record per customer/project holds the business profile — each location just a stable id, a free-form metadata object, and labeled files — so a site can need any shape without a schema change.site_content rows in section blog with a draft/published workflow; drafts are never served.