Data model
The Nebbos platform schema comprises 288 tables produced by 514 numbered migrations. Every operator-scoped table carries an operator_scope column and a database-enforced row-level-isolation policy. This reference enumerates the entity families and the isolation contract.
Entity families
| Family | Entities | Function |
|---|---|---|
| Identity and access | Operators, workspaces, groups, org-units, delegations, sessions, WebAuthn credentials, Cradle device-keys | Identity plane joined by every operator-scoped table |
| Departments and Pearls | Departments, Pearl configurations, memory registers, insight rows, playbook selections, prediction traces | Reasoning substrate scoped per operational domain |
| Operational work | Projects, tasks, decisions, comments, task-department bindings, activity events | Operator-scoped work-tracking substrate |
| Signals | Signals, acknowledgements, escalations, resolutions | Cross-domain risk plane maintained by the Orchestrator |
| Audit chain | Audit events and daily chain-check results | Hash-chained record of MCP tool calls and platform API changes |
| Attachments and ingestion | Uploaded documents, meeting recordings, indexed content, embeddings | Row-level isolated from ingestion |
| Governance and substrate | ADR nodes, doctrine clusters, ratification events, drift trackers, incident postmortems | Self-describing corpus supporting substrate reasoning about itself |
Row-level-isolation contract
Every operator-scoped table carries a not-null operator_scope column together with a database-enforced policy applied at SELECT, UPDATE, DELETE, and INSERT. The policy resolves the caller’s identity to the set of authorised scopes at authentication and applies the predicate at the query planner. Application-level bypass is architecturally excluded.
Full mechanism specification and failure-mode analysis is documented in Row-level isolation.
Introspection surfaces
The current schema is served through the following introspection surfaces:
https://api.nebbos.ai/api/v1/openapi.json— endpoint shape specification- Platform administration API — table and column metadata; Architect-tier only
https://api.nebbos.ai/api/v1/schema/head— current migration head
New tables are introduced through numbered migrations. The current migration head is the latest sequence number.
Operator-scoped exports of every row associated with an identity are produced through Portability & export.