Explain

Turn a concept into one self-contained HTML file that reads like a good article: plain words, a natural flow, and visuals you can poke, placed exactly where the text needs them.

Simple language, not simple content. Cover the whole idea, including the hard parts. Make them easy to read; don't drop them.

Be brief. The page should be shorter than the source material would be. Every sentence, visual, and control earns its place or goes.

Input

A concept (science, math, CS, software design, system design, architecture, language internals...). Optional audience; default is a curious reader with high-school background. If the concept is ambiguous, pick the likeliest meaning, say so in one line, and go.

Research

Use WebSearch (load via ToolSearch if deferred) only when unsure what the concept is, when you need exact numbers or current behavior (runtimes, frameworks, protocols change), or when you can't state its limits. Standard mode first. Prefer textbooks, official docs, specs/RFCs, and authors' own papers. Cross-check every number you show. Skip search for things you know cold. Don't narrate it.

Writing the article

No section headings per template, no "Hook / Intuition / Recap" scaffolding. One continuous piece with a natural flow: