Writes are proposals
Incoming observations go through consolidation before they update current state.
Our approach
Memory you can inspect and govern.
Useful agent memory needs clear rules for what changes, what stays current, and where information came from. These principles shape ConceptMem.
In practice
An answer with a history behind it.
The system governs recorded knowledge. The quality of that knowledge still depends on the observations and policies you provide.
- Current state
- The accepted facts available to the agent.
- History
- Superseded and retracted values kept separately.
- Provenance
- The origin and context of each mutation.
- Policy
- The rules used to decide how an update lands.
Built into the workflow
Seven principles behind every record.
Consolidate, do not append
Repeated and conflicting observations are handled as updates to coherent records.
Separate current state and history
Keep the accepted record distinct from previous values and the changelog.
Let the ontology govern
Classes, fields, and relationships define your model. Strictness determines when non-conformance refuses a write.
Require provenance
Every mutation carries source, actor, confidence, timestamp, and extraction method.
Treat projections as views
Markdown and exports derive from memory. Editing them does not change stored state.
Make policy pluggable
Merge, conflict, retention, privacy, and review settings belong in explicit policy.
See the principles in action.
Follow a new observation from submission through consolidation to a queryable record.
Explore the 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.