Dotabases

A Dotabase is a typed collection of rows that keeps its structure. Because the structure survives the act of writing something down, the same knowledge is a table you scan, a graph you traverse, and context an AI reads. Nothing is exported or converted between those three readings.

Everything you or an agent stores in Dots is a row in a Dotabase. A Tasks Dotabase and a Songs Dotabase are the same two database tables wearing different schemas, different views, and different behavior bindings. That is what makes Dots one primitive rather than a bundle of features: a capability built for one Dotabase works on every Dotabase, including the ones you have not created yet.

Key Features

• Typed Rows — a title, a body, and typed properties drawn from thirty-three built-in property types, so a date comes back a date and a number a number.
• Closed Schema — a write naming a property the schema does not declare is refused, which is what lets a filter, a view, or an agent depend on the shape.
• Behaviors — thirty-nine enrichment behaviors across six lifecycle hooks, each Dotabase binding only the ones it wants: classification, embedding, version history, relation-to-edge promotion.
• Typed Edges — seventy-nine built-in verbs in five categories, connecting rows across two Dotabases or out to a code symbol.
• Ten View Types — table, board, gallery, list, calendar, timeline, stream, wheel, graph, and dashboard over the same rows. A view is a lens, never a copy.
• Hybrid Search — full-text and semantic retrieval over the same row, because both the search vector and the embedding live on it.
• Operation Manual — stored guidance that rides along to an agent reading the Dotabase, so it knows how the rows are meant to be used. See the Dotabase Operation Manual (DBOM).
• Three Ways In — the web app, the dots CLI, and any agent on MCP reach the same data, every read and write scoped to one company.

Get Started

• Create A Dotabase — the short path from nothing to a schema and a first row.
• Import From Markdown — when the knowledge already exists as a folder of files.
• Import Your Coding-agent Conversations — bring in your local Claude Code, Codex, and Cursor history.
• Publish A Dotabase To The Web — when a Dotabase is worth showing to people outside the workspace.

Resources

• How Dotabases Work — the anatomy, property by property.
• Views And Lenses — every view type, and how dashboards are assembled.
• Foundational And Internal Dotabases — the four seeded into every workspace, and the internal ones behind specific features.
• Conversations — the import-only Dotabase your dialogue lands in.
• DIIICE — the six-value taxonomy rows are classified against.
• Chat Overview — hold a conversation against these rows.