scriveno 2.0.5

package/templates/pitfalls/screenplay.md

@@ -0,0 +1,54 @@
+# Pitfall pack: screenplay
+
+*Type-specific traps for screenplay drafting. Loaded after WRITING-RULES.md. STYLE-GUIDE.md wins where it conflicts.*
+
+## Unfilmable description
+
+Screenplays show pictures and sound. Cut anything the camera and microphone cannot capture.
+
+- Interior thought in action lines ("She remembers her father", "He feels guilty"). Cut. Show the memory through behavior or render it as a flashback scene.
+- Backstory in description ("Marcus, who has spent twenty years as a detective..."). Cut. The reader will not see his career history on screen.
+- Adjectival character history ("the bitter, divorced accountant"). Show the bitterness in one beat.
+- Novel-prose description that paints atmosphere through metaphor. Use concrete physical details only.
+
+## Action line bloat
+
+- Paragraphs longer than three lines. Break.
+- Run-on sentences. Action lines should hit like beats: short, declarative, present tense.
+- Adverbs in action lines ("she walks slowly across the room"). Cut, or pick a stronger verb.
+- "We see" and "we hear" repeated. Use sparingly; they remind the reader they are reading a script, which is sometimes the point and usually not.
+
+## Dialogue pitfalls
+
+- On-the-nose dialogue (characters saying exactly what they mean and feel). Subtext is the form.
+- Parentheticals as direction ("(angrily)", "(sadly)"). The actor decides. Use parentheticals only when intent is genuinely ambiguous.
+- Speeches over a half-page. Break with action or interruption.
+- Every character sounding the same. Read each character's lines back-to-back; if you can swap names without confusion, the voices are not differentiated.
+- Phone-call coverage as info dump. Find a more visual way.
+
+## Format tics
+
+- Slug lines that are too long ("INT. THE OLD ABANDONED FACTORY ON THE EDGE OF TOWN - LATE AFTERNOON, SUMMER"). Tighten.
+- Day/night sloppiness. Match LATER, CONTINUOUS, MOMENTS LATER to actual time logic.
+- Inconsistent character intro caps. The first time a speaking character appears, name in CAPS. Once.
+- Camera direction (CLOSE ON, DOLLY IN, PUSH IN) when the script is not for a director-writer. Keep restrained.
+
+## Stock screenplay tells
+
+- "She closes her eyes." (used as transition or emotional beat overuse)
+- "A beat." (overused; use it when the beat carries meaning, not as filler)
+- "He looks at her. She looks back." (placeholder for a real exchange)
+- "Tears stream down her face."
+- "He clenches his jaw."
+
+## Pacing pitfalls
+
+- Scenes longer than three pages without a turn. Cut into the moment of change.
+- Establishing shots that establish nothing. The first image of a scene must mean something.
+- Montages as a substitute for dramatized progression. Earn them.
+
+## Closing pitfalls
+
+- THE END title cards on a script that is not pretending to be silent-era.
+- Smash cuts to black on every act break. Vary.
+- A final monologue that explains the theme.

package/templates/platforms/README.md

@@ -0,0 +1,16 @@
+# Publishing Platform Profiles
+
+This directory is the drop-in extension point for per-platform publishing configs. Each subdirectory ships as a self-contained profile; Scriveno's runtime reads the directory listing at load time -- no core-template edits are required to add a platform.
+
+## Adding a new platform
+
+1. Create `templates/platforms/<your-platform-slug>/`.
+2. Inside, add a `manifest.yaml` declaring: `platform`, `label`, `trim_sizes`, `max_pages`, `epub_variant`, `metadata_shape`, `formats_accepted`, `status`. See any of the shipped manifests for the shape.
+3. Set `status: active` once the manifest is populated. Profiles with `status: placeholder` are recognized by the validator but signal "schema present, content pending."
+4. Optional: add sibling files alongside `manifest.yaml` (per-platform CSS, metadata YAML, Typst snippets) as Phase 32 defines conventions.
+
+## Currently shipped platforms
+
+kdp, ingram, d2d, apple, kobo, google, bn, smashwords.
+
+All 8 ship with `status: active` and populated manifest data (trim sizes where applicable, page limits, metadata shapes, accepted formats, and EPUB variants).

package/templates/platforms/apple/manifest.yaml

@@ -0,0 +1,20 @@
+# Publishing platform profile -- Apple Books.
+# Populated in Phase 32 (Build Pipelines & Platform Awareness).
+# DO NOT remove this file -- Phase 29's validator reads the directory listing
+# to populate the allowed platform values.
+platform: apple
+label: "Apple Books"
+status: active
+formats_accepted:
+  - epub
+trim_sizes: null
+default_trim: null
+max_pages: null
+epub_variant: "epub3"
+epub_notes: "Apple Books requires epub:type semantic markup and valid cover image. Use Pandoc --toc for semantic nav."
+metadata_shape:
+  title: required
+  author: required
+  language: required
+  description: optional
+  isbn: optional

package/templates/platforms/bn/manifest.yaml

@@ -0,0 +1,20 @@
+# Publishing platform profile -- B&N Press.
+# Populated in Phase 32 (Build Pipelines & Platform Awareness).
+# DO NOT remove this file -- Phase 29's validator reads the directory listing
+# to populate the allowed platform values.
+platform: bn
+label: "B&N Press"
+status: active
+formats_accepted:
+  - epub
+trim_sizes: null
+default_trim: null
+max_pages: null
+epub_variant: "epub3"
+epub_notes: "B&N Press accepts EPUB3. Ensure valid cover image and NCX nav for compatibility."
+metadata_shape:
+  title: required
+  author: required
+  language: required
+  description: optional
+  isbn: optional

package/templates/platforms/d2d/manifest.yaml

@@ -0,0 +1,20 @@
+# Publishing platform profile -- Draft2Digital.
+# Populated in Phase 32 (Build Pipelines & Platform Awareness).
+# DO NOT remove this file -- Phase 29's validator reads the directory listing
+# to populate the allowed platform values.
+platform: d2d
+label: "Draft2Digital"
+status: active
+formats_accepted:
+  - epub
+trim_sizes: null
+default_trim: null
+max_pages: null
+epub_variant: "epub3"
+epub_notes: "D2D runs its own EPUB validator on upload. Pandoc-generated EPUB3 passes without manual post-processing."
+metadata_shape:
+  title: required
+  author: required
+  language: required
+  description: optional
+  isbn: optional

package/templates/platforms/google/manifest.yaml

@@ -0,0 +1,20 @@
+# Publishing platform profile -- Google Play Books.
+# Populated in Phase 32 (Build Pipelines & Platform Awareness).
+# DO NOT remove this file -- Phase 29's validator reads the directory listing
+# to populate the allowed platform values.
+platform: google
+label: "Google Play Books"
+status: active
+formats_accepted:
+  - epub
+trim_sizes: null
+default_trim: null
+max_pages: null
+epub_variant: "epub3"
+epub_notes: "Google Play Books accepts EPUB3. Description and ISBN strongly recommended for discoverability."
+metadata_shape:
+  title: required
+  author: required
+  language: required
+  description: recommended
+  isbn: recommended

package/templates/platforms/ingram/manifest.yaml

@@ -0,0 +1,44 @@
+# Publishing platform profile -- IngramSpark.
+# Populated in Phase 32 (Build Pipelines & Platform Awareness).
+# DO NOT remove this file -- Phase 29's validator reads the directory listing
+# to populate the allowed platform values.
+platform: ingram
+label: "IngramSpark"
+status: active
+formats_accepted:
+  - epub
+  - pdf_print_ready
+pdf_requirements:
+  standard: "PDF/X-1a"
+  note: "Use Ghostscript (gs) for PDF/X-1a conversion after building with Pandoc + Typst"
+trim_sizes:
+  5x8:
+    width_in: 5
+    height_in: 8
+    wpp: 220
+  5.25x8:
+    width_in: 5.25
+    height_in: 8
+    wpp: 230
+  5.5x8.5:
+    width_in: 5.5
+    height_in: 8.5
+    wpp: 235
+  6x9:
+    width_in: 6
+    height_in: 9
+    wpp: 250
+  7x10:
+    width_in: 7
+    height_in: 10
+    wpp: 300
+default_trim: "6x9"
+max_pages:
+  paperback: 1200
+epub_variant: "epub3"
+metadata_shape:
+  title: required
+  author: required
+  language: required
+  description: optional
+  isbn: optional

package/templates/platforms/kdp/manifest.yaml

@@ -0,0 +1,42 @@
+# Publishing platform profile -- Amazon KDP.
+# Populated in Phase 32 (Build Pipelines & Platform Awareness).
+# DO NOT remove this file -- Phase 29's validator reads the directory listing
+# to populate the allowed platform values.
+platform: kdp
+label: "Amazon KDP"
+status: active
+formats_accepted:
+  - epub
+  - pdf_print_ready
+trim_sizes:
+  5x8:
+    width_in: 5
+    height_in: 8
+    wpp: 220
+  5.25x8:
+    width_in: 5.25
+    height_in: 8
+    wpp: 230
+  5.5x8.5:
+    width_in: 5.5
+    height_in: 8.5
+    wpp: 235
+  6x9:
+    width_in: 6
+    height_in: 9
+    wpp: 250
+  7x10:
+    width_in: 7
+    height_in: 10
+    wpp: 300
+default_trim: "6x9"
+max_pages:
+  paperback: 828
+  hardcover: 550
+epub_variant: "epub3"
+metadata_shape:
+  title: required
+  author: required
+  language: required
+  description: optional
+  isbn: optional

package/templates/platforms/kobo/manifest.yaml

@@ -0,0 +1,20 @@
+# Publishing platform profile -- Kobo Writing Life.
+# Populated in Phase 32 (Build Pipelines & Platform Awareness).
+# DO NOT remove this file -- Phase 29's validator reads the directory listing
+# to populate the allowed platform values.
+platform: kobo
+label: "Kobo Writing Life"
+status: active
+formats_accepted:
+  - epub
+trim_sizes: null
+default_trim: null
+max_pages: null
+epub_variant: "epub3"
+epub_notes: "Kobo Writing Life accepts EPUB3. Ensure metadata includes language and description for store listing."
+metadata_shape:
+  title: required
+  author: required
+  language: required
+  description: recommended
+  isbn: optional

package/templates/platforms/smashwords/manifest.yaml

@@ -0,0 +1,26 @@
+# Publishing platform profile -- Smashwords (via Draft2Digital merger).
+# Populated in Phase 32 (Build Pipelines & Platform Awareness).
+# DO NOT remove this file -- Phase 29's validator reads the directory listing
+# to populate the allowed platform values.
+platform: smashwords
+label: "Smashwords"
+status: active
+formats_accepted:
+  - epub
+trim_sizes: null
+default_trim: null
+max_pages: null
+epub_variant: "epub3"
+epub_notes: >
+  Smashwords requires Nuclear Option compliance: no tabs, no manual indents, paragraph
+  styles only. The Pandoc EPUB output is Nuclear Option compliant when generated from
+  clean Markdown (no HTML passthrough with tab characters or manual indent styles).
+  Review the Smashwords Style Guide before final submission.
+metadata_shape:
+  title: required
+  author: required
+  language: required
+  description: required
+  isbn: optional
+  category: required
+  keywords: recommended

package/templates/sacred/COSMOLOGY.md

@@ -0,0 +1,88 @@
+# Setting & cosmology
+
+*The world of the sacred/historical text. Includes geography, cosmological framework, sacred spaces, and the rules governing how the natural and supernatural interact.*
+
+## Physical geography
+
+### Sacred places
+{{SACRED_PLACES}}
+
+### Regions
+{{REGIONS}}
+
+### Cities and towns
+{{CITIES}}
+
+### Natural features
+{{NATURAL_FEATURES}}
+*(Mountains, rivers, wildernesses, bodies of water with symbolic or historical weight.)*
+
+## Cosmological framework
+
+### Cosmic structure
+{{COSMIC_STRUCTURE}}
+*(Heavens, earth, underworld, spiritual realms. How many levels, how they connect, who inhabits each.)*
+
+### Divine realm
+{{DIVINE_REALM}}
+*(Nature of the divine, court structure, hierarchy.)*
+
+### Intermediate beings
+{{INTERMEDIATE_BEINGS}}
+*(Angels, demons, spirits, bodhisattvas, devas -- whatever the tradition recognizes.)*
+
+### Afterlife
+{{AFTERLIFE}}
+
+### Time and eras
+{{TIME_ERAS}}
+*(How the text conceives of time -- cyclical, linear, apocalyptic, ages/yugas/dispensations.)*
+
+## Natural/supernatural interface
+
+### How the supernatural enters the natural world
+{{SUPERNATURAL_ENTRY}}
+*(Theophany, prophecy, miracle, vision, dream, possession, incarnation.)*
+
+### Rules governing miracles
+{{MIRACLE_RULES}}
+*(What kinds of miracles happen, by whom, under what conditions, with what permanence.)*
+
+### Sacred vs. profane
+{{SACRED_PROFANE}}
+*(What makes a space, object, time, or person sacred. Rules for maintaining sanctity.)*
+
+## Cultural and social setting
+
+### Social structure
+{{SOCIAL_STRUCTURE}}
+
+### Economy
+{{ECONOMY}}
+
+### Religious practice
+{{RELIGIOUS_PRACTICE}}
+*(Rituals, pilgrimages, festivals, sacrifices, daily devotion.)*
+
+### Legal framework
+{{LEGAL_FRAMEWORK}}
+*(Laws, courts, justice, punishment.)*
+
+## Historical context
+
+### Dating
+{{DATING}}
+*(Use the config's calendar_system -- AM, AH, BCE/CE, regnal years, etc.)*
+
+### Adjacent cultures and kingdoms
+{{ADJACENT}}
+
+### Trade and migration patterns
+{{TRADE}}
+
+### Historical events that frame the text
+{{FRAMING_EVENTS}}
+
+---
+
+*This file establishes the rules of the world. Drafter agents check it to avoid anachronisms, contradictions with established geography, and violations of cosmological structure.*

package/templates/sacred/DOCTRINES.md

@@ -0,0 +1,45 @@
+# Doctrinal threads
+
+*The sacred/historical equivalent of THEMES.md. Theological themes, moral teachings, prophetic patterns, and doctrinal claims the text makes or embodies.*
+
+---
+
+## {{DOCTRINE_NAME}}
+
+**Position:** {{POSITION}} (affirmed, disputed, developed, implicit)
+**Tradition alignment:** {{TRADITION_ALIGNMENT}}
+**Scope:** {{SCOPE}} (central, peripheral, contested)
+
+### The claim
+{{CLAIM}}
+
+### How the text establishes it
+{{METHOD}}
+*(Narrative example, direct teaching, parable, legal code, prophetic declaration, lived practice of a figure, contrast with an opposing view.)*
+
+### Where it surfaces
+{{APPEARANCES}}
+*(Specific units/passages where this doctrine is presented, challenged, refined, or reinforced.)*
+
+### Related doctrines
+{{RELATED}}
+
+### Counter-positions in the text
+{{COUNTER_POSITIONS}}
+*(Views the text argues against, or that characters/figures in the text hold before being corrected.)*
+
+### Pastoral application
+{{APPLICATION}}
+*(If this is a devotional, commentary, or sermon -- how this doctrine is meant to shape the reader's life or practice.)*
+
+### Historical-critical notes
+{{HISTORICAL_NOTES}}
+*(For scholarly work -- development of this doctrine, disputed interpretations, relationship to adjacent traditions.)*
+
+### Scholarly disputes
+{{DISPUTES}}
+*(Which commentators/schools disagree about this doctrine and how.)*
+
+---
+
+*Drafter agents check this file to avoid contradicting established doctrines when drafting passages. `/scr:doctrinal-check` flags any unit that contradicts or undermines an affirmed doctrine without explicit intent.*

package/templates/sacred/FIGURES.md

@@ -0,0 +1,69 @@
+# Figures
+
+*One entry per figure. Figures include prophets, saints, deities, angels, patriarchs, historical persons, and any named individual in the text. Each figure gets a voice register anchor that drafter agents use for consistency.*
+
+---
+
+## {{FIGURE_NAME}}
+
+**Type:** {{TYPE}} (prophet, patriarch, deity, angel, historical person, disciple, etc.)
+**Tradition:** {{TRADITION}}
+**Historical period:** {{PERIOD}}
+**First appearance:** {{FIRST_APPEARANCE}} (book/chapter/verse)
+
+### Significance
+- **Role in the text:** {{ROLE}}
+- **Theological significance:** {{SIGNIFICANCE}}
+- **Lineage/tribal affiliation:** {{LINEAGE}}
+
+### Canonical attributes
+- **Titles:** {{TITLES}}
+- **Epithets:** {{EPITHETS}}
+- **Symbols/iconography:** {{SYMBOLS}}
+
+### Voice register anchor
+*Sample speech showing how this figure speaks. Drafter agents load this when drafting passages with this figure's speech.*
+
+{{VOICE_SAMPLE}}
+
+### Speech register
+- **Primary register:** {{REGISTER}} (prophetic, wisdom, legal, liturgical, didactic, etc.)
+- **Characteristic phrases:** {{PHRASES}}
+- **Address style:** {{ADDRESS}} (direct, mediated, third-person)
+- **Authority source:** {{AUTHORITY}} (divine commission, inherited, scholarly)
+
+### Persona under pressure
+- **When afraid:** {{AFRAID_BEHAVIOR}}
+- **When angry:** {{ANGER_BEHAVIOR}}
+- **When withholding truth:** {{LYING_BEHAVIOR}}
+- **When vulnerable:** {{VULNERABLE_BEHAVIOR}}
+- **Physical tells:** {{PHYSICAL_TELLS}}
+
+### Arc across the text
+- **Introduction:** {{INTRODUCTION}}
+- **Key moments:** {{KEY_MOMENTS}}
+- **Departure/death/translation:** {{DEPARTURE}}
+- **Post-mortem references:** {{POST_MORTEM}}
+
+### Relationships
+{{RELATIONSHIPS_SUMMARY}}
+*(Cross-reference LINEAGES.md for genealogical and covenantal connections.)*
+
+### Relationship-specific interactions
+For each important relationship, note how this figure changes with that person.
+
+- **With {{OTHER_FIGURE}}:** {{INTERACTION_DYNAMIC}}
+  - **Trust posture:** {{TRUST_POSTURE}}
+  - **Conflict pattern:** {{CONFLICT_PATTERN}}
+  - **Speech shift:** {{SPEECH_SHIFT}}
+  - **Hidden agenda, fear, or theological tension:** {{HIDDEN_AGENDA}}
+
+### Source traditions
+{{SOURCES}}
+*(Which primary sources, oral traditions, or manuscript variants describe this figure. Relevant for historical accounts and critical editions.)*
+
+### Doctrinal position
+{{DOCTRINAL_POSITION}}
+*(Where this figure sits within DOCTRINES.md -- what they embody, reject, model, or warn against.)*
+
+---

package/templates/sacred/FRAMEWORK.md

@@ -0,0 +1,98 @@
+# Theological framework / historical scope
+
+*The sacred/historical equivalent of BRIEF.md. Establishes the project's theological or historical posture, its intended audience, its relationship to tradition, and the boundaries of what it will and won't do.*
+
+## Vision
+
+{{VISION}}
+
+## Purpose of this work
+
+{{PURPOSE}}
+*(Devotional edification, scholarly exegesis, pastoral teaching, critical edition, translation, new commentary, liturgical resource, historical reconstruction.)*
+
+## Intended audience
+
+{{AUDIENCE}}
+*(Scholarly, lay faithful, seekers, interfaith, academic, students, specific community.)*
+
+## Tradition and stance
+
+### Primary tradition
+{{TRADITION}}
+
+### Denominational/school alignment
+{{ALIGNMENT}}
+
+### Posture toward tradition
+{{POSTURE}}
+*(Confessional -- working from within the tradition as a believer; descriptive -- presenting the tradition without endorsement; comparative -- placing this tradition alongside others; critical -- examining the tradition with scholarly distance.)*
+
+### Relationship to canonical sources
+{{CANONICAL_RELATIONSHIP}}
+*(Commentary on existing canon, original scripture, historical account of a tradition, new devotional material using canonical references.)*
+
+## Theological framework
+
+### Core doctrines to affirm
+{{CORE_DOCTRINES}}
+
+### Doctrines that are contested or open
+{{OPEN_DOCTRINES}}
+
+### Doctrines to engage critically
+{{CRITICAL_DOCTRINES}}
+
+### Doctrines explicitly outside scope
+{{OUT_OF_SCOPE}}
+
+## Interpretive framework
+
+### Hermeneutical approach
+{{HERMENEUTICS}}
+*(Literal, allegorical, typological, historical-critical, reader-response, canonical, narrative, devotional.)*
+
+### Methodology
+{{METHODOLOGY}}
+*(How the writer will work with sources, handle disputed passages, present multiple interpretations.)*
+
+### Language posture
+{{LANGUAGE_POSTURE}}
+*(Formal equivalence, dynamic equivalence, paraphrase, original language preservation, transliteration preferences.)*
+
+## Historical scope
+
+### Time period covered
+{{PERIOD}}
+
+### Geographic scope
+{{GEOGRAPHY}}
+
+### Sources used
+{{SOURCES}}
+*(Canonical texts, non-canonical texts, oral traditions, archaeological evidence, secondary scholarship.)*
+
+### Source hierarchy
+{{SOURCE_HIERARCHY}}
+*(When sources conflict, which takes priority.)*
+
+## Boundaries
+
+### What this work will do
+{{WILL_DO}}
+
+### What this work will NOT do
+{{WILL_NOT_DO}}
+
+### Sensitivity considerations
+{{SENSITIVITY}}
+*(How disputes, heresies, interfaith topics, and traditionally sensitive subjects will be handled.)*
+
+## Success criteria
+
+{{SUCCESS}}
+*(What does a successful version of this work look like? Both craft-wise and in terms of impact on the intended audience.)*
+
+---
+
+*This file replaces BRIEF.md for sacred and historical work types. It establishes the posture from which every drafted unit proceeds.*

package/templates/sacred/LINEAGES.md

@@ -0,0 +1,52 @@
+# Lineages & connections
+
+*Genealogical trees, covenantal relationships, teacher-student chains, tribal affiliations, and dynastic succession. The sacred/historical equivalent of RELATIONSHIPS.md.*
+
+## Genealogies
+
+### {{LINEAGE_NAME}}
+**Type:** {{TYPE}} (patriarchal, maternal, tribal, spiritual succession, teacher-student)
+**Tradition:** {{TRADITION}}
+
+```
+{{GENEALOGY_TREE}}
+```
+
+**Notes:** {{NOTES}}
+
+---
+
+## Covenants
+
+### {{COVENANT_NAME}}
+**Parties:** {{PARTIES}}
+**When:** {{WHEN}}
+**Terms:** {{TERMS}}
+**Sign:** {{SIGN}}
+**Status:** {{STATUS}} (active, fulfilled, broken, renewed)
+**References in text:** {{REFERENCES}}
+
+---
+
+## Teacher-student chains
+
+### {{CHAIN_NAME}}
+**Tradition:** {{TRADITION}}
+**Founder:** {{FOUNDER}}
+**Transmission type:** {{TRANSMISSION}} (oral, written, initiatory)
+
+```
+{{CHAIN_SEQUENCE}}
+```
+
+**Notes:** {{NOTES}}
+
+---
+
+## Tribal and dynastic affiliations
+
+{{AFFILIATIONS}}
+
+---
+
+*When drafting any unit involving figures, the drafter agent checks this file to verify lineage claims, covenant references, and relationships. Contradictions are flagged by `/scr:doctrinal-check`.*

package/templates/sacred/README.md

@@ -0,0 +1,20 @@
+# Sacred Tradition Profiles
+
+This directory is the drop-in extension point for sacred tradition profiles. Each subdirectory ships as a self-contained profile; Scriveno's runtime reads the directory listing at load time -- no core-template edits are required to add a tradition.
+
+## Adding a new tradition
+
+1. Create `templates/sacred/<your-tradition-slug>/`.
+2. Inside, add a `manifest.yaml` declaring: `tradition`, `label`, `book_order`, `approval_block`, `font_stack`, `rtl`, `numbering`, `script`, `status`. See any of the shipped manifests for the shape.
+3. Set `status: active` once the manifest is populated. Profiles with `status: placeholder` are recognized by the validator but signal "schema present, content pending."
+4. Optional: add sibling files alongside `manifest.yaml` (CSS, Typst snippets, font-stack fragments) as downstream phases define conventions.
+
+## Currently shipped traditions
+
+catholic, orthodox, tewahedo, protestant, jewish, islamic-hafs, islamic-warsh, pali, tibetan, sanskrit.
+
+All 10 ship with `status: active` and populated manifest data (book order where fixed, approval blocks, font stacks, RTL flags, numbering macros, and script metadata).
+
+## Co-located legacy files
+
+The files `COSMOLOGY.md`, `DOCTRINES.md`, `FIGURES.md`, `FRAMEWORK.md`, `LINEAGES.md`, `THEOLOGICAL-ARC.md` in this directory are project-scaffold templates copied into new sacred-work-type projects (see `/scr:new-work`). They are unrelated to tradition profiles and are preserved as-is.