bible/docs/2026-05-31-family-codex-design.md

The Family Codex — Design Document

Created 2026-05-31. This is the master blueprint for the book. Read this first when resuming work.

---

1. Purpose

A family religious text. Two jobs:

1. Reference now — for the author's wife and daughter, who already share the faith. Look things up: a ritual, an entity, a point of doctrine.
2. Teaching tool later — to pass the faith to the daughter's children and future generations, taught in sequence from the ground up.

Authoritative for the family. Not a Bible — a modern learning tool for the family religion, plus a tactical guide to spiritual battle. Possibly published (Amazon KDP) later, but family use is primary.

2. The Faith (scope)

Personal theology built from lived experience and research:

• Gnostic / Sethian teachings at the core (cosmology, the divine).
• New Testament tie-ins woven through.
• Lived demonic experience as testimony and evidence.
• A tactical spiritual-battle discipline — plans, protection, rituals, discernment.

3. Audience

Family. Wife and daughter already know the faith (reference altitude). Future generations do not (teaching altitude). The book must serve both — hence reference-first modules plus a defined teaching sequence (the Reading Path).

4. Architecture — "Codex with a Path"

Each Part is a self-contained, cross-linked module. Reference-first: jump straight to any entity, ritual, or doctrine. A Reading Path in the front matter defines the order to teach a newcomer.

Modular by design so it can split into two volumes later (Book of Belief + Book of War) with no rework.

The Six Parts

Part	Title	Voice
I	Doctrine — cosmology, the divine, Sethian/Gnostic core, NT tie-ins	Elevated / scriptural
II	Family Canon — origin of our faith, lineage, why this book exists	Warm + reverent
III	Testimony — the author's demonic encounters, as record + lesson	Plain, first-person
IV	Practice & Devotion — daily/weekly rites, prayers, calendar	Warm teaching
V	Demonology — the enemy and the mechanics of authority (naming, binding, the "stronger man"); theory of spiritual combat	Plain / evidence-based
VI	The Spiritual Battle Manual — discernment, protection, battle plans, rituals, step-by-step	Field manual
VII	Reference — glossary, entities/names, quick-lookup tables	Terse reference

Demonology (Part V) was added during drafting, placed before the Battle Manual so the theory of the enemy precedes the tactics. The two form the "warfare" block at the book's end.

Default ordering logic: foundation (Doctrine) → who we are (Canon) → why it's real (Testimony) → how we live it (Practice) → how we fight (Battle) → lookup (Reference).

Reading Path (teaching a child) may reorder, e.g. Canon → Doctrine → Practice → Battle → Testimony → Reference. Finalized in OUTLINE.md.

Front Matter

• Dedication / letter to the reader (author → daughter → descendants).
• The Reading Path (numbered teaching order).
• How to use this book (reference vs. cover-to-cover).

Cross-Linking

Every entity / term / ritual has a canonical home in one Part. Other Parts link to it via markdown links. The Battle Manual cites Doctrine; the Glossary points back to full treatments. GLOSSARY-MASTER.md tracks every term and its canonical location.

5. Voice

Mixed by section (see table above and STYLE-GUIDE.md). Four registers: scriptural, warm-teaching, plain-testimony, field-manual.

6. Production System

Folder layout

input/      raw dumps — notes, memory transcripts, research links (messy OK, one file per topic)
docs/       this design doc, STYLE-GUIDE.md, OUTLINE.md, GLOSSARY-MASTER.md
book/       finished chapters, numbered markdown
  part1-doctrine/  part2-canon/  part3-testimony/  part4-practice/
  part5-demonology/  part6-battle/  part7-reference/
CLAUDE.md   working context for resuming sessions
README.md   project overview

Drafting loop (per chapter)

1. Author drops raw material in input/ (or speaks it; Claude captures).
2. Claude drafts the chapter in its Part folder, in that section's voice.
3. Author reviews — corrects theology, facts, tone. The author is the authority.
4. Claude revises, locks the chapter, updates GLOSSARY-MASTER.md + cross-links.
5. Repeat.

Hard rule — no invention

Claude never invents doctrine, entities, rituals, or events. Missing material → ask, or mark [NEEDS YOUR INPUT]. The author's lived experience and beliefs are the only source of truth. Claude shapes, organizes, phrases, and structures; the author supplies all substance.

Version control

Git tracks every change. Nothing is lost. Commit per locked chapter (or more often).

7. Status / Next Steps

• Design approved
• Repo + folder structure created
• STYLE-GUIDE.md drafted
• OUTLINE.md drafted (full chapter list + Reading Path)
• First Part begun

Recommended first draft target: Part II — Family Canon (origin + dedication) or Part I — Doctrine. Decide at next session.