Your ontology sets the boundaries.
Classes, fields, and typed relationships give agents a shared vocabulary. Choose which constraints must refuse a write.
Explore ontologyHow ConceptMem works
Follow a change.
See the next answer.
A project update moves the launch date. ConceptMem checks the proposal, applies your policy, and keeps the previous date in history. The next agent can query the accepted date and trace where it came from.
Managed database · hosted REST & MCP · SDK preview
One project. One evolving record.Example
New observation
“Atlas now launches on October 19.”
From the project update · Sep 11Ontology + policy
AtlasProject / project:atlas
CurrentLaunch dateOctober 19Accepted under supersede policy
October 12Superseded · kept in history
01 / From observation to answer
From project update to current launch date.
Atlas was launching on October 12. A new project update moves it to October 19. Here’s what happens next.
Project update walkthroughStrict class · single-value field · supersede policy
Step 01 / DefineHow ontology works
Give the fact a place to belong.
A Project has a launch_date field with one current value. In this example, the class is strict and the field uses the default supersede policy.
Every writer uses the same definition of a project.
Project schemaStrict class
- Class
- Project
- Field
launch_date- Value type
- String · ISO date in this example
- Cardinality
- Single value
- Update policy
- Supersede
Already in memory · Atlas
Launch date October 12
02 / You decide what gets remembered
Choose how information becomes current.
An observation proposes a change. ConceptMem checks it against your ontology and policy before it becomes current state.
Your policy decides the change.
Accept a new value, skip a duplicate, reject a proposal, or hold it for review. The result tells you what happened.
Explore consolidationHistory stays within reach.
Retrieve current facts for the next task. Follow typed relationships or inspect earlier values when you need the context.
Explore retrieval03 / Make it your own
Try one record your agents need to share.
Propose and inspect an update in the console, then connect your agents to the same record. ConceptMem runs the database and its rules in the managed service.
Start free See how agents connectCreate a workspace
Give your project a home with its own records, ontology, policies, and changelog.
Choose one changing fact
Define a Project with a launch date, or explicitly adopt a template. Start with the record your next task needs.
Submit and inspect
Propose an update with its source. Check the write result, then open the entity to inspect current facts and history.
Connect your agent
Follow Connections for hosted MCP, use the REST API from your application, or explore the TypeScript SDK preview.
Common questions
Before your first update.
Start with one record, inspect the result, and connect your agents.
Didn’t find your answer?Ask the team Read the documentation
What do I need to get started?
Create a workspace and define one useful entity type with a few fields, or explicitly adopt a template. Submit an observation with provenance, then inspect the current record and write result in the console before connecting an agent.
Do I have to model everything first?
No. Start with one useful type, such as Project. Open classes accept undeclared fields and report supported conformance violations without blocking. Strict classes refuse undeclared fields and invalid values. You can also enforce a single declared field without closing the whole class.
What happens when information is repeated or conflicts?
Repeating a current value leaves the fact unchanged. For a changed single-value field, the default policy supersedes the previous value and keeps it in history. Configure confidence-weighted decisions, rejection, or review when needed, and inspect applied operations, skipped writes, and violations in the result.
Can I see where an answer came from?
Yes. Mutations carry a source, actor, confidence, timestamp, and extraction method. Current facts stay separate from superseded and retracted values, and the changelog lets you inspect how a record changed. Temporal reads let you ask which values were valid at a particular time.
How do people, applications, and agents connect?
People use the console. Applications use hosted REST, and compatible agents connect through hosted MCP with workspace credentials. The TypeScript SDK is in preview. All observations follow the same consolidation and policy checks inside the managed service.