​
Series Support

Scritorio should support book series as an optional project shape. Authors should be able to start with one book and later create or attach it to a series without reorganizing the book’s core Markdown model.

​
Core Concept

A Scritorio project may be:
  • a standalone book
  • a book inside a series
  • a full series workspace containing multiple books
Series-level material should be available to individual books when the author chooses to include it, but each book should still have its own manuscript, reports, publishing metadata, and revision history. The library UI should show standalone books at the top level. Series should appear as expandable top-level items with their books nested underneath. Moving a standalone book into a series should move the local book folder into series/books/. Moving a book out of a series should move it back to the top-level Scritorio projects folder. The filesystem remains the source of truth for whether a book is standalone or series-owned. The create flow should use separate New book and New series panels. A series should not contain nested series. A new series starts with series.md, books/, shared/, and .scritorio/settings.json. Series should have a series_type:
  • fiction
  • nonfiction
  • mixed
Mixed series are important for projects that combine story books with companion nonfiction, such as a fictional universe plus a handbook, glossary, atlas, textbook-style reference, or research guide. In that model, individual books keep their own book_type, while the series provides the shared container.

​
Series-Level Content

Series workspaces should support shared material such as:
  • series bible
  • global timeline
  • recurring characters
  • recurring locations
  • worldbuilding or research canon
  • terminology and style rules
  • series arc
  • continuity notes
  • shared visual assets

​
Book-Level Content

Each book in a series should support its own:
  • manuscript
  • outline
  • local timeline
  • book-specific cast or source notes
  • editorial reports
  • Editorial Board customizations
  • reader reactions
  • coaching history
  • visual assets
  • publishing metadata
  • export configuration

​
Context Boundaries

Series support must preserve context control. When reviewing a scene, chapter, or manuscript, Scritorio should make it clear whether the AI context includes:
  • only the current book
  • current book plus selected series context
  • previous books
  • future-book planning notes
  • series bible entries
Blind reader mode should not see series context unless the author explicitly gives the reader that knowledge.

​
Continuity Across Books

Series-aware review should help catch:
  • character name or trait drift
  • timeline contradictions
  • location changes
  • world rule changes
  • repeated terminology changes
  • unresolved promises from prior books
  • accidental spoilers from future-book notes
  • contradictions between book-level events and series-level canon

​
Publishing Across A Series

Long-term publishing support should allow series metadata and book metadata to work together. This may include:
  • series title
  • book number
  • reading order
  • shared imprint metadata
  • shared style and layout profile
  • per-book ISBN and export settings
  • series-level front or back matter templates

​
CLI And Agent Support

The CLI should be able to inspect and operate series workspaces. Expected capabilities:
  • list books in a series
  • show current book context
  • validate series structure
  • search across one book or the full series
  • preview AI context by scope
  • run continuity checks against selected prior books or series bible material
The app and CLI should make scope visible so agents do not accidentally mix book-specific and series-wide context.