Dotabase

A structured, searchable collection of DOTs — the platform's core container, and the single foundational data primitive Dots is built on. Roughly "a database of DOTs", but with an AI-native shape: schema, saved views, bound behaviors, an embedding path, and its own Operating Manual telling agents how to use it.

Users create Dotabases freely — that is the platform's central premise. Four are canonical and provisioned for every tenant (Memory Bank, Conversations, Artifacts, HUMAN.md); a handful more are platform-internal (Tasks, Projects, Automations, Glossary). A Dotabase is not a module: modules are product surfaces, Dotabases are knowledge containers.

Each Dotabase has a stable slug, an auto DB-N id, and a row prefix that names its rows (the Glossary's is TERM, so its rows are TERM-1 … TERM-N).

Usage examples

• "Run dots dotabases describe --slug glossary to resolve its id before you search it."
• "The Glossary is an internal, non-foundational Dotabase — provisioned like Tasks and Projects rather than enrolled among the canonical stores."
• "Don't put that in the Cabinet; it belongs in its own Dotabase with a real schema."

Source

AGENT-GOVERNANCE.md § Dots Agent Governance (preamble) — "a single foundational data primitive: the Dotabase" — and § Architecture ("A Dotabase is not a module"). Shape and identity conventions at SPEC-156 § 2 and packages/dotabases/src/seed/glossary.ts; the plain-language gloss at packages/prompts/chat/chip-system.v6.md line 10.