reflect
Capture when and why your understanding changed. Creates audit trail.
{ "tool": "reflect", "arguments": { "observation": "I was wrong about the auth flow. Tokens refresh client-side.", "about": ["node_old_belief", "node_new_evidence"] }}Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
observation | string | Yes | What changed in your understanding |
about | string[] | No | Related node IDs |
tags | string[] | No | Tags for organization |
Examples
Section titled “Examples”Correcting a mistake:
{ "tool": "reflect", "arguments": { "observation": "Previous belief about rate limits was outdated. API v2 doubled the limits.", "about": ["node_old_rate_limit", "node_new_rate_limit"] }}Noting a contradiction:
{ "tool": "reflect", "arguments": { "observation": "Documentation says X but code does Y. Need to verify which is correct.", "about": ["node_doc_claim", "node_code_behavior"], "tags": ["contradiction", "needs-verification"] }}When to Use
Section titled “When to Use”- You update a belief based on new evidence
- You notice a contradiction
- You correct a mistake
- Your confidence shifts significantly
The history of belief is as valuable as current belief.