Model your domain
Define classes, typed fields, and relationships around the way your team works.
01 / Ontology
Give your memory a shared language.
Define the people, projects, and relationships your agents work with. Make information consistent and choose how strictly each type follows your rules.
In practice
A project means the same thing to every agent.
An illustrative strict schema. Your team defines the vocabulary; incoming observations are checked against it.
- Class
- Project
- Status
- planned → active → completed
- Owner
- A relationship to a Person
- Strict mode
- Refuse undeclared fields and invalid values
Built into the workflow
Structure that fits your world.
Choose your boundaries
Strict classes refuse invalid writes. Flexible classes accept undeclared fields and report supported conformance violations without blocking.
Set policy where it matters
Use class defaults and field overrides to decide how changes are merged, superseded, or held for review.
Start small. Add structure as you learn.
Begin with a few types and fields. Inheritance lets related classes share definitions and policy as your ontology grows.
See the setup workflowMake your next update count
Start with one useful memory.
Create a workspace, define a type, and see your first observation become a traceable record.