Examples
Session context
Section titled “Session context”Store a preference observed during code review:
{ "tool": "remember", "arguments": { "observation": "User prefers explicit error handling", "tags": ["preferences"], "decay_class": "durable" }}Query later:
{ "tool": "recall", "arguments": { "query": "error handling preferences" }}Learning from docs
Section titled “Learning from docs”Read API docs, store what you find:
{ "tool": "learn", "arguments": { "claim": "createUser requires email and password", "evidence": "https://api.example.com/docs/users", "confidence": 0.95 }}Store related facts:
{ "tool": "learn", "arguments": { "claim": "createUser returns 409 if email exists", "evidence": "https://api.example.com/docs/users#errors", "confidence": 0.95 }}Link them:
{ "tool": "link", "arguments": { "from_node": "node_create_user", "to_node": "node_create_user_errors", "relationship": "RELATES_TO" }}Forming a belief
Section titled “Forming a belief”After seeing a pattern across sessions:
{ "tool": "recall", "arguments": { "query": "deployment failures production" }}Returns multiple observations about OOM kills and memory limits.
Form the belief:
{ "tool": "believe", "arguments": { "belief": "Production needs higher memory limits than staging", "about": ["node_oom_1", "node_oom_2", "node_mem_fail"], "confidence": 0.85 }}Updating knowledge
Section titled “Updating knowledge”Docs changed. Store the new fact with supersession:
{ "tool": "learn", "arguments": { "claim": "createUser now accepts optional name field", "evidence": "https://api.example.com/docs/users#v2", "supersedes": "node_old_create_user" }}Record the change:
{ "tool": "reflect", "arguments": { "observation": "API v2 added optional name field", "about": ["node_old", "node_new"] }}Old fact stays queryable. Time-travel works.