memory-debugger

Debug memory by inspecting profile.md, diary entries, and trust matrices to identify inconsistencies between recorded events and agent state. Use file-system access to read memory contents, validate updates align with actual events, and diagnose where trust or profile data diverged from expected behavior.

Agent memory consists of profile.md (agent identity and metadata), suspects.csv (trust matrix tracking confidence in other agents), and diary entries (timestamped event logs). These files must stay synchronized; misalignment between them signals memory corruption or stalled updates.

Validate memory by cross-checking diary timestamps and events against corresponding trust matrix changes. Read both files to confirm each diary entry has a corresponding trust update, and verify the chronological sequence is consistent across both records.

Yes. Inspect the agent's profile.md, diary, and suspects.csv to identify where updates stalled. Check for corrupted entries, missing diary records, or trust matrix inconsistencies that prevent the agent from processing new information and updating confidence scores.

Navigate to the agent's memory directory (data/memories/player_ID/), list all files to verify structure, then read profile.md and diary entries sequentially. Examine suspects.csv to inspect the trust matrix, checking for gaps or anomalies that explain memory behavior.

Yes. Memory debugging requires direct file-system access to read and validate profile.md, suspects.csv, and diary entries stored on disk. This allows precise inspection of memory state and history without relying on agent APIs.