alfa-search-recall-deepresearchlisted

# 🅰️ Alpha Protocol — Recall + Deep Research before deciding > 🧒 **When reporting to the operator:** end with a child-simple "In plain words" recap (his standing request; reports TO the operator only). **Binding rule (must):** For ANY new strategic function, product, business model, tokenomics, AI-functionality, GTM, market, investment hypothesis, or architecture decision — it is **FORBIDDEN to go to implementation on recall alone**. Do `Recall → Gap → Deep Research → Synthesis → Decision Memo` first. Recall is necessary but NOT sufficient for strategic work. Canon: vault note `protocol-alpha-protocol-recall-plus-deep-research`. ## When this fires - The operator writes the trigger: **`R+DR`** (= **`RDR`** — `+`/space & case don't matter), **`alpha protocol`** (or `/alpha`). - OR you are about to start a **Level-2** task (below) — invoke this protocol proactively, don't wait for the trigger. ## Levels (size the response to the task) - **L0 — Quick** (answer a question, fix a bug, tiny tweak): plain recall is enough. No DR. - **L1 — Recall** (new module / hypothesis / feature / market): recall memory + internal docs + past research + form hypotheses. **Do NOT decide immediately.** Usually no external DR unless it turns strategic. - **L2 — Recall + DR** (strategic — see binding rule): run the full flow below. ## ★ Proactive multi-agent reflex (EVERY task, not just strategic) — set 2026-06-25 The user FORGETS whether they need agents — so YOU remember and propose, reflexiv