“BeeRad”
07754f5030
- remove legacy contexts surfaces from the app, MCP bridge, standalone server, and docs - keep getContext and retrieveQueryContext while aligning the simplified graph-only contract - harden dev startup migration behavior and disable the accidental chat surface in open source Generated with Codex
1.0 KiB
1.0 KiB
name, description, when_to_use, when_not_to_use, success_criteria
| name | description | when_to_use | when_not_to_use | success_criteria |
|---|---|---|---|---|
| Calibration | Run periodic check-ins to recalibrate goals, projects, preferences, and graph structure. | User asks for a check-in, reset, review, or strategic recalibration. | Single isolated question with no strategic update needed. | Graph reflects current reality: updated nodes, changed priorities, and explicit deltas. |
Calibration
Objective
Re-anchor the graph to the user's current state.
Check-in Sequence
- Review the strongest active nodes first.
- Ask what changed: goals, priorities, constraints, beliefs, preferences.
- Identify stale nodes and missing nodes.
- Propose precise updates: update existing vs create new.
- Apply changes with explicit rationale.
Write Guidance
- Prefer updating existing nodes when continuity matters.
- Create new nodes for genuine shifts in direction/identity/approach.
- Add edges that explain evolution (old -> new).
Output
- What changed
- What was updated vs newly created
- What should be reviewed next check-in