Skip to content
wiki.fftac.org

Manuscript Page

**Site relevance:** Spiralist.org

**Memory type:** docs archive

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

**Size:** 4.4 KB

Summary

The manuscript surfaces must stay human-first and fully linkable across enabled locales.

Source Headings

  • Manuscript Page
  • Current Public Surfaces
  • Workstation Rules
  • Locale And Machine-Surface Rule
  • Current Implementation Anchor

Source Preview

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

# Manuscript Page

The manuscript surfaces must stay human-first and fully linkable across enabled locales.

## Current Public Surfaces

The NS12 Manuscript plugin now exposes several public manuscript routes:

- `/manuscript/` for the quick-flip browser across the whole book
- `/manuscript/section/{section-slug}/` for chapter-scoped browsing
- `/manuscript/{folio-slug}/` as the canonical dedicated folio route
- `/manuscript/folio/{folio-slug}/` as a compatibility alias for the same folio route
- `/manuscript/community/`, `/manuscript/studio/`, and `/manuscript/profile/{profile}` for collaboration and participant-specific views when enabled

Locale-prefixed versions of those routes remain canonical through enabled locale tags such as `en-us`, `es-us`, `fr-fr`, and `spiral`.

## Workstation Rules

- Overview and section routes stay in fast browsing mode with thumbnail, jump, TOC, search, and page-turn controls.
- Dedicated folio routes keep one page and its dossier in focus: page notes, prompt linkage, metadata, and related prompts.
- Dedicated folio routes should include a compact "use this folio for..." bridge when prompt mappings are available. Use 2-4 practical actions such as explain in plain English, map symbols to a workflow, generate a teaching summary, create a safe public explainer, or review a related prompt for anthropomorphism and dependency risk.
- Deeper folio, section, symbol, and prompt paths should keep breadcrumbs or equivalent orientation visible so readers can recover the route back to the manuscript.
- The viewer must preserve zoom, raw-image access, facing or single-page reading, and optional study-surface overlays when a folio supports them.
- The Runtime Path drawer shows current execution state, active symbols, recent traversal events, and executable next nodes from Spiralist Engine without replacing the folio viewer. Signed-in state is stored by Spiralist Engine; anonymous execution state is browser-local until reset.
- Study overlay nodes can mark the current runtime node, mark executable next nodes, and execute next nodes directly while keeping the drawer and study-field inspector synced.
- Study overlays and future graph views should reveal detail progressively: start with the active page, chapter, or selected symbol, then expose related nodes through hover/focus previews, filters, or explicit mode changes.
- IIIF manifest and IIIF search links stay available from the workstation when the runtime exposes them.
- The manuscript image remains the anchor object. Supporting metadata, prompts, and overlays must not overwhelm the artifact itself.
- Long technical, legal, UAIX, protocol, and machine-route details should remain accessible but should move behind compact sections, tabs, or drawers when they are not part of the folio's primary reading task.
- Do not add redundant link panels or spacer sections when those destinations are already reachable through the main site navigation or dossier controls.
- Do not reserve empty viewport height below the workstation or between the workstation and footer. Compress the chrome and let the artifact use the space.

## Locale And Machine-Surface Rule

When the Spiral Script locale is active:

- The manuscript image remains visible.
- Workstation chrome and inspector text may translate.
- Search, dossier, and inspector text can render symbolically where possible.
- Raw node JSON or machine documents stay out of the primary reading surface.
- The active manuscript page must still be copyable and reopenable through its locale-prefixed URL.

When a UAIX machine exchange route is opened:

- The human manuscript route stays a separate reading surface.
- The UAI-1 exchange envelope stays on its dedicated `/wp-json/uaix/v1/*` machine route.

## Current Implementation Anchor

- `wp-content/plugins/ns12-manuscript/includes/frontend.php`
- `wp-content/plugins/ns12-manuscript/includes/runtime.php`
- `wp-content/plugins/ns12-manuscript/templates/manuscript-workstation.php`
- `wp-content/plugins/ns12-manuscript/assets/js/manuscript-workstation.js`
- `wp-content/plugins/spiralist-engine/spiralist-engine.php`
- `wp-content/themes/spiralist/assets/data/manuscript-nodes.json`

For the current book order, prompt mapping, and editorial evaluation checklist, see [Manuscript Folio Sequence](manuscript-folio-sequence.md).

For the proposed next step, see [WordPress Runtime Overview](wordpress-runtime/README.md).
Website health report