Glossary
The following are the canonical definitions of terms used across the Nebbos technical documentation. Definitions on this page apply consistently across every reference on the site.
Products
Platform. The web application surface of the Nebbos platform. Hosts department-scoped Pearls, dashboards, approval workflows, task tracking, and audit-chain readers. Every action recorded on the Platform is attributed to a resolved identity.
App. The native desktop client for macOS and Windows. Executes the offline path of the platform, retains operator work locally, and synchronises with the Platform when network connectivity returns.
MCP. The Model Context Protocol capability layer. Every tool call is classified by the MCP to the appropriate data tier on the operator’s host, redacted prior to egress where required, and forwarded to the substrate. Policy is operator-scoped.
Cradle. The customer-facing name for the fourth product surface — the hardware device that carries the MCP binary, the operator’s Pearl memory slice, and the cryptographic keys authorising Host-tier and Architect-tier operations. The internal substrate term is USB (referring to the physical form factor); customer-facing surfaces use “Cradle.”
Concepts
Pearl. A department-scoped reasoning component that runs inside the Platform. Each Pearl is trained on the operator’s ratified decisions. Pearl output is bounded by the scope in which it was trained.
Operator. The organisation whose data resides in Nebbos and whose identities gate substrate access. A single operator holds one or more identities distributed across the three tiers.
Attested action. An operation whose approval is a cryptographic signature verified by the substrate before state changes.
Operator tiers
| Tier | Internal designation | Authentication requirement |
|---|---|---|
| Guest | L1 · Starter | Device-native biometric |
| Host | L2 · Team | Biometric plus Cradle physically present |
| Architect | L3 · Enterprise | Biometric, Cradle, and enclave-signed approval token |
Audit and enforcement
Row-level isolation. Data isolation enforced at the database layer through native row-security policies. Queries against unauthorised scopes are refused prior to answer composition; application-layer code cannot override the policy.
Hash-chained audit. Every read, every write, and every tier decision produces a tamper-evident chain entry. External auditors verify the chain end-to-end from the exported bundle without vendor mediation.
Continuous portability. The export path executes on every production deploy against scoped test tenants. Operators may execute an export at any time on their own schedule.