Skip to main content

Live Editor Technical Notes

This page describes the current Studio shell and Bookcicle Editor behavior.

Short Answer​

The current product does show a real editor and Studio shell, but some surrounding areas are still placeholders or partial implementations.

Main Studio Shell​

Current shell behavior includes:

  • drawer panels for files, sync, and collab
  • split-right and split-down pane layout
  • draggable tabs and pane reordering
  • projection tabs alongside the main manuscript tab
  • multiple file-type pane surfaces instead of a manuscript-only shell

The current shell mounts real pane surfaces for:

  • the main manuscript
  • projection views
  • Markdown
  • HTML
  • plain text
  • images
  • PDF
  • DOCX
  • EPUB
  • media files

Persistence Model​

Important current defaults include:

  • local layout and session persistence enabled by default
  • autosave runs at roughly an 800 ms cadence
  • pane layout, pane sizes, tab state, projection state, selection state, cursor state, scroll state, and editor view state all persisted by default

The persistence contract is real even though the long-term storage strategy is still adapter-based.

Live Editor Surface​

The current editor package supports:

  • prose and screenplay profiles
  • configurable outline sidebar
  • page-style editor mode
  • grammar and spelling hooks via LanguageTool
  • manual AI editing hooks
  • auto-edit settings and review settings
  • local search and replace
  • semantic outline generation
  • screenplay block roles and screenplay navigation behavior

Notable current defaults:

  • novel mode is the default writing profile
  • manual AI editing is available
  • automatic AI editing is off by default
  • AI edit review remains on
  • the outline is shown by default on the left side

Projection Model​

The projection workflow is one of the clearest Live Editor behaviors right now.

Current behavior:

  • the manuscript can be broken into section-based units
  • projections can open one section in its own tab
  • semantic outline items and projection tree nodes are linked
  • large manuscripts can switch into a section-windowing approach for section-level work

The current windowing helpers use:

  • section-aware document structure
  • heading detection
  • screenplay scene-heading detection
  • a threshold of roughly 50000 HTML characters before switching into the section-windowing path
  • a minimum of 3 sections before treating the document as section-windowable

Collaboration State​

The collaboration shape exists, but the transport story is still partial.

What exists now:

  • a shared document model for local collaboration
  • browser tab-to-tab update sharing
  • initial editor content can be loaded into that shared document state

What does not exist here yet:

  • a real remote collaboration transport
  • a finished collaboration UI

So the current product supports local collaboration primitives, but not a fully shipped remote multi-user collaboration product.

Sync State​

The sync story is even more obviously scaffolded.

That panel currently says:

  • workspace is local only
  • remote state is not connected
  • sync diagnostics are future wiring

So sync should not be documented as a shipped remote feature.

What Should Be Documented as Real Today​

Based on the current product behavior, the safe claims are:

  • Studio is a real multi-pane workspace shell
  • the Bookcicle Editor is a real rich-text editor package
  • projection/focus editing is real
  • outline-driven navigation is real
  • screenplay-aware authoring is real
  • local persistence structure is real
  • local collaboration primitives exist

The unsafe claims would be:

  • fully shipped remote sync
  • fully shipped multi-user collaboration
  • fully shipped comments, redline, or revision history inside this surface