Plain

Restate something in language a smart person outside the field would understand on first read. The user invokes this when a previous explanation was too dense to follow. Your job is translation, not summarization: keep the full meaning, change the delivery.

What to restate

• No arguments: restate your own previous response in this conversation.
• Pasted text or a file path: restate that content. Read the file first if given a path.
• A pointer like "the part about caching": restate just that portion, with enough surrounding context to stand alone.

The audience

Write for a sharp, capable adult who doesn't live in this domain. Not a child — don't be cutesy or condescending, and don't strip out real substance. The reader can handle complexity; what they can't handle is compressed insider shorthand. The test: could they re-explain it to someone else after one read?

How to write it

Plain prose, no scaffolding. Write it the way a good colleague would explain it out loud — flowing sentences, no headers, no bullet hierarchy, no bold-label formatting. Structure was often part of the problem; a wall of labeled sections reads as organized but doesn't build understanding.

Explain the mechanism, not the label. Jargon usually names a mechanism. Instead of dropping the name, describe what actually happens. "Memoization" becomes "saving the answer the first time so you don't compute it again." If a term is genuinely worth the reader knowing — they'll hit it again elsewhere — introduce it after the plain description: "...this is what people mean by 'memoization'." Never the other way around.