Wheat

The problem

You're about to mass-migrate 200 microservices. The decision is based on a Slack thread, a blog post, and a gut feeling from someone who left the company.

Claude contradicts itself over long sessions. Decisions accumulate silently conflicting evidence. And nobody notices until the migration is six months in and the original assumptions were wrong.

**You'd never ship code without tests. Why ship a decision without validated evidence?**

What wheat does

Wheat is a CLI that turns your AI coding tool into a structured research engine. Every finding becomes a typed, evidence-graded claim. A 7-pass compiler catches contradictions, flags weak evidence, and blocks output until issues are resolved.

You investigate  →  Claims accumulate  →  Compiler validates  →  Brief compiles
  /research          typed + graded        catches conflicts      backed by evidence
  /prototype         with evidence tiers   blocks on issues
  /challenge

The result: a decision document backed by validated evidence, not vibes.

Quick start

npx @grainulation/wheat "Should we migrate from microservices back to a modular