Back
The Workspace ModelPrimitives that compose.Synap doesn't ship features — it ships building blocks. Any data structure, any interface, any workflow emerges from the combination of a few simple primitives.
The product triptychEverything in Synap is one of three things.
Data
EntitiesUniversal data objects with typed profiles. A task, a note, a person, a deal — all entities. Properties define the shape. Relations connect them.
Lenses
ViewsNamed queries + rendering configs. Same data, different perspective. Switch from table to kanban to calendar — your data never moves.
Connections
ChannelsEvery conversation — with AI, with people, about an entity — is a channel. Connects users, AI agents, and external services.
14 entity types, infinitely extensibleSystem profiles ship with every pod. You and AI can create custom profiles. Profile inheritance (parent → child) lets you specialize without duplication.
note
task
project
event
person
contact
company
deal
bookmark
article
file
capture
website
anchor
+ custom
Infinite views — same dataViews are lenses over your data. A "Tasks" table becomes a "Sprint Board" kanban by changing the view type. The entities don't move. Only the perspective changes.
Table
Kanban
Calendar
Graph
Dashboard
List
Whiteboard
Flow
Feed
Gallery
Matrix
Masonry
+ build your own
The cell systemEverything visual in Synap is a cell. A cell renders in any container: full-screen page, side panel, bento grid widget, embedded in a document, or as a node on a whiteboard.
70+ built-in cellsStat cards, entity lists, kanban boards, calendars, AI chat, code editors — all cells.
AI can compose themAsk AI to build a dashboard. It picks from the library, configures each cell, and arranges them on a bento grid.
AI can create new onesAI can write entirely new cell types as HTML/JS components, sandboxed in iframes, proposal-gated.
The test
If a new feature requires special-casing in the codebase rather than composing from entity profiles, view types, and cell types — it's the wrong approach. Complexity should emerge from combining simple primitives, not from adding special cases.
This is why Synap can be a CRM, a project manager, a research tool, a personal wiki, and a knowledge graph — without being any of those things explicitly. They emerge from the same three building blocks.
