essay

これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。

---
name: essay
description: Write a derivation-quality essay answer to a 213-concept question. Uses the derive+cite+dual-function+cross-frame+self-check+constructive-accessibility protocol to produce an essay that simultaneously interprets a classical concept and refines the 213 narrative.  Triggered by "essay" / "essay", "에세이", "교과서" / "교과서", "교과서 쓰기" / "교과서 쓰기", "213-style answer", "Mingu-style answer", "what is X (in 213)", "X가 213에서 뭐야".
---

# Essay derivation — 213-native concept exposition

A 213 question (limit / completeness / equality / residue / gauge / ...)
deserves more than a wiki paragraph or a Lean module pointer.  It
deserves an **essay** that simultaneously interprets the classical
concept (packaging stripped per G6 §0) and refines the 213 narrative
(operational primitive made syntactic).

This is the format `theory/` book content takes **on top** of the
89-chapter catalog index.  Catalog = static AST + reference.  Essay =
on-demand trajectory through catalog nodes for a specific query Lens.

## When to invoke

Trigger on:
  - "X가 뭐야 (in 213)" / "what is X" foundational questions
  - Concept clarifications (limit, completeness, equality, infinity,
    residue, set, function, distinguishing, gauge, ...)
  - Re-framings ("how does 213 see X?")
  - Adversarial probes ("does 213 have Y?", "where does 213 fail?")
  - Cross-concept connections ("how do X and Y relate?")

Do NOT invoke for:
  - Implementation tasks (Lean code, build verification, file moves)
  - Pure factual lookup ("what's in chapter X?")
  - Navigation ("where is Y defined?")
  - Already-answered questions

## Protocol (6 steps)

### 1 — Identify the 213-native target

Locate the `theory/` chapter(s) + `lean/E213/` modules + `seed/AXIOM/`
sections containing the 213-native expression.  Examples:

| Concept | Primary targets |
|---|---|
| limit | `theory/math/analysis/modulus.md` + `theory/math/analysis/cauchy.md` |
| completeness | `theory/math/numbersystems/real213.md` |
| equality | `theory/lens/algebra.md` + `theory/lens/universal.md` |
| residue | `seed/AXIOM/01_residue.md` + `theory/math/foundations/universe_chain.md` Möbius P |
| gauge | `theory/physics/symmetry/c3_chain.md` |
| infinity | `seed/AXIOM/06_lens_readings.md` §6.7 + `Lib/Math/Foundations/ResolutionLimit.lean` |

If no clear chapter exists, the concept may not be promoted yet —
flag this honestly; do not invent.

### 2 — State 213-native answer first (NOT classical contrast)

Open with the operational definition.  Do NOT lead with "in classical
math X means..."  — that imports the classical/213 dichotomy.

Bad: *"In classical analysis, a limit is ε-δ defined.  In 213,
instead, we use explicit modulus..."*

Good: *"A sequence paired with an explicit modulus function
`f : Nat → Nat`.  The pair IS the limit."*

### 3 — Derive from catalog with citations

Citations ARE the derivation, not bibliography.  Each claim points to
`theory/.../X.md` or `lean/E213/.../X.lean` or
`research-notes/G##_X.md` or `seed/AXIOM/##_X.md`.

Multi-chapter derivations are stronger than single-chapter
paraphrases.

### 4 — Dual function: interpretation + refinement in one move

After 213-native derivation, surface the dual:
  - **Interpretation**: this answer is the classical concept with
    redundant packaging stripped (per G6 §0 corrected position)
  - **Refinement**: 213's specific reading is sharper here

These are ONE act, not two paragraphs — per the dual-function
structural fact.

### 5 — Discover cross-frame connections

Watch for moments where the same structural fact appears in multiple
frames (atomic / Möbius / Lens / §8 / §9.2 / G31 / ...).  Surface
explicitly when discovered:

> "§8.1 no-exterior + §9.2 op-object non-separation + P(φ) = φ
> fixed-point + G31 trajectory-as-witness — same fact, four
> resolutions."

This emergence is what makes essays valuable beyond catalog lookups.
Do NOT force convergences that aren't there.

### 6 — Self-check (continuous, not endpoint)

Throughout, monito