NIGHTRAVEN IMPROVEMENT LOOP CYCLE PROMPT

# NightRaven Improvement Loop — Cycle Prompt

**Purpose:** One cycle incrementally improves NightRaven (portable + wired repos) as if **six specialist teams** reviewed the framework in parallel — Brent stays one person; the loop compounds memory without manual role-switching.

**Authority:** Master `docs/37_NIGHTRAVEN.md` §9 (virtual teams + loop law), §10 (Tier C — Creator-Innovator). Repo overlays extend locally only.

**Laws (non-negotiable):** Always watches · Always learn · **`+#` only** · Never `-#` · Supersedes for corrections · One small improvement per cycle · **Always sync, approval-aware** (fetch/pull before; push after approved commit or record explicit defer).

**Execution mode:** If running under LM Studio (local), run six audits **serially** — no parallel subagents. If running under a cloud frontier model (Anthropic, Google, OpenAI), parallel subagents and full six-team lens are allowed. See [`NIGHTRAVEN_LOCAL_VS_CLOUD_EXECUTION.md`](NIGHTRAVEN_LOCAL_VS_CLOUD_EXECUTION.md) §4.

**Default posture:** **Tier C — Creator-Innovator leads** (doc 37 §10). Tier C **opens** each cycle and **leads synthesis**; Architecture, Engineering, Design/UX, QA, and Product are **supporting** passes. Product/QA still **win** on boundary and anti-pattern conflicts — Tier C revises the proposal, not the law.

### Sixty-second cycle

| Step | Action |
|------|--------|
| 1 | **Tier C opens** — craft bar + human-world gate |
| 2 | **Five support audits** — Architecture → Engineering → Design/UX → QA → Product |
| 3 | **Tier C synthesizes** — pick **one** `+#` improvement |
| 4 | **Wire + log** — cross-links; append changelog / learning log / handoff |
| 5 | **Report** — one short paragraph; defer the rest |

---

## How Brent starts this loop

Pick a cadence and paste into Cursor chat (Agents window):