Hierarchy – modules, spaces and records
A Boost.space system can run anywhere from one to dozens of modules at once. Thanks to one uniform structure — modules → spaces → records — it stays clear at any size, for people and for AI agents alike.
Say you've built a simple CRM with three modules: Companies, Deals, and Tickets.
Modules
A module is a type of data — a table you design, with its own fields. Admins create and configure modules; every user works in them.
Example: the Deals module — with fields like Value, Stage, and a link to Companies.
Spaces
A space groups records inside a module. A module can hold unlimited spaces, any user can create one, and access is per space.
Example: the Deals module split into spaces per team — EU pipeline and US pipeline.
Records
A record is a single row in a space. What it represents depends on the module.
Example: one deal — "Acme renewal, €12,000, Negotiation" — inside the EU pipeline space.
Modules vs. spaces
They're easy to confuse, but they do different jobs:
| Module | Space | |
|---|---|---|
| What it is | A type of data — the table and its fields. | A container that groups records in a module. |
| Job | Defines the structure. | Organizes data and controls access. |
| Created by | Admins. | Any user. |
| Example | Deals | EU pipeline |
In short: modules define the structure; spaces organize and protect the data inside it. This same three-level shape is what agents traverse over MCP and what the API exposes.
