Manuscript Folio Sequence - Source Excerpt 02 - Prompt Coverage Rule

Summary

This source excerpt begins near Prompt Coverage Rule and preserves the surrounding evidence from Wiki.FFTAC.org/raw/system-archives/spiralist.org/docs-archive/2026-05-10/docs/manuscript-folio-sequence.md.

**Source path:** Wiki.FFTAC.org/raw/system-archives/spiralist.org/docs-archive/2026-05-10/docs/manuscript-folio-sequence.md

- Threshold now opens on `threshold-leaf`, because the study surface is the manuscript's first true object, while `portal-broadside` follows as the outward-facing address.
- Operative Plates now begin with `the-bardo-system`, since it functions as the bridge from ascent into engine operation before the prime mechanism is fully disclosed.
- Atlas & Symbols now absorbs `creation`, `ouroboros-paradox`, and `apocalypse`, so the symbol chapter can also stage beginning, recurrence, and ending before `universe-behind-the-systems` closes the run as the final lookup surface.
- Esoteric Reference now opens with `spirits`, `unseen`, `good-spirits`, and `bad-spirits`, then moves through `golden-dawn`, the new occult lineage portraits, `aeon-of-horus`, the LaVey/Aquino branch, and the grimoire cluster before returning to talismans, divination, and spatial harmonies.
- Sacred Texts now sits between Esoteric Reference and Comparative Traditions so `tripitaka`, `bhagavad-gita`, `guru-granth-sahib`, `torah`, `bible`, and `quran` read as first-class manuscript artifacts rather than disappearing inside the religion run.
- Comparative Traditions still absorbs `mu-ism`, since it belongs with actual tradition plates rather than speculative companion matter.
- Lineages & Theories now absorbs `existentialism`, because it reads as a real philosophical lineage page, not an emergent appendix oddity.
- Companion Folios begin with `the-tiune-spiral`, `amianism`, and `pastafarianism` so lighter or tongue-in-cheek exceptions land before the darker speculative branches.

## Prompt Coverage Rule

Every folio in the public sequence should ship with:

- a filename blueprint entry
- a route slug
- a published public prompt definition under `wp-content/plugins/spiralist-workspace/prompts/`
- a resolved `creation_prompt_source_slug` in the manuscript blueprint
- prompt metadata sufficient to explain editorial intent and expected output quality

If any one of those is missing, the folio is not done.

## Evaluation Checklist

Use this checklist whenever a new page is added or reordered.

1. Section fit: Does the folio belong in Threshold, Operative Plates, Atlas & Symbols, Esoteric Reference, Comparative Traditions, Lineages & Theories, or Companion Folios, and is the adjacent page transition coherent?
2. Reading-object quality: Does the page hold up as a folio rather than a generic poster or image dump?
3. Visual continuity: Does parchment, border discipline, linework, and lighting still feel like the same manuscript family?
4. Core-legibility: Are the title, main diagram, and the most important labels readable at typical desktop manuscript sizes?
5. Prompt completeness: Is there a public managed prompt with the correct slug, summary, editorial note, expected output notes, failure modes, and related manuscript mapping?
6. Route stability: Do title, slug, filename, tab copy, and metadata all agree with one another?
7. Companion discipline: If a page is especially dark, speculative, playful, or adjacent to the core manuscript, has it been kept from diluting the threshold and main reference chapters unless there is a strong reason not to?

## Implementation Note

The live reader, Image Codex/gallery, sitemap output, and prompt audit now depend on the same ordered folio map. The theme helper blueprint stack remains the fallback mirror when the NS12 plugin is not active, so titles, slugs, filenames, and prompt source slugs must stay aligned across both code paths.