Skip to Content
ReferenceData model

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

FamilyEntitiesFunction
Identity and accessOperators, workspaces, groups, org-units, delegations, sessions, WebAuthn credentials, Cradle device-keysIdentity plane joined by every operator-scoped table
Departments and PearlsDepartments, Pearl configurations, memory registers, insight rows, playbook selections, prediction tracesReasoning substrate scoped per operational domain
Operational workProjects, tasks, decisions, comments, task-department bindings, activity eventsOperator-scoped work-tracking substrate
SignalsSignals, acknowledgements, escalations, resolutionsCross-domain risk plane maintained by the Orchestrator
Audit chainAudit events and daily chain-check resultsHash-chained record of MCP tool calls and platform API changes
Attachments and ingestionUploaded documents, meeting recordings, indexed content, embeddingsRow-level isolated from ingestion
Governance and substrateADR nodes, doctrine clusters, ratification events, drift trackers, incident postmortemsSelf-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.