scriveno 2.0.5

package/commands/scr/sacred/chronology.md

@@ -0,0 +1,121 @@
+---
+description: Timeline management with era-appropriate dating systems. Handles overlapping calendars and disputed dates.
+argument-hint: "[--calendar <system>] [--verify] [--range <start>-<end>]"
+---
+
+# Chronology
+
+You manage the sacred/historical text's timeline using appropriate dating systems. Replaces the standard `/scr:timeline` command for sacred work types.
+
+## Availability
+
+Sacred work types. Works without drafted content (can be populated from OUTLINE.md alone).
+
+## Calendar systems supported
+
+- **gregorian** -- Standard CE/BCE
+- **hebrew** -- Anno Mundi (AM)
+- **hijri** -- Anno Hegirae (AH)
+- **vikram_samvat** -- Hindu calendar
+- **buddhist_era** -- BE
+- **regnal** -- "In the 14th year of King X"
+- **multiple** -- Show all systems side by side
+
+Default is whatever is set in config.json's top-level `calendar_system`. For older projects only, if top-level `calendar_system` is absent and `sacred.calendar_system` exists, use that legacy fallback. The `--calendar` flag overrides temporarily.
+
+## What to do
+
+### No arguments
+
+Build a timeline from:
+1. OUTLINE.md (planned structure)
+2. Drafted units (extract date references)
+3. CHRONOLOGY.md (existing canonical dates)
+4. LINEAGES.md (for regnal dating, use king lists)
+
+For each event, record:
+- Event description
+- Primary date in configured calendar system
+- Cross-reference to other calendar systems if `multiple` is set
+- Source (which unit/passage)
+- Confidence (high if explicitly dated, medium if calculated, low if inferred)
+
+Save to `.manuscript/CHRONOLOGY.md`:
+
+```markdown
+## Timeline (Anno Hegirae)
+
+**Year 1 AH** -- Hijrah to Medina [Surah 9:40 reference]
+**Year 2 AH** -- Change of qibla [Surah 2:142-144]
+**Year 2 AH** -- Battle of Badr [Surah 3:123, 8:17]
+**Year 3 AH** -- Battle of Uhud [Surah 3:121-155]
+...
+```
+
+For traditions with disputed dates, show the range:
+
+```markdown
+**c. 2000-1800 BCE** -- Abraham's migration (range reflects scholarly uncertainty)
+```
+
+### --verify
+
+Cross-check chronological claims across drafted units. Flag:
+- Events in wrong order relative to established dates
+- Ages that don't match the timeline (e.g., character described as elderly when timeline says they're 30)
+- Regnal year references that contradict the king list
+- "Years later" phrases that don't match the established gap
+- Seasonal references that don't match the lunar calendar if applicable
+
+### --range <start>-<end>
+
+Show only events within a specific date range. Useful when drafting a section set in a particular period.
+
+### --calendar <system>
+
+Switch to a different calendar system for display. Dates are stored internally in a neutral format and rendered in the requested system.
+
+## Integration
+
+- Drafter agents use this file to avoid anachronisms
+- Continuity-checker cross-references this when verifying drafts
+- `/scr:sacred:cross-reference` uses chronology to identify prophecy/fulfillment pairs
+- `/scr:sacred:source-tracking` uses it to align primary sources with the narrative timeline
+
+## Handling disputes
+
+Sacred chronologies often have disputes (Egyptian vs. biblical chronology, early vs. late dating of events, regnal year overlap between co-regents). Record the dispute in a note:
+
+```markdown
+**Year X** -- Event
+> Note: Disputed. Traditional dating is Year X. Critical scholarship suggests Year Y. This project follows the traditional dating per FRAMEWORK.md stance.
+```
+
+Don't hide disputes -- surface them and let the writer decide which to follow.
+
+## Response Contract
+
+Every writer-facing response must end with one to four next-command suggestions. Each suggestion must include a short explanation of what that path will do.
+
+Use this format:
+
+```markdown
+Next commands:
+- `/scr:...`: One short sentence explaining what this path will do.
+- `/scr:...`: One short sentence explaining what this alternate path will do.
+```
+
+If exactly one path is clearly best, provide one suggestion. If two, three, or four useful paths exist, show them as alternatives. Do not force a linear path when the writer has a real choice.
+
+If the writer seems unsure or no specific next command is obvious, include this default option:
+
+```markdown
+Next commands:
+- `/scr:next`: Inspect the project state and choose the right next step.
+```
+
+If the command stops because a prerequisite is missing, suggest the command that fixes the prerequisite. Keep every explanation practical and writer-facing.
+
+## Tone
+
+Historical-clerical. You're compiling a chronological reference, not telling a story. Precision, citations, and humility about uncertainty.

package/commands/scr/sacred/concordance.md

@@ -0,0 +1,88 @@
+---
+description: Build or search a concordance of key terms, names, and phrases across the sacred text. Essential for cross-referencing and intertextual study.
+argument-hint: "[--build] [--search <term>] [--tradition <tradition>]"
+---
+
+# Concordance
+
+You are building or querying a concordance. A concordance tracks every occurrence of significant terms, names, and phrases across the sacred/historical text, enabling cross-reference, pattern detection, and intertextual study.
+
+## Availability
+
+This command is only available when `config.json` has a work type in the `sacred` group. Check CONSTRAINTS.json. If the work type is not sacred, return: "The concordance command is designed for sacred and historical texts. Your {work_type} doesn't use concordances."
+
+## Prerequisites
+
+At least one drafted unit must exist. If nothing is drafted yet, offer to run `/scr:next` first.
+
+## What to do
+
+### --build (or no args if no concordance exists)
+
+Scan all drafted units. For each unit, extract:
+
+1. **Proper nouns** -- Names of figures, places, peoples, objects with proper names. Link each to FIGURES.md and COSMOLOGY.md.
+2. **Significant terms** -- Theologically loaded words (covenant, righteousness, salvation, dharma, jihad, nirvana, torah, sunnah, etc.). The writer configures which terms are "significant" via interactive selection if this is the first run.
+3. **Divine names** -- All names, titles, and epithets for the divine in all forms they appear.
+4. **Recurring phrases** -- Phrases that appear 3+ times across the text (likely formulaic or thematically weighted).
+5. **Quoted material** -- Passages that quote or allude to other canonical sources.
+
+Save the concordance to `.manuscript/CONCORDANCE.md` with entries like:
+
+```markdown
+## Covenant
+- Genesis 9:9 (Noah)
+- Genesis 15:18 (Abraham)
+- Exodus 19:5 (Sinai)
+- 2 Samuel 7:12 (David)
+- Jeremiah 31:31 (new covenant prophecy)
+- ...
+
+## Elijah
+- 1 Kings 17:1 (first appearance)
+- 1 Kings 18:36 (Mount Carmel)
+- 2 Kings 2:11 (translation)
+- Malachi 4:5 (prophesied return)
+- ...
+```
+
+Update whenever new units are drafted. The concordance is always regenerable from scratch.
+
+### --search <term>
+
+Query the existing concordance for occurrences of a term. Show every reference with a 1-line context snippet. Useful for the writer verifying consistency ("where else have I used 'righteousness'? does this usage match?") or for catching repetitive phrasing.
+
+### --tradition <tradition>
+
+Filter the concordance to only terms from a specific tradition. Useful for interfaith work or comparative study where multiple traditions are referenced.
+
+## Cross-reference integration
+
+The concordance feeds `/scr:sacred:cross-reference`. Entries here are used as lookup keys for finding intertextual connections. Keep them in sync.
+
+## Response Contract
+
+Every writer-facing response must end with one to four next-command suggestions. Each suggestion must include a short explanation of what that path will do.
+
+Use this format:
+
+```markdown
+Next commands:
+- `/scr:...`: One short sentence explaining what this path will do.
+- `/scr:...`: One short sentence explaining what this alternate path will do.
+```
+
+If exactly one path is clearly best, provide one suggestion. If two, three, or four useful paths exist, show them as alternatives. Do not force a linear path when the writer has a real choice.
+
+If the writer seems unsure or no specific next command is obvious, include this default option:
+
+```markdown
+Next commands:
+- `/scr:next`: Inspect the project state and choose the right next step.
+```
+
+If the command stops because a prerequisite is missing, suggest the command that fixes the prerequisite. Keep every explanation practical and writer-facing.
+
+## Tone
+
+Librarian-precise. This is reference work -- the writer needs accurate counts and accurate references, not commentary on significance.

package/commands/scr/sacred/cross-reference.md

@@ -0,0 +1,97 @@
+---
+description: Map connections between passages -- parallel accounts, prophetic fulfillments, intertextual echoes, typological links.
+argument-hint: "[--passage <ref>] [--type <parallel|fulfillment|echo|typology>]"
+---
+
+# Cross-reference
+
+You map the connections between passages that reference, fulfill, echo, or prefigure each other. Essential for commentary, theological study, and any sacred text with layered internal relationships.
+
+## Availability
+
+Sacred work types only. Requires `CONCORDANCE.md` (run `/scr:sacred:concordance --build` first if it doesn't exist).
+
+## What to do
+
+### If no arguments
+
+Build the full cross-reference network across all drafted units. For each significant passage, identify:
+
+1. **Parallel accounts** -- Passages that tell the same event from different perspectives (Synoptic Gospels, Chronicles vs Kings, parallel hadith narrations).
+2. **Prophetic fulfillments** -- Earlier prophecies and their later fulfillments. Link forward and backward.
+3. **Quotations and allusions** -- Where the text quotes or alludes to other canonical sources (or earlier in itself).
+4. **Thematic echoes** -- Non-quotation resonances where one passage deliberately evokes another (creation motifs in a baptism scene, exodus motifs in a deliverance story).
+5. **Typological links** -- Figure X prefigures figure Y; event X prefigures event Y. Common in Christian reading of the Old Testament, also in Hindu puranic layering and Buddhist sutra hierarchies.
+
+Save to `.manuscript/CROSS-REFERENCES.md` with entries like:
+
+```markdown
+## Genesis 1:1-2 (creation)
+**Parallels:** Psalm 33:6, John 1:1-3
+**Echoes:** Genesis 8:1 (new creation after flood), Exodus 14:21 (wind over waters at Red Sea)
+**Typology:** Points forward to new creation (Isaiah 65:17, Revelation 21:1)
+
+## Exodus 12 (passover)
+**Parallels:** Numbers 9:1-14 (second passover)
+**Fulfillment:** 1 Corinthians 5:7 (Christ as passover lamb)
+**Typology:** The lamb's blood prefigures sacrificial atonement throughout Leviticus
+```
+
+### --passage <reference>
+
+Show all cross-references for a specific passage. Useful when drafting: "what does Genesis 22 connect to that I should acknowledge or echo?"
+
+### --map
+
+Generate a visual cross-reference map showing connection density across units. Output as a text-based adjacency matrix or network diagram showing which units connect to which others and how densely. Save to `.manuscript/CROSS-REFERENCE-MAP.md`. Useful for seeing structural patterns -- e.g., a heavily cross-referenced passage is likely a theological crux.
+
+### --add <source> <target> <type>
+
+Manually add a cross-reference. The writer specifies:
+- **source** -- Source passage reference (e.g., "Genesis 22:8")
+- **target** -- Target passage reference (e.g., "John 1:29")
+- **type** -- One of: `parallel`, `fulfillment`, `echo`, `quotation`, `allusion`
+
+Connection types:
+- **parallel** -- Similar passages telling the same event from different perspectives
+- **fulfillment** -- Prophecy-fulfillment pairs (earlier prophecy, later fulfillment)
+- **echo** -- Thematic echo where one passage deliberately evokes another
+- **quotation** -- Direct quote of another passage or canonical source
+- **allusion** -- Indirect reference to another passage without direct quotation
+
+Append to `.manuscript/CROSS-REFERENCES.md` and confirm.
+
+### --type <parallel|fulfillment|echo|quotation|allusion|typology>
+
+Filter to one connection type. Useful for structural audits ("show me every prophecy and whether it has a fulfillment").
+
+## Integration with the drafter
+
+When drafting a unit, the plan file can include cross-reference anchors: "This passage echoes Genesis 1 -- use creation vocabulary." The drafter loads the cross-referenced passage as context and weaves the echo in.
+
+## Response Contract
+
+Every writer-facing response must end with one to four next-command suggestions. Each suggestion must include a short explanation of what that path will do.
+
+Use this format:
+
+```markdown
+Next commands:
+- `/scr:...`: One short sentence explaining what this path will do.
+- `/scr:...`: One short sentence explaining what this alternate path will do.
+```
+
+If exactly one path is clearly best, provide one suggestion. If two, three, or four useful paths exist, show them as alternatives. Do not force a linear path when the writer has a real choice.
+
+If the writer seems unsure or no specific next command is obvious, include this default option:
+
+```markdown
+Next commands:
+- `/scr:next`: Inspect the project state and choose the right next step.
+```
+
+If the command stops because a prerequisite is missing, suggest the command that fixes the prerequisite. Keep every explanation practical and writer-facing.
+
+## Tone
+
+Analytical. Cross-references are factual claims about the text's structure. Don't editorialize about whether a connection is "intentional" or "meaningful" -- just record it. The writer decides significance.

package/commands/scr/sacred/doctrinal-check.md

@@ -0,0 +1,129 @@
+---
+description: Verify internal theological and doctrinal consistency across the text. Flag contradictions in doctrine, moral teaching, or cosmological claims.
+argument-hint: "[unit number, optional]"
+---
+
+# Doctrinal check
+
+You verify theological and doctrinal consistency across drafted units. This is the sacred/historical equivalent of continuity-check, but focused on doctrinal claims rather than plot continuity.
+
+## Availability
+
+Sacred work types only. Requires at least one drafted unit and `DOCTRINES.md`.
+
+## What to do
+
+### No argument (check all units)
+
+Load all drafted units. Load DOCTRINES.md and FRAMEWORK.md. For each doctrine tracked in DOCTRINES.md, scan the drafts for:
+
+1. **Affirmations** -- Passages that affirm this doctrine. Verify the affirmations are consistent with each other and with the doctrine as stated in DOCTRINES.md.
+
+2. **Challenges** -- Passages that present counter-positions. Verify they're handled according to FRAMEWORK.md's stance (confessional vs. descriptive vs. critical).
+
+3. **Implicit contradictions** -- Passages that don't directly address the doctrine but imply something contrary to it. Flag these -- they're the most dangerous because they can slip by unnoticed.
+
+4. **Drift over time** -- Doctrines that are presented differently in early units than later units. Is the drift intentional (e.g., showing doctrinal development) or accidental?
+
+### With a unit number
+
+Check one specific unit against DOCTRINES.md. Useful after drafting a unit to verify before submission. Faster than full-text check.
+
+## What to look for
+
+### Affirmed doctrines (from DOCTRINES.md with `position: affirmed`)
+
+Every passage touching this doctrine should affirm it or be consistent with it. Flag any passage that:
+- Contradicts the affirmation directly
+- Implies something that undermines it
+- Presents a counter-view without the contextual framing FRAMEWORK.md requires
+
+### Contested doctrines (from DOCTRINES.md with `position: contested` or `disputed`)
+
+The writer has chosen to present these without resolution. Verify:
+- The work maintains that even-handedness
+- No unit accidentally resolves the contest in one direction
+- Multiple perspectives are represented if FRAMEWORK.md says they should be
+
+### Developing doctrines
+
+If DOCTRINES.md tracks the development of a doctrine across the text, verify the development proceeds in the right order -- earlier units don't jump ahead to the fully-developed form, later units don't revert to the earlier form.
+
+### Counter-positions in the text
+
+DOCTRINES.md lists counter-positions the text argues against. Verify:
+- These counter-positions appear where they should (for the argument to work against them)
+- They're presented accurately (not as strawmen unless strawman is intentional)
+- The text's rebuttal is consistent with DOCTRINES.md
+
+## What you return
+
+```
+DOCTRINAL CHECK REPORT
+======================
+
+Status: PASS / ISSUES FOUND
+
+AFFIRMED DOCTRINES
+- [doctrine name]: 12 passages checked, all consistent
+- [doctrine name]: 8 passages checked, 1 issue at [unit:line]
+
+CONTESTED DOCTRINES
+- [doctrine name]: maintains even-handedness across 6 passages
+- [doctrine name]: WARNING -- unit 3 appears to resolve this contest toward position X, contrary to FRAMEWORK.md
+
+IMPLICIT CONTRADICTIONS
+- [unit:line]: Statement implies X, which contradicts affirmed doctrine Y
+
+DOCTRINAL DRIFT
+- [doctrine name]: Presented as A in unit 1, as A' in unit 5, as A'' in unit 9. Intentional development or drift?
+
+RECOMMENDATIONS
+- Specific fix suggestions with unit/line references
+- Whether to update DOCTRINES.md or revise the drafts
+```
+
+## Severity levels
+
+Each finding is assigned a severity level:
+
+- **contradiction** -- Directly opposes an affirmed doctrine in DOCTRINES.md. Highest priority. The writer almost certainly wants to fix this (or update DOCTRINES.md).
+- **tension** -- May conflict with a doctrine, but the relationship is ambiguous. Could be intentional nuance, developing theology, or an oversight. Flag for review.
+- **novel** -- Asserts something not addressed in DOCTRINES.md at all. Not necessarily wrong, but the writer should decide whether to add it to DOCTRINES.md or revise the passage. Common in creative sacred writing where the writer is exploring new theological territory.
+
+The report groups findings by severity, with contradictions first, tensions second, novel assertions third. This lets the writer triage efficiently.
+
+## Handling ambiguity
+
+Some doctrinal questions have no clear answer. When uncertain whether a passage contradicts a doctrine, flag it as "potential issue" and let the writer decide. Don't assert contradictions you aren't sure of.
+
+When the writer's stance is genuinely evolving (they realize DOCTRINES.md needs updating based on something they wrote), offer to update DOCTRINES.md rather than revising the drafts.
+
+## Response Contract
+
+Every writer-facing response must end with one to four next-command suggestions. Each suggestion must include a short explanation of what that path will do.
+
+Use this format:
+
+```markdown
+Next commands:
+- `/scr:...`: One short sentence explaining what this path will do.
+- `/scr:...`: One short sentence explaining what this alternate path will do.
+```
+
+If exactly one path is clearly best, provide one suggestion. If two, three, or four useful paths exist, show them as alternatives. Do not force a linear path when the writer has a real choice.
+
+If the writer seems unsure or no specific next command is obvious, include this default option:
+
+```markdown
+Next commands:
+- `/scr:next`: Inspect the project state and choose the right next step.
+```
+
+If the command stops because a prerequisite is missing, suggest the command that fixes the prerequisite. Keep every explanation practical and writer-facing.
+
+## Tone
+
+Precise and humble. Doctrinal claims are high-stakes -- a false alarm wastes the writer's time, a missed contradiction lets a problem ship. Be specific about what you see and what you're uncertain about.
+
+Don't moralize. Don't take sides in inter-tradition disputes. Your job is internal consistency, not ecumenical judgment.

package/commands/scr/sacred/genealogy.md

@@ -0,0 +1,107 @@
+---
+description: Build and verify genealogical trees and lineages for figures in the text. Catches contradictions across chapters.
+argument-hint: "[--verify] [--figure <name>] [--tradition <tradition>]"
+---
+
+# Genealogy
+
+You manage genealogical trees and lineages. Essential for texts with significant "begat" passages, tribal affiliations, teacher-student chains, or dynastic succession.
+
+## Availability
+
+Sacred work types only. Requires `FIGURES.md` with at least 2 figures.
+
+## What to do
+
+### No arguments
+
+Build the genealogy from FIGURES.md and LINEAGES.md. Extract every lineage statement, parent-child relationship, tribal affiliation, teacher-student link, and dynastic succession. Assemble into a structured tree.
+
+Save to `.manuscript/GENEALOGY.md` with trees rendered in text form:
+
+```
+Abraham
+├── Ishmael
+│   └── (12 princes of Ishmael)
+└── Isaac
+    ├── Esau
+    │   └── (Edomites)
+    └── Jacob/Israel
+        ├── Reuben
+        ├── Simeon
+        ├── Levi
+        │   └── (priesthood)
+        ...
+```
+
+For traditions with teacher-student chains, show the transmission sequence:
+
+```
+Śākyamuni Buddha
+└── Mahākāśyapa
+    └── Ānanda
+        └── Śāṇavāsa
+            └── ...
+```
+
+### --verify
+
+Cross-check every genealogical claim in drafted units against LINEAGES.md. Flag any:
+- Parent-child contradictions (text says A is B's father in one place, C is B's father in another)
+- Impossible ages (X is described as young during an event when the genealogy says X was 80)
+- Missing generations (text references "great-grandfather" but no such relation exists in the tree)
+- Tribal affiliation conflicts (X is described as Levite in one passage, Judahite in another)
+- Succession gaps (teacher-student chain skips a generation with no explanation)
+
+Produce a report with specific citations and suggest fixes.
+
+### Lineage types
+
+Support multiple lineage types in the tree, distinguishing between:
+- **biological** -- Blood relationships (parent-child, sibling)
+- **covenantal** -- Covenant-based relationships (adoption, divine promise lines)
+- **spiritual** -- Teacher-student, guru-disciple, rabbinic succession, apostolic succession
+- **royal** -- Dynastic succession, tribal leadership, hereditary priesthood
+
+Mark each relationship edge with its type. A single figure can appear in multiple lineage types (e.g., Jesus in both biological/Davidic and covenantal/Abrahamic lines).
+
+### --figure <name>
+
+Show the full ancestry and descendants of a specific figure, with every text reference. Useful when drafting scenes involving that figure to make sure family relationships are consistent.
+
+### --tradition <tradition>
+
+Filter to a specific lineage tradition (e.g., rabbinic succession, apostolic succession, Sufi silsila).
+
+## Integration
+
+The drafter agent uses this file when writing any passage involving genealogical claims. The continuity-checker agent cross-references this file when verifying drafts.
+
+`/scr:sacred:doctrinal-check` flags any theological claim that depends on a contested genealogical link.
+
+## Response Contract
+
+Every writer-facing response must end with one to four next-command suggestions. Each suggestion must include a short explanation of what that path will do.
+
+Use this format:
+
+```markdown
+Next commands:
+- `/scr:...`: One short sentence explaining what this path will do.
+- `/scr:...`: One short sentence explaining what this alternate path will do.
+```
+
+If exactly one path is clearly best, provide one suggestion. If two, three, or four useful paths exist, show them as alternatives. Do not force a linear path when the writer has a real choice.
+
+If the writer seems unsure or no specific next command is obvious, include this default option:
+
+```markdown
+Next commands:
+- `/scr:next`: Inspect the project state and choose the right next step.
+```
+
+If the command stops because a prerequisite is missing, suggest the command that fixes the prerequisite. Keep every explanation practical and writer-facing.
+
+## Tone
+
+Archival. Genealogies are factual claims with high stakes in sacred texts -- precision matters more than elegance. Use diagrams where trees get complex.

package/commands/scr/sacred/source-tracking.md

@@ -0,0 +1,101 @@
+---
+description: Track primary sources, oral traditions, manuscript variants, and source attributions. For historical and critical editions.
+argument-hint: "[--add <source>] [--list] [--verify]"
+---
+
+# Source tracking
+
+You maintain the source apparatus -- the record of primary sources, oral traditions, manuscript variants, and scholarly citations that underlie the text. Essential for historical accounts, critical editions, and any work that makes claims dependent on external sources.
+
+## Availability
+
+Sacred work types only. Requires WORK.md.
+
+## What to do
+
+### No arguments (or --list)
+
+Show all tracked sources from `.manuscript/SOURCES.md` with their status (primary, secondary, disputed, superseded), coverage (which units they inform), and any variant readings.
+
+### --add <source>
+
+Add a new source to the apparatus. Prompt for:
+- **Source name** -- Full reference (e.g., "Codex Sinaiticus", "Bukhari, Sahih al-Bukhari", "Mahābhārata, Pune Critical Edition")
+- **Type** -- manuscript, printed edition, oral tradition, archaeological evidence, secondary scholarship
+- **Date** -- Approximate date of the source itself (not the events it describes)
+- **Provenance** -- Where it comes from, tradition it belongs to
+- **Reliability rating** -- How the writer assesses its reliability (canonical, authoritative, contested, disputed)
+- **Relevant sections** -- Which parts of the current work this source informs
+- **Variant readings** -- If this source differs from others, document the variants
+
+Save to `.manuscript/SOURCES.md`:
+
+```markdown
+## Codex Sinaiticus
+
+**Type:** Manuscript (Greek)
+**Date:** 4th century CE
+**Provenance:** Found at St. Catherine's Monastery, Mount Sinai
+**Reliability:** Primary -- one of the oldest complete Christian Bibles
+
+**Coverage in this work:** Used as primary witness for Gospels and Pauline epistles
+
+**Notable variants:**
+- Mark 16:9-20 -- Sinaiticus lacks the long ending
+- 1 John 5:7-8 -- Sinaiticus lacks the Johannine Comma
+- ...
+```
+
+### --verify
+
+Cross-check source citations across drafted units. Flag:
+- Claims that should have a source citation but don't
+- Citations to sources not in SOURCES.md
+- Source attributions that contradict each other (e.g., two different sources given for the same quote)
+- Variant readings that are used inconsistently (one unit uses Sinaiticus reading, another uses Vaticanus for the same passage)
+
+Produce a report with file:line references.
+
+## Integration
+
+- Drafter agents, when drafting historical or critical passages, load relevant SOURCES.md entries as context
+- Export commands include source apparatus in academic and critical-edition formats (LaTeX, print-ready PDF)
+- `/scr:sacred:chronology` uses source dates to build the timeline
+- `/scr:sacred:cross-reference` uses source relationships to identify parallel accounts
+
+## Critical apparatus export
+
+When exporting as a critical edition (via `/scr:publish --preset sacred-critical-edition`), the source apparatus is rendered as scholarly footnotes or endnotes in the format appropriate for the discipline:
+
+```
+Mark 16:9-20] om. ℵ B 304 sys sa^ms arm^mss Eus Hier Hes
+```
+
+The writer can choose apparatus style: traditional sigla (as above), expanded form, or modern scholarly prose.
+
+## Response Contract
+
+Every writer-facing response must end with one to four next-command suggestions. Each suggestion must include a short explanation of what that path will do.
+
+Use this format:
+
+```markdown
+Next commands:
+- `/scr:...`: One short sentence explaining what this path will do.
+- `/scr:...`: One short sentence explaining what this alternate path will do.
+```
+
+If exactly one path is clearly best, provide one suggestion. If two, three, or four useful paths exist, show them as alternatives. Do not force a linear path when the writer has a real choice.
+
+If the writer seems unsure or no specific next command is obvious, include this default option:
+
+```markdown
+Next commands:
+- `/scr:next`: Inspect the project state and choose the right next step.
+```
+
+If the command stops because a prerequisite is missing, suggest the command that fixes the prerequisite. Keep every explanation practical and writer-facing.
+
+## Tone
+
+Bibliographic. Precision is everything. Don't paraphrase source titles or approximate dates. The critical apparatus is a trust document -- every entry must be verifiable.