Meditation Facilitation

The 4 R's — Expanded

Review — What happened this session?

• List concrete actions taken (files created, bugs fixed, features added)
• Identify surprising discoveries or unexpected connections
• Note what was harder or easier than expected and why
• Quality check: If the review is all "I did X, Y, Z" with no reflection, it's too shallow

Relate — How does this connect to existing knowledge?

• Which existing skills/instructions does this session's work touch?
• Are there cross-project patterns? (→ global knowledge candidate)
• Did this session reveal a gap in the architecture?
• Quality check: At least one connection identified, or explicitly note "isolated learning"

Reinforce — What's worth remembering long-term?

Filter aggressively. Not everything is worth persisting:

Record — Persist the right things in the right places

Facilitation Techniques

Socratic Probing

Don't just list what happened — ask why it matters:

• "What would you do differently next time?"
• "Is this a one-time fix or a recurring pattern?"
• "If you saw this in another project, would you recognize it?"

Diminishing Returns Detection

Depth Calibration

• Too shallow: "I learned about testing" → probe for specifics
• Right depth: "Property-based testing caught an edge case our unit tests missed because..."
• Too deep: 30 minutes on one function's implementation → zoom out to pattern level

Session Record Template

Store in .github/episodic/YYYY-MM-DD-topic.md:

# Meditation: [Topic]
**Date**: YYYY-MM-DD
**Type**: Quick Reflect | Deep-Dive | Full | Self-Actualization
**Duration**: X minutes

## Focus
What this session was about.

## Key Learnings
- Learning 1 (→ stored in [location])
- Learning 2 (→ connected to [skill/instruction])

## Updates Made
- File X: added/updated Y
- Synapse: connected A → B

## Open Questions
- What still needs investigation?

Synapses

See synapses.json for connections.