A worked exampleThe one example the programme specifies: a protagonist's profile, her relationships, her arc, the questions her bible still leaves open — and the field each line came from.
Free · No account needed · Nothing uploaded

The tool does not invent characters, so there is no generated example to browse. This is the free-tools plan's own worked output, written into the spec before the tool existed, and reproduced here as the document the tool produces — followed by the mapping from every line back to the field it came from.

Character: Mara Vale
Role: Protagonist
External goal: Discover who sent the letter written in her handwriting.
Internal conflict: Mara wants the truth but fears reopening the family secret.
Core fear: That the truth will prove she abandoned her brother.

Important relationships:
- Elias Vale — missing brother; source of Mara's guilt.
- Dr. Imani Reed — trusted friend who challenges Mara's assumptions.

Character arc:
Mara begins by hiding evidence from everyone. She gradually learns
that protecting the family story has prevented her from understanding it.

Continuity questions:
1. What does Mara already know about the handwriting?
2. Why has she avoided the orchard for ten years?
3. What would make her trust Elias's message?

Collaborator note:
Protect Mara's hesitation and guilt. Do not resolve the mystery
in the next scene.

The plan's worked example, as the tool compiles it

Which field each line of the example came from
Line in the exampleField it came from
External goalExternal goal (want)
Internal conflictInternal struggle
Core fearCore fear
Important relationshipsRelationship entries
Character arcArc — starting state, turning point, ending state
Continuity questionsOpen questions
Collaborator noteProtected canon (do not change)

Everything above is a field you fill in. The goal, the fear and the misbelief are Quick and Standard fields; the relationships are one bidirectional row each, so they appear on Mara's profile and on Elias's without being entered twice; the arc is three fields and a sentence; the questions are generated from what is still unanswered and kept on the profile; and the collaborator note is a protected canon fact, which is why it sits at the top of the compiled bible.

FAQ

Why does the bible come before the invitation?
A collaborator can only contribute well when they know the characters, the relationships, the world's rules and the continuity you want protected. That context is the thing this tool makes, and it is the thing you can hand over without handing over the book.
Why is the bible safe to share?
The bible is the safe artifact. It says who these people are and what must not change, and it says nothing about how the story ends, so sharing it does not mean showing anyone your draft.
How do I invite the role I actually need?
A co-writer needs the cast and the rules. An editor needs the arc and the open questions. A beta reader needs the one-page brief. Because the bible separates those, each of them can be given the right half.
Why review a response against the same ground?
When two people work from the same protected canon, a disagreement is about the story rather than about which version of the character they each remember.
What do I get on Nexet that this tool cannot do?
The tool builds the context; Nexet is where a story is written against it. A Nexet project holds your scenes and your bible together: draft in the Manuscript Studio, keep the characters, world, plots and outline in the same project, and let the cast and the do-not-change canon stay visible while you write. It also keeps a revision of every scene, and it tracks the plot threads and the outline. The finished work exports as Word, PDF, EPUB, Markdown, Final Draft and more.
Can I invite a co-writer or an editor to work from my bible?
Yes, and that is what the bible is for. On Nexet you invite someone as a role, whether co-writer, editor or beta reader, and they work from the same approved context rather than from a copy that drifts. Each role is given the part of the context its job needs, and a private thread keeps the conversation with the work instead of in an email.
What is the Writers' Audition Arena?
It is where you find someone to write with. You publish a frozen seed: a passage from your own work, held at that exact version. Other writers answer it with continuations, and you read them and choose. Your manuscript is never handed over by publishing a seed: what they see is the seed, and the writer you pick works on from there.
How do I get this bible into a Nexet project?
Export the JSON file, which is the round-trip format and the one that imports back without loss, then start the project on Nexet and bring it with you. Importing the file directly is coming; until it ships, the JSON export and the one-page brief are what travel, and the brief is what a collaborator reads first.
Does Nexet cost anything?
Nexet needs an account, and it starts free: you can create projects and write in them without paying, with more project slots available if you want them. Nothing on this page is affected either way: the free tool, its exports and its brief stay free, and they never ask for an account.

“You shouldn’t have to send your entire book to get useful feedback.”

  • The draft and the bible in one project. Draft a scene in the Manuscript Studio with the cast, the world and the canon beside it, so the reference sits where the writing happens instead of in another file.
  • Invite the role you actually need. Bring in a co-writer, an editor or a beta reader as a role. Each works from the same approved context, with a private thread for the conversation.
  • Never lose a version of a scene. Revisions keep a copy whenever a scene changes, so an edit is not a one-way door and a collaborator's answer can be read against what it answered.
  • Find a collaborator in the Arena. Publish a frozen seed of your own writing, read the continuations other writers send back, then work with the one that fits. Your manuscript stays private.
  • Take everything with you. Export the project or the finished document as Word, PDF, EPUB, Markdown, Final Draft, Rich Text, OpenDocument, plain text, HTML or JSON. Nothing is locked in.