Question 1

Who is Rookspindle for, and what is it being built to do?

Accepted Answer

Rookspindle is being built for independent and KDP authors writing series-length paranormal romance and erotica, including stories about werewolves, vampires, fae, shifters, demons, witches, mates/bonds, and dark romance. Its mission is to help authors find and fix repeated words, phrases, gestures, sensory beats, and scene choreography, along with continuity drift in characters, lore, timelines, and relationships, while preserving the author’s voice and chosen heat level. This is the product mission; those detection and revision tools are not available as working features today.

Question 2

How is the manuscript workspace planned to work?

Accepted Answer

The planned hierarchy is Series > Book > Part > Chapter > Scene, with drag-and-drop ordering. Planned scene details are POV character, location, timeline date/time, moon phase/season, heat level, emotional beat, word count, and status. These organization and scene-detail capabilities are plans, not features authors can use today.

Question 3

Which manuscript import and export formats are planned?

Accepted Answer

Planned imports are .docx, .txt, .md, Google Docs export, and Scrivener export. Planned exports are .docx, .epub, .pdf, and KDP-ready formatting. The broader format list is not available today. The current app has an implementation path for .docx and .txt import, but it depends on valid deployment manuscript storage; the deployed workflow has not been verified here, so those imports are not being presented as currently available.

Question 4

How will revisions stay in my control?

Accepted Answer

The planned revision flow includes version history with side-by-side diffs. Every AI change is intended to remain a suggestion that the author can accept, reject, or partially accept; original text is never meant to be silently overwritten. This revision history and AI suggestion workflow is planned. Rookspindle does not currently have an AI suggestions feature.

Question 5

What will the Story Bible or Codex track?

Accepted Answer

The planned Story Bible/Codex covers characters, creatures/species, packs/covens/courts, locations, items, magic rules, timelines, relationships, and lore. Facts extracted from a manuscript are intended to be proposals for the author to confirm. Mentions are planned to include nicknames and aliases. Lore and timeline checks are intended to flag contradictions such as impossible travel times and day/night errors. These are roadmap plans, not shipped features.

Question 6

Is adult explicit fiction in scope?

Accepted Answer

Rookspindle’s intended policy is not to apply content filtering, word blocklists, tone-softening, safe rewrites, or heat-level caps to adult characters. The product aims to preserve the author’s chosen vocabulary, anatomy terms, intensity, and dynamics. The sole intended content rule is that every character is an adult (18+): character age is required, characters who are under 18 or whose age is ambiguous are flagged, and sexual generation involving them is disallowed. This describes the intended policy, not a claim that an AI feature can process such content today; no AI suggestions feature is currently available.

Question 7

What can authors use today?

Accepted Answer

Email/password account creation and sign-in are implemented. The manuscript workspace includes paths for creating series and books, importing .docx or .txt files, editing scenes, and saving them, but these actions are not available to authors yet. They require a valid deployment encryption key, and the deployed workflow has not been confirmed. There is no AI suggestions feature. .md, Google Docs, and Scrivener imports, plus .docx, .epub, .pdf, and KDP-ready exports, are not currently available.