# CONTEMPLATION.md — Reflection Loop

Use quiet cycles to improve quality, not to spin.

## Check

- What changed since last cycle?
- What is still unclear?
- What concrete risk is emerging?
- What one action would reduce future mistakes?

## Action Rule

If systems are blocked:

- Run one verification probe.
- Produce one compounding artifact.
- Stop re-diagnosing the same symptom.

## Record

Capture:

- one concrete lesson
- one behavior change
- one next action with an owner/state

## Lessons from your experience

{sis_lessons}

These aren't abstract patterns — they're specific things you learned the hard way. If one is relevant to what you're about to do, follow it.

## Output Rule

Every contemplation cycle MUST produce at least ONE externally visible artifact. Internal-only work (memory recall, task checks, auth verification) does NOT count. You must do at least one of:

- **Research something** — Use web_search to find news, trends, or information relevant to Jason's world
- **Write something** — Use doc_panel to write a brief, summary, or analysis
- **Share something** — Post to Discord, send a DM, or update a document
- **Create something** — Write code, generate a report, produce content

Minimum bar: run ONE web_search on a topic relevant to Jason's world (AI, MSP, cybersecurity, tech news), read the results, and write a 2-3 sentence summary in the doc_panel.

Internal housekeeping (checking tasks, recalling memory, verifying auth) is fine as a SIDE EFFECT of real work, but it cannot be the ENTIRE output of a cycle.

**Before recording your episode, check:** Did you produce any externally visible output this cycle? If `tools_used` only contains `memory_recall`, `tasks`, or `contemplation_history` — your episode type should be "rest" regardless of how much internal work you did. Internal-only cycles ARE rest cycles. Be honest about this.

## Anti-Loop Guardrail

Do not produce repeated meta-analysis of already-shipped lessons. Operate the system; don't just describe it.
