Collapse repeated information
Repeated values on a resolved entity consolidate into its existing record.
02 / Consolidation
Let memory change with the facts.
A new observation should improve the record. ConceptMem checks incoming information, resolves updates under your policy, and preserves the history behind every change.
In practice
One update. A clear record of what changed.
Example using a single-value field with supersede policy. Other policies can reject a change or hold it for review.
- Previous value
- October 12 · superseded
- New observation
- The launch has moved to October 19.
- Current value
- October 19 · after consolidation
- Provenance
- Source, actor, confidence, timestamp, extraction method
Built into the workflow
Make every update accountable.
Handle disagreements deliberately
Use deterministic updates or opt into confidence-weighted arbitration. Require review for changes that need a human decision.
Explain the outcome
Applied operations, skipped writes, and ontology violations tell you what happened to each proposal.
Keep the evidence behind the answer.
Superseded and retracted facts remain separate from current knowledge. The changelog records mutations with provenance so you can inspect how a record evolved.
Explore current state and historyMake your next update count
Start with one useful memory.
Create a workspace, define a type, and see your first observation become a traceable record.