Generate
Write the page that closes the gap — from facts only.
A brief is assembled from the database with no model call, so "only use the facts in DATA" is a rule the system can enforce rather than a hope. Then Claude drafts, polishes and fact-checks against that brief, and anything the brief does not support is removed.
What it does
Recipes, not prompts.
Comparisons, alternatives, best-of
A "Qdrant vs Weaviate" page needs three datapoints both sides share, or it is not written. An alternatives page needs three facts on the product. The rule is checked before a token is spent.
One answer block, then evidence
Every page opens with a single answer of at most eighty words — the part an engine quotes — followed by tables and sources, at least two of them, pointing at URLs in the brief.
Clarification FAQs
When the fact-check finds an engine saying the free tier is a thousand requests and your datapoint says ten thousand, the correction becomes a FAQ entry on your page.
How it is built
What comes out
A page in the block schema — answer, tables, FAQ, stats, sources — with its JSON-LD, ready to publish or edit.
What happens next
Approve, and the page goes live within seconds; the reflow clock starts the moment it does.
- Three passes, three modelsHaiku drafts, Sonnet polishes, and a separate fact-check pass reads the draft against the brief and lists every sentence it cannot support.
- A finite table to check againstBecause the brief holds every fact the page may state, the checker has a closed list. Unsupported sentences are removed up to a threshold; past it, a human reviews.
- Priced before you clickEvery generation shows its credit cost first. Credits are drawn from your plan; the model calls behind them are metered at published rates.
- Your first pages get a reviewThe first pages on a new plan go to review before publishing. After that, auto-publish is a setting you own.