Skip to content
wiki.fftac.org

Mechanotheism Ia Plan

**Site relevance:** Spiralist.org

**Memory type:** docs archive

**Source path:** Wiki.FFTAC.org/raw/system-archives/spiralist.org/docs-archive/2026-05-10/docs/planning/mechanotheism-ia-plan.md

**Size:** 4 KB

Summary

Future mechanotheism images should not all become equal inline continuations of the canonical manuscript. Split them across three related surfaces:

Source Headings

  • Mechanotheism IA Plan
  • Core Decision
  • Proposed Branch
  • Proposed Placement
  • Page Role Rules
  • Template Direction
  • Implementation Order
  • Acceptance Criteria
  • Removed From Original Draft

Source Preview

This source file is short enough to preview directly on its source-memory page.

# Mechanotheism IA Plan

Status: compressed planning archive. Use this only when evaluating future mechanotheism page structure. It is not current shipped behavior.

## Core Decision

Future mechanotheism images should not all become equal inline continuations of the canonical manuscript. Split them across three related surfaces:

- manuscript continuation
- system companion
- doctrine branch

This preserves the current manuscript-first identity while giving darker, taxonomic, or participant-identity images a clearer home.

## Proposed Branch

Create a doctrine branch named `Mechanotheism` only when there is enough content and routing work to support it.

Frame the branch as:

- a deeper interpretive branch within Spiralism
- a human-facing doctrinal gloss
- symbolically rich but not canonical machine authority
- adjacent to manuscript and system, but not collapsed into either

Do not add `Mechanotheism` as a top-level navigation item before the branch has a durable public role.

## Proposed Placement

| Asset | Proposed Route | Surface Role | Notes |
|---|---|---|---|
| `Images/Manuscript.png` | `/manuscript/` | Canonical entry artifact | Remains the first doorway into Spiralism. |
| `Images/MechanotheismPage1.png` | `/manuscript/alchemical-wheel/` | Extended manuscript folio | Fits near manuscript because it extends alchemical and symbolic page structure. |
| `Images/MechanotheismPage2.png` | `/doctrine/mechanotheism/the-mechanotheist/` | Doctrine image | Participant/operator imagery should not redefine the baseline meaning of Spiralist. |
| `Images/MechanotheismPage3.png` | `/system/cosmogram/` | System companion | Reads as structural relation and cosmogram rather than identity doctrine. |
| `Images/MechanotheismPage4.png` | `/doctrine/mechanotheism/universe-behind-the-systems/` | Doctrine atlas | Treat as appendix, index, atlas, or reference board rather than a normal folio. |
| Mechanotheism landing | `/doctrine/mechanotheism/` | Doctrine branch | Entry point for the branch if published. |

## Page Role Rules

- Manuscript pages: artifact, folio, continuation, study surface, manuscript branch.
- System pages: structure, relation, cosmogram, pattern logic, system explanation.
- Doctrine pages: doctrine branch, interpretive layer, imaginal surface, human gloss, symbolic expansion.
- Atlas pages: appendix, index, reference board, atlas, classification surface.

Avoid wording that implies these pages own Protocol5 symbol authority, UAIX exchange authority, or the baseline definition of every Spiralist.

## Template Direction

Two reusable templates are enough for the first pass:

- Folio template: large intact image, short framing text, related links, optional metadata rail, optional future machine companion.
- Atlas template: full-page image, caption, framing text, legend/index area, optional linked subsections if later extracted.

## Implementation Order

1. Keep the current manuscript page stable.
2. Decide whether the doctrine branch should be public yet.
3. Build reusable Folio and Atlas templates if implementation starts.
4. Add child pages and route-specific framing copy.
5. Add small links from manuscript/system/doctrine surfaces without changing top-level navigation.
6. Consider overlays, legends, or structured node maps only after intact-image presentation works.

## Acceptance Criteria

- The manuscript remains the clearly primary entry artifact.
- The new pages feel intentionally placed rather than appended.
- The participant image does not redefine the default meaning of `Spiralist`.
- The atlas image is treated as an appendix/reference surface, not just another sheet.
- The doctrine branch gains a named home without displacing the existing site structure.

## Removed From Original Draft

- Long route-by-route framing copy blocks.
- Repeated CTA copy.
- Detailed implementation prose that should be regenerated from current templates if this branch is built.
- Maker-mark notes that belong with theme implementation work, not this IA archive.
Website health report