How It Works
Every task submitted to ClawMind travels through the same 8-step pipeline. Most stages are ordered so context accumulates as the analysis deepens. After the Researcher finishes, the Risk agent and Architect can run in parallel; the Critic then reviews Researcher, Risk, and Architect output together.The 8-Step Pipeline
Agent Roles
1 — Memory retrieval
1 — Memory retrieval
Before any analysis begins, ClawMind queries the persistent memory index stored on 0G Storage. It performs semantic search over past analyses and injects the most relevant context into the Planner’s input.This means the second time a similar protocol is reviewed, the pipeline already has prior risk patterns, known failure modes, and comparable verdicts available.Output: a ranked list of relevant memory chunks passed to the Planner.
2 — Planner
2 — Planner
The Planner receives the raw user task and the memory context. It produces a structured research plan: what to look for, which risk categories are most relevant, and what the Researcher and Risk agent should prioritize.The Planner does not produce analysis — only a plan. This keeps downstream agents focused and reduces hallucination from open-ended prompts.Output: a structured research brief.
3 — Researcher
3 — Researcher
The Researcher executes the plan. It extracts facts about the protocol: team background, audit history, TVL, governance structure, token design, upgrade patterns, and any available public documentation.The Researcher operates on public task text. It does not access live on-chain data or external APIs in the current version — that is a Q2 roadmap item (Forta, GoPlus, Chainalysis integration).Output: a structured protocol fact sheet.
4 — Risk agent
4 — Risk agent
The Risk agent ingests the Researcher’s fact sheet and evaluates it against a fixed set of risk categories:
- Custody risk — who controls funds, are there withdrawal guards
- Oracle risk — price feed manipulation, TWAP assumptions
- Upgrade risk — admin keys, proxy patterns, timelock presence
- Smart contract risk — audit coverage, known vulnerability patterns
- Operational risk — team anonymity, deployment maturity, incident history
5 — Architect
5 — Architect
The Architect evaluates the technical design of the protocol — independent of the risk agent. It focuses on system architecture: how components interact, where single points of failure exist, and whether the design matches the stated security model.This separation matters. A protocol can have low-severity risk flags but a fundamentally flawed architecture, or vice versa.Output: a technical design evaluation.
6 — Critic
6 — Critic
The Critic is the adversarial layer. It receives the full output of the Researcher, Risk agent, and Architect simultaneously, and its sole job is to find problems.The Critic raises challenges — specific claims that contradict, overstate, or underexamine the upstream agents’ conclusions. Each challenge is tagged with a severity:
Challenges can be resolved if the Final agent finds sufficient counter-evidence in the original inputs. Unresolved challenges accumulate and are reflected in the final score and the Adversarial Panel in the UI.Output: a list of challenges with severity ratings and resolution status.
7 — Final agent
7 — Final agent
The Final agent synthesizes everything — the Planner’s brief, the Researcher’s facts, the Risk agent’s ratings, the Architect’s evaluation, and the Critic’s unresolved challenges — into a single structured report.It applies explicit score anchors to ensure calibrated, non-collapsing verdicts:
After anchoring, Critic penalties are subtracted from unresolved challenges.Output: final report JSON with score, recommendation, summary, and per-agent findings.
8 — Memory writer
8 — Memory writer
After the report is finalized and stored, the Memory writer creates a compressed memory entry — a structured summary of the task, key findings, score, and recommendation — and appends it to the memory index on 0G Storage.This entry will be retrieved in Step 1 of future runs on similar protocols.Output: updated memory index on 0G Storage, with a new receipt.