Consolidation

Namespaces improve with age. A background consolidation pass periodically groups corroborating facts and synthesizes observations — memory units that state what the evidence repeatedly shows.

Facts: "Ada fixed the payments retry bug", "Ada shipped the payments rewrite", "Ada reviewed the payments oncall runbook"

Observation: "Ada is the payments domain expert."

Properties

• Observations carry the observation fact type and are never written directly — consolidation is their only source.
• Each observation links to its source facts. Recall can inline them with include_source_facts.
• Consolidation is incremental and idempotent; it does not duplicate observations for evidence it has already folded in.

Control

• Enable or steer synthesis per namespace via config (enable_observations, observations_mission).
• Trigger a pass on demand with POST /consolidate (meters as a reflect operation).
• Recover a stuck run with POST /consolidation/recover.
• Clear synthesized observations — namespace-wide or per memory — and the next pass rebuilds from surviving evidence.

Observations in recall

The REST recall endpoint includes observations by default (types narrows this). They rank by the same relevance/recency/corroboration scoring as other memories, and corroboration is where observations shine — they carry the weight of every source fact behind them.