Consolidation

Namespaces improve with age. A background consolidation pass periodically groups corroborating facts and synthesizes signals: 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"

Signal: "Ada is the payments domain expert."

Properties

• Signals carry the signal fact type and are never written directly. Consolidation is their only source.
• Each signal links to its source facts. Search can inline them with include_source_facts.
• Consolidation is incremental and idempotent; it does not duplicate signals for evidence it has already folded in.

Control

• Enable or steer synthesis per namespace via config (enable_signals, signals_mission).
• Trigger a pass on demand with POST /consolidate (meters as an illuminate operation).
• Recover a stuck run with POST /consolidation/recover.
• Clear synthesized signals, either namespace-wide or per memory, and the next pass rebuilds from surviving evidence.

Signals in search

The REST search endpoint includes signals by default (types narrows this). They rank by the same relevance/recency/corroboration scoring as other memories, and corroboration is where they pull ahead: a signal carries the weight of every source fact behind it.