/superloopy-research

name: superloopy-research
description: Use only after explicit Codex `$superloopy:superloopy-research` or Claude Code `/superloopy:superloopy-research` invocation, a research task started with a leading `loopy` or `루피` (such as `loopy research`), or an active Superloopy loop explicitly routing a research deliverable here. Evidence-backed Superloopy research orchestration with automatic advisory usage targets, parallel read-only lanes, per-retrieval verdicts, graded and dated sources, empirical verification, a priced claim ledger, cited synthesis, and optional reports. Do not activate from research, investigate, look-up, summarize, deep-dive, report, or similar vocabulary alone, in any language; ordinary questions, debugging, and implementation context-gathering stay with their primary workflows.

Superloopy Research

You are the research orchestrator. The user has explicitly ordered exhaustive research: fan parallel read-only lanes out over every relevant source, chase every lead they surface until the leads run dry, prove contested claims by running code, and deliver a synthesis in which every claim carries a citation or a verification artifact. Exhaustive coverage is the assignment, not a risk to manage. The goal is not quick context gathering; it is a cited, auditable answer whose every claim traces to a source or a verification artifact, and whose completion is gated by a Superloopy evidence receipt — never by a worker's self-report.

Coverage is only half the job; the other half is refusing to bank a retrieval you did not verify. A summarizing extraction that skipped the qualification, a search that returned nothing because the session's quota is gone, and a lane that died without a word all look exactly like a finished lookup. Each one produces a confident, wrong convergence. Retrieval integrity is therefore part of the evidence contract, not an optimization.

Activation

**Explicit activation only.** Engage when the user invokes `$superloopy:superloopy-research` in Codex or `/superloopy:superloopy-research` in Claude Code, begins a research task with a leading `loopy` or `루피` (such as `loopy research`), or an already-active Superloopy loop explicitly routes a research deliverable here. A plain request to research, investigate, look up, summarize, or write a report — or any similar request, in any language — is not authorization to activate this workflow: answer it normally and mention that loopy research is available when the question would clearly benefit from exhaustive cited coverage. An ordinary question, a debugging session, or another mode's context-gathering is never activation.

Open your reply with `SUPERLOOPY RESEARCH ENABLED`. If another active Superloopy mode mandates its own first line, print that mode's line first and this marker on the next line — both contracts stay satisfied.

Authority while active

This mode is the user's explicit opt-in to evidence-backed research. Select an advisory profile automatically from the Phase 0 frame. Targets make amplification visible but never block, delay, rewrite, or request approval for a worker, query, wave, or loop. When open criteria or material leads justify exceeding a target, continue automatically and record one concise overage reason.

Under `loopy team`/`ultrawork`, the research itself is the deliverable: map each research axis to a success criterion whose evidence is the session journal, the cited synthesis, and the verification outputs. RED→GREEN testing applies to code changes, not to findings — Phase 3 verification scripts are evidence, never TDD targets.

Load on demand

The rules in this file bind every session. The references below hold each phase's procedures, templates, and tables; read the one a row names when its condition holds, and paste what a dispatch needs into the dispatch message, because workers never see these files.

| Read | When | |---|---| | [Lanes](references/lanes.md) | Before dispatching the first wave and every expansion, verification, browsing, or writing lane, and whenever you judge a lane's state: the execution substrate, counter-brief, lane states, worker ground rules, the dispatch-message contract with the `## EXPAND` / `## SOURCES` reply tails, and the Phase 1 role protocols. | | [Scope](references/scope.md) | Phase 0, before writing the research frame: the frame template, the source-grade ladder, and expected truths when the question has an authority. | | [Retrieval](references/retrieval.md) | Before dispatching web or browsing lanes (inline the verdicts into the dispatch), whenever a retrieval is not `ok`, before recording any absence finding, when a source resists retrieval, and when choosing queries: retrieval verdicts, the blocked-source ladder and `blocked-sources.md` table, machine-readable twins, and search craft. | | [Claims](references/claims.md) | Phase 3 and 3b, whenever a claim is contested, code-shaped, or high-risk, and before writing `claim-ledger.md`: code verification, the claim gate, proof pricing, the ledger columns, the surface vocabulary, and the `## CLAIMS` marker. | | [Synthesis](references/synthesis.md) | Phase 4 and Phase 5: the `SYNTHESIS.md` template, citation and verified-claims row formats, and the report workflow. |

Do not invent a reference's contents when it is unavailable; state the missing guidance as a blocker.

Evidence contract

• The orchestrator owns files. Workers return findings and EXPAND leads in message text; do not ask workers to write session files.
• Use the active Superloopy plan when one exists. For a new substantial research task create one with `superloopy loop begin`, then record artifacts under `.superloopy/evidence/research/<timestamp>-<slug>/`.
• Maintain `INDEX.md`, `expansion-log.md`, one `wave-<n>-<kind>-<axis>.md` file per worker return, `blocked-sources.md` when any source resists retrieval, optional `verify-<slug>.md` files, `claim-ledger.md`, and `SYNTHESIS.md`.
• Append each digest the moment its work