Grainulator
Research that compiles.
Ask a question. Get a multi-pass investigation with typed claims, tension detection, and a confidence-graded answer. Not a chatbot — a research sprint that runs in under 60 seconds.
What it does
- Multi-pass investigation — 3 research passes build evidence from different angles before synthesizing an answer
- Typed claims, not vibes — every finding is tagged as factual, constraint, risk, recommendation, or estimate with an evidence tier (stated / web / documented / tested / production)
- Tension detection — the compiler finds contradictions between claims and surfaces them before generating output
- Confidence scoring — a 7-pass compiler grades evidence strength, type coverage, and bias to produce a 0-100 confidence score
Try the demo
grainulator.app runs a sprint in your browser. Type a question, watch three research passes execute, and see the compiled answer with claim breakdown.
What to expect from a single sprint:
| Metric | Typical value |
|---|
| Claims generated | 12-16 |
| Claim types | 5 (factual, constraint, risk, recommendation, estimate) |
| Tensions detected | 3-6 |
| Evidence tiers | web, documented, stated |
| Confidence score | 63-68 / 100 |
| Time to answer | 40-70 seconds |
The demo runs client-side to show the pipeline. The real tool (installed as a plugin) uses Claude for substantially higher quality research and deeper evidence.
Install
Step 1 — Add the marketplace (one-time):
claude plugin marketplace add https://github.com/grainulation/grainulator.git
Step 2 — Install:
claude plugin install grainulator
Inside Claude Code, use /plugin instead of claude plugin.
That's it. The plugin registers MCP servers, skills, hooks, and an autonomous agent.
Requirements: Claude Code with Node.js >= 20.
Alternative: clone directly
git clone https://github.com/grainulation/grainulator.git ~/.claude/plugins/grainulator
claude plugin add ~/.claude/plugins/grainulator
Team deployment
Commit to your project's .claude/settings.json:
{
"enabledPlugins": ["grainulator@grainulation-marketplace"]
}
For air-gapped environments, use CLAUDE_CODE_PLUGIN_SEED_DIR with the plugin baked into container images.
Troubleshooting
MCP server disconnected / "tool not found". Claude Code's MCP
registry occasionally drops stdio-connected servers (sleep, network
hiccup, long-running session). Re-add the affected server:
claude mcp add wheat -- npx -y -p @grainulation/wheat wheat-mcp
claude mcp add mill -- npx -y @grainulation/mill serve-mcp
claude mcp add silo -- npx -y @grainulation/silo serve-mcp
Or run /healthcheck from any grainulator-enabled session to verify
all three servers are responding and get the exact fix command for
any that aren't.
Plugin commands not showing up. Restart Claude Code after
claude plugin install — plugin registration is read at startup.
Permission prompts from hooks. Grainulator's hooks (pre-compile,
post-claim) need .claude/settings.json permission. On first use
Claude Code will prompt; allow, or pre-approve in your user or
project settings.
How it works
You ask a question. Grainulator runs a research sprint.
The sprint has two phases:
1. Investigation (3 passes)
Each pass approaches the question from a different angle — constraints, risks, alternatives — and produces typed claims. Claims accumulate in claims.json, the sprint's evidence ledger.
2. Compilation (7 passes)
The compiler runs seven analysis passes over the collected claims:
