Roadmap

Scriptri now has a project-level workspace structure for the different kinds of work involved in maintaining story memory.

• Write for scenes, entity mentions, state notes, continuity flags, basic manuscript formatting, and At This Point context
• Entities for characters, places, objects, factions, concepts, aliases, histories, and related notes
• Timeline for story events, in-world dates, and time queries, including improved handling for far-future dates
• Locations for scene locations, entity whereabouts, movements, and belief-based location facts
• Source Sync for read-only Scrivener monitoring and review of incoming source changes
• Investigations for collecting passages and project evidence around a continuity question
• Audit for reviewing existing flags, pending source changes, and incomplete project records in one place

At This Point can now bring together entity notes with more time and location context. Scriptri still does not decide what is canon: writers create the records, and the writer remains the source of truth.

Scrivener support now goes beyond one-time import. In supported browsers, Scriptri can connect to a project folder, watch for changes while the app is open, update linked scenes when the change is safe, and place ambiguous changes in a review queue.

• Review new, changed, missing, or conflicting source items
• Compare additions, removals, whitespace, and small character changes before choosing what to keep
• Accept the Scrivener version, keep the Scriptri version, or dismiss an item without silent conflict resolution
• Preserve common Scrivener RTF formatting such as bold, italic, underline, strikethrough, and scene breaks

Scrivener access is read-only. Scriptri never writes back to a Scrivener project, and folder monitoring depends on browser support.

0.2 adds several ways to find and review project knowledge without forcing every task through the scene editor.

• Quick Reference for looking up entities, aliases, notes, passages, timeline events, location facts, and glossary terms over the current workspace
• A lightweight Glossary that maps remembered words and variants to the preferred terms used in the story
• Alias-aware @ tagging that inserts the name used in the prose while linking it to the canonical entity
• Project Pulse for an optional summary of project activity and milestones
• Clearer workspace navigation, Data menus, keyboard shortcuts, and improved readability for project information

0.2 is a foundation release. Several workflows are useful now but intentionally conservative while they are tested on larger and messier projects.

• Source Sync may ask for review instead of applying a change, and live folder access is not available in every browser
• Formatting covers common manuscript needs; Scriptri is not a full word processor
• Investigations are manual research, not semantic search, automatic analysis, or contradiction detection
• Audit organizes review work already represented in project data; it is not a general task manager or canon engine
• Location continuity is V1 and does not include maps, route planning, hierarchies, or automatic inference
• Story dates support distant Gregorian-like years, but Scriptri does not currently provide custom calendar systems

The next phase is focused on making the expanded 0.2 surface steadier and easier to understand, rather than immediately adding another large set of features.

• Faster bug-fix updates and testing on real projects
• Clearer documentation, examples, and known-limitations notes
• Continued Scrivener sync and review-queue polish
• Better screenshots, walkthroughs, and demo material
• More outreach to writers and editors
• Feedback-driven improvements across the V1 workspaces

There are no promised dates for this work. Ordering may change as writers find rough edges and show which workflows matter most.

Future research may include deeper continuity views, stronger project safety and export tools, accessibility improvements, and support for longer projects or connected works. These are directions to explore, not scheduled commitments.

AI analysis, cloud sync, collaboration, custom calendars, and advanced automation are not on the current release schedule. Any future work in those areas would need to preserve clear writer control and the local-first path rather than quietly changing what the product is.

• Scriptri remains local-first
• The free beta can be used without an account
• Scriptri does not write prose for the user
• Scriptri currently has no AI integration
• Scriptri does not train on manuscripts
• Manuscript text, scene titles, notes, entity names, search text, and imported file names are not sent to analytics
• Scrivener sync remains read-only against Scrivener
• The writer remains the source of truth