# CLAUDE.md — Working Context

Read this first when resuming. This is a **family religious book** project.

## What this is

An authoritative family text: a modern teaching tool for the family's personal theology (Gnostic/Sethian + New Testament tie-ins, built from the author's lived demonic experience and research), plus a tactical spiritual-battle manual. For the author's wife and daughter now (reference), and future generations later (teaching).

Full blueprint: **`docs/2026-05-31-family-codex-design.md`** — read it before working.

## The most important rule

**Never invent doctrine, entities, rituals, or events.** The author is the sole authority on belief and experience. If material is missing, ask or write `[NEEDS YOUR INPUT]`. Claude's job: organize, shape, phrase, structure, cross-link — never originate substance.

## Structure

- 6 Parts, each a self-contained cross-linked module ("Codex with a Path"):
  - I Doctrine · II Family Canon · III Testimony · IV Practice & Devotion · V Battle Manual · VI Reference
- Front matter holds the **Reading Path** (teaching sequence).
- Mixed voice by Part — see `docs/STYLE-GUIDE.md`.

## Files

- `docs/2026-05-31-family-codex-design.md` — master design
- `docs/OUTLINE.md` — chapter list + Reading Path (living)
- `docs/STYLE-GUIDE.md` — voices, capitalization, ritual/testimony formats, citations
- `docs/GLOSSARY-MASTER.md` — every term + its canonical home
- `input/` — author's raw material
- `book/partN-*/` — finished chapters (`chNN-short-title.md`)

## Drafting loop

1. Author supplies raw material (in `input/` or spoken).
2. Claude drafts chapter in correct Part folder + voice.
3. Author reviews/corrects.
4. Claude revises, locks chapter, updates glossary + cross-links, commits.

## Tone in this project

Treat the subject with full respect. This is sacred to the family. Be precise, careful, and reverent. Caveman/brief mode may be active for chat, but **book prose is always written in full, polished form** per the style guide.

## Where we are

See the Status section at the bottom of the design doc and the `[NEEDS YOUR INPUT]` markers across `docs/`.