docs(sf): clarify memory-sleeper.ts is NOT part of the memory pipeline
memory-sleeper.ts had no file header and the "memory" prefix is misleading — it's a runtime tool-output watchdog (detects repeated bash failures, too-large tool results) that emits steers, completely unrelated to memory-store / memory-relations / memory-embeddings. A contributor reading directory listing top-down would reasonably assume this file participates in the same pipeline as the other memory-*.ts modules. Header now states the historical naming and points readers in the right direction. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
e10511ce38
commit
ec4dab450b
1 changed files with 9 additions and 0 deletions
|
|
@ -1,3 +1,12 @@
|
|||
// SF Memory Sleeper — runtime tool-output watchdog
|
||||
//
|
||||
// Despite the "memory" prefix, this module is unrelated to the
|
||||
// memory-store / memory-relations / memory-embeddings pipeline. It
|
||||
// observes tool-result events at runtime and emits a steer (info /
|
||||
// warning) when patterns like a repeated bash failure or a too-large
|
||||
// tool result indicate the agent is stuck. Naming is historical —
|
||||
// "sleeper" means a dormant watcher, not a stored memory.
|
||||
|
||||
import type { ToolResultEvent } from "@singularity-forge/pi-coding-agent";
|
||||
|
||||
export interface MemorySleeperSteer {
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue