Success Criteria
Scritorio succeeds when it helps authors revise more clearly without taking over authorship.MVP Success
The MVP should prove that Scritorio can serve fiction authors well enough to justify the broader product:- open a local Markdown project
- identify a normal single-book project as a book, not a series
- edit manuscript files
- search project files
- parse front matter
- run a useful editorial review
- run a blind persona reader reaction
- save feedback locally as Markdown
- identify or create a useful visual planning asset
- show what context will be sent before an AI call
- run core project inspection and review workflows through the CLI
Fiction Proof
Using the example project, Scritorio should be able to:- find scenes, characters, locations, and handbook files
- catch naming or terminology drift
- check selected scene context against relevant canon
- distinguish book-level context from series-level context
- simulate a blind reader reaction without leaking worldbuilding notes
- preserve project style guidance
Series Proof
Scritorio should prove that an author can:- create or open a series workspace
- list books in the series
- set the current book
- keep shared series context separate from book-specific content
- run a review against current-book context only
- run a review against current-book plus selected series context
- search within one book or across the series
- avoid leaking future-book planning notes into blind reader mode
Version 2 Technical And Nonfiction Proof
Using a technical or nonfiction sample project in Version 2, Scritorio should be able to:- identify a chapter thesis
- flag unsupported or unclear claims
- identify citations, footnotes, bibliography entries, and missing source coverage
- suggest draft index terms for author review
- review section order
- suggest clearer examples or visual explainers
- distinguish source-aware review from blind reader review
Index And Bibliography Proof
For nonfiction projects, Scritorio should be able to:- preserve footnotes and endnotes in local Markdown-compatible form
- connect claims to source notes and bibliography records
- suggest index terms and cross-references
- produce a draft index or bibliography that the author can review
- keep final authority with the author, especially for index wording and source inclusion
Visual Proof
Visual Studio should be able to:- suggest where a visual would help
- generate or refine a prompt from selected context
- save visual assets locally
- record source context and prompt history
- link a visual back to the relevant manuscript section
- support cover art concepts and interior illustrations as distinct asset roles
- support chapter art, page art, spreads, and children’s book visual planning
- track whether an asset is draft concept art, an approved candidate, or a final production asset
Writing Coach Proof
The Writing Coach should be able to:- generate a focused assignment from a skill area, manuscript passage, or curriculum path
- show assignments in project navigation by status
- show active curriculum progress when the author is following a guided module
- let the author write and revise an assignment response
- review the response with a rubric tied to the assignment goal
- save the assignment, submission, feedback, and revision prompt locally
- suggest one manuscript-linked revision task after review
- maintain an author-editable writer profile that helps calibrate future assignments
- preserve a clear distinction between app-managed curriculum content and author-owned local writing
Quality Bar
Feedback should be:- specific
- actionable
- tied to author intent
- honest about uncertainty
- respectful of author voice
- separated by severity and purpose
Publishing Path Proof
Long-term, Scritorio should prove that an author can:- start a project from a blank folder
- follow coaching assignments from idea formation through drafting
- revise through editorial and reader workflows
- assemble a complete manuscript
- prepare front matter, back matter, notes, index, and bibliography material
- prepare cover and interior visual assets
- run preflight checks for publication readiness
- export reviewable PDF and EPUB files
- produce an ebook package from the reviewed manuscript source
- create an audio-version plan with narrator voice, character voice assignments, pronunciation notes, and reviewable generated clips
- prepare vendor-specific self-publishing packages, including an IngramSpark-oriented profile
Agent And CLI Proof
Scritorio should prove agent usability by supporting CLI workflows that can:- inspect project state
- list files and parsed metadata
- run search
- preview AI context
- create a local report
- return structured JSON when requested
- avoid hidden provider calls