diff --git a/memory/2026-02-25-analytics-telemetry-collection-in-signetai.md b/memory/2026-02-25-analytics-telemetry-collection-in-signetai.md
new file mode 100644
index 000000000..1a7fe82f3
--- /dev/null
+++ b/memory/2026-02-25-analytics-telemetry-collection-in-signetai.md
@@ -0,0 +1,11 @@
+# 2026-02-25 Session Notes
+
+## Analytics & Telemetry Collection in signetai
+
+Nicholai asked how anonymous statistics about token usage, errors, and performance are collected in the signetai daemon. An exploration agent was dispatched to investigate the analytics system.
+
+Initial findings from `packages/daemon/src/analytics.ts` revealed that signetai uses an **in-memory analytics accumulator** for ephemeral counters during each daemon lifetime. The system does not persist analytics directly—instead, it relies on structured logs and the `memory_history` database table for durable backing of any metrics that need to survive restarts.
+
+Error tracking is organized by a **stage-keyed taxonomy** with six stages: extraction, decision, embedding, mutation, and connector. Each stage has specific error codes (e.g., EXTRACTION_TIMEOUT, DECISION_INVALID, EMBEDDING_PROVIDER_DOWN).
+
+Usage metrics include `EndpointStats` (count, errors, latency) and `ActorStats` (requests, remembers, recalls). Investigation was ongoing at session end.
\ No newline at end of file
diff --git a/memory/memories.db-wal b/memory/memories.db-wal
index 41ff3353f..f0f3640d8 100644
Binary files a/memory/memories.db-wal and b/memory/memories.db-wal differ