quaid-alerts

Memory state monitoring detects contradictions, resolved gaps, stale pages, and embedding drift by running periodic alert cycles after memory updates. It outputs per-line JSON alerts to stdout for downstream logging, dashboards, or MCP clients to enable timely remediation.

Automated monitoring notifications prevent alert fatigue through built-in deduplication timing and configurable suppression windows. These mechanisms suppress repeated alerts within set periods, ensuring only actionable memory state changes surface to downstream loggers or dashboards.

JSON alerts output directly to stdout as per-line objects for downstream logging, dashboards, or MCP clients. This structured format allows automated pipelines to parse and route memory state notifications like contradiction_new and page_stale efficiently.

Memory alerts detect four specific types after memory_put or memory_link operations: contradiction_new, gap_resolved, page_stale, and embedding_drift. Each alert type surfaces actionable brain state changes requiring timely remediation.

Automated alert cycles schedule to run after memory updates by triggering the monitoring process post memory_put or memory_link operations. Pipe each resulting JSON alert line directly to your downstream logger to capture brain state changes.

Suppression windows are configurable for memory state alerts, allowing control over deduplication timing. This configuration prevents alert fatigue by suppressing repeated notifications for the same contradiction or stale page within defined timeframes.