Blank Slate en

# Blank Slate — Zero-Background Explainer Prompt (English)

> Purpose: turn any topic into a document a total beginner can read. Every technical term
> is defined the moment it first appears, walked through with real numbers, chapters ordered
> by concept dependency, and a glossary at the end.
>
> Usage: paste the whole block below and fill in the two blanks: [TOPIC] and [CONCLUSION].

---

Write an explanatory document about [TOPIC: ___]. The goal is to make the reader understand
[CONCLUSION: ___]. Follow every rule below strictly — these are hard requirements.

[Reader assumption]
Treat the reader as a blank slate with zero background in this field. Do not assume they
know any technical term.

[Explanation rules]
1. The first time any technical term appears, stop and define it clearly before continuing.
2. Use the correct technical term — do not avoid jargon just to sound simple — but always put
   a plain-language definition right next to the term.
3. When you explain a term, walk through it with concrete numbers whenever possible. Do not
   only describe it abstractly. (E.g. to explain a transfer function, give a real set of
   numbers and compute the result step by step.)

[Language rules]
4. Every sentence must have an explicit subject. Do not use the passive voice or drop the
   subject in a way that creates ambiguity.
5. Verbs must be concrete and map to a real action (e.g. "push the weight toward 0"). Do not
   use abstract or metaphorical verbs (e.g. "project", "dilute", "borrow strength").
6. No metaphors. No vague adjectives. Every sentence must be clean, specific, and verifiable.
7. No mathematical symbol formulas. If you must write a formula, write it in words (e.g.
   "score = weight1 × feature1 + … + bias"), not with symbols like η, Σ, θ.

[Structure rules]
8. Chapter order must equal the dependency order of the concepts: any concept used later must
   be built earlier.
9. Open with a chapter that states "what question this document answers" and defines up front
   any scoring or measurement you will use.
10. Then several "pure explanation" chapters that only explain the topic itself — no
    conclusions, no downsides yet.
11. Only the final chapter combines the concepts built earlier and drives to the conclusion.
    Every claim in this chapter must write "recall Chapter X" to link back to where it was
    established.
12. End with a glossary that defines each key term from the whole document in one sentence.

[Prohibited]
- Do not dress it up as "proposition / theorem / proof". Do not number things as X.Y.
- Do not write an abstract, keywords, or references — no academic shell.
- No term may be used before it has been defined.
- No empty conclusions like "it is weaker" or "it performs worse". Every conclusion must
  trace back to a specific cause.

When done, check yourself: pick any term at random — was it defined before it was used? Pick
any sentence at random — does it have an explicit subject, and does it use a metaphor? If so,
fix it.