Agents
Recall within their readable envelope. Write directly — or as proposals, when you configure them that way.
recall,entity,deltaremember,forget
Teams & roles
Built for the whole team. Not just the bots.
Agents read and write. Humans decide what becomes the team’s truth. Each role does exactly what it should, and the database enforces the boundary — so a role is a permission, not a convention.
Contributors
The humans adding what they know — facts, evidence and pages, with their name on every change.
- Write and refine facts
- Attach evidence
- Raise flags
Curators
The team’s editors-in-chief. Nothing becomes canon without them.
- Accept or reject proposals
- Verify facts
- Publish playbooks
- Merge entities
Administrators
Own the boundary: who’s in, what they can read, and when that ends.
- Workspaces and includes
- Members and principals
- Revocation, effective going forward
- Imports, exports, legal holds
You do not need a team to start
The free developer plan is for one person with one connected agent, and it includes the governance features. A solo user is not a second-class tenant: you are the contributor, the curator and the administrator of your own workspace, and you can add people later without moving anything.
When you do add a team, roles are additive. A reader never needs a paid seat, and the same workspace boundary applies to agents and people alike.