ADR-0007: Sermon, Question, Person, Glossary schemas

Status: Accepted Date: 2026-05-19

Context

Four remaining note types beyond Atomic and Thread. Each needs a minimal schema that supports its specific role.

Decision

Sermon

  • sermon-kind: pastoral | worship-redirect (more kinds added later as needed)
  • Required fields: occasion, duration-target, threads (which threads it draws from)
  • Body sections: ## Hook, ## Beats, ## Call / Prayer
  • No word cap — storytelling needs the room it needs
  • Lives in /sermons/pastoral/ or /sermons/worship-redirect/
  • Sermons link INTO threads for readers who want to dig deeper

Question

  • Status enum: open | answered (the one place a status enum exists — questions ARE inherently open or closed)
  • answered-by: links to the resolving thread when applicable
  • AI auto-marks answered when a thread cites the question and resolves it

Person

  • Thin index — real content lives in atomics/threads that cite the person, not in the person note
  • Fields: aliases, role, key-works
  • Body: one-paragraph summary + auto-generated ## Referenced by section (see ADR-0013)

Glossary

  • Defined vocabulary, important for UC’s dense terminology (Sungsang, Hyungsang, indemnity, Universal Prime Force, etc.)
  • Fields: aliases, korean (original term where applicable), related
  • Body: ## Definition (one sentence), ## Expanded (1–2 paragraphs citing canonical sources), auto-generated ## Referenced by

Alternatives considered

  • Skip Person notes: rejected — UC has named central figures that AI needs an addressable index for (“what did Father say about X?”). Worth the maintenance cost.
  • Skip Question notes: rejected — user said “I might need help coming up with good questions, because most of the time I don’t know what I don’t know” — Questions are the explicit handle for AI to surface gaps.
  • Sermon as flat folder (no sermon-kind sub-folders): considered — folders cost nothing and help scan-by-kind (“avoid repeating last year’s worship redirects”). Sub-folders kept.

Consequences

  • (+) Each type does one job; no overloaded schemas
  • (+) Person/Glossary become first-class navigation aids on the published site
  • (−) Two more schemas to maintain, mitigated by their auto-generated ## Referenced by sections (ADR-0013)