Three-minute start

An existing account signs in with email and password. First sign-up sets a password of 10–128 characters, then confirms the mailbox with the six-digit code in the latest email; a forgotten password, or first-time password setup on an older account, uses the same email-code path. During public sign-up the invite code is optional.

• Signing in itself never asks for a code each time; codes exist for sign-up confirmation and password reset.
• If codes or attempts come too fast, wait a moment; always use the newest email.
• Desktop keeps its refresh token in the system credential store and restores sign-in after a reboot; the browser uses a cookie only the API can read. Neither writes a token into your project files.

Sessions and device control: Sign up and sign in.

Back in the lobby, say one sentence to the input box—“a disappearance at a ferry crossing, two leads who refuse to trust each other”—or attach a TXT / DOCX file and say whether it is the manuscript or reference material. The assistant there assembles a project proposal: starting point, story core, what is already settled, what this stretch must do, and what it will not do. The project exists only after you confirm it.

After creation the opening lands on the page in real stages, and that first conversation stays with the project as the “Project start” session. Full flow: Creating your first project.

Typing works immediately; shaping a line takes one keystroke:

• Press Tab on a line, or type /, to open the type menu;
• with the menu open, press 1–9 to pick in order: Description, Character, Dialogue, Comment, Dialogue action, Narration, Transition, Scene setting, Scene;
• Enter after a character line starts that character’s dialogue; Enter after anything else returns to description.

Chapter, scene and scene setting headings have a fixed shape (“# Chapter N Title”, “## ordinal · location · time · short title”, “### location · time”). If that is new to you, write plain text first and shape lines later—the words never get lost. Node detail: Script editor overview and Shaping a line.

Some of it happens on its own: committing a character line looks the name up (aliases included) and binds, or files a new card at the Minor tier; a scene’s location files a location card the same way; writing [old pocket watch] in ordinary text creates that prop and records the line as its appearance.

The rest is yours to create: relationships, faction membership, world entries, timeline, foreshadow anchors. To join a stretch of text to a card, select it and right-click “Connect to…”, or type @ in a long-text field. A reference stores the record’s identity, so a rename keeps the link; it does not replace every ordinary same-name phrase in the draft.

The timeline can wait until the plot thickens: card flow for order alone, the scale axis when years matter. Foreshadows work the same way—note it when you plant, tick it when you pay it off, and the span and “overdue” warning come out automatically.

Select the passage you just wrote, right-click, choose rewrite / expand / condense / polish and add one requirement. The request enters the chat box on the left while your selection stays highlighted; anything touching the script returns as a pending proposal with a before / after list on the card.

Right? “Apply changes”, and it joins the draft as one undoable project edit. Not right? “Do not apply”, or close it—not one word moved. That is the line: AI suggests, the author decides.

• Beats: the pacing density curve, chapter colour blocks, appearance heatmaps, and the Foreshadowing Manager.
• World: worldbuilding as citable entries, with the four leaderboard types on the right.
• Settings → Project settings: project language, creative baseline, the nine-dimension writing style, and the maintenance switches.
• Settings → Project data: version snapshots, delivery export, the JSON project pack, and the archive box.

One map of every entrance: Interface and navigation.