Beta onboarding
Reader and author paths for the closed beta.
The goal is not just to click around. The goal is to prove that a reader can discover, read, and signal fiction without confusion, and that an author can publish, revise, organise canon, and export a series without losing trust.
Before you start
Closed beta access is invite-only and currently 18+ only.
Sign-in requires acknowledgement of the beta terms, privacy notice, and content policy.
Keep your own copy of important writing even though LoreBranch exports are already live.
Payments should be treated as disabled unless the beta owner explicitly says otherwise.
Reader path
Verify the reading proposition first.
- 01Open /browse and pick a public series that already has a published chapter.
- 02Read the chapter prose-first before touching the diff or signal tools.
- 03Open the published history or version log only when you want the release context.
- 04Select an exact block and place signals once you have enough reading progress.
- 05Follow the author or series if you want it to show up in your feed and library surfaces.
- 06Use the floating beta feedback route or support route to report friction, confusion, or trust concerns.
Author path
Verify the author workspace chain.
- 01Open the author base and create a short test series if you do not already have one.
- 02Publish a first chapter so you can verify the public reading path, version log, and diff flow.
- 03Open the chapter editor, save a draft, commit a change, and preview the publish diff.
- 04Add one Decision Log entry, one Canon Engine entry, and one Timeline node so the private workspace chain is exercised.
- 05Download the per-series canon export from the private author base to confirm portability.
- 06Use support for account/privacy/safety issues and beta feedback for product/UX issues.
What we want beta users to notice
Anything that makes you unsure who can see a draft, suggestion, or signal.
Confusing editor or reader terminology, especially around blocks, versions, and signals.
Places where LoreBranch feels slower or heavier than your normal writing or reading workflow.
Any mismatch between public-facing copy and what the app actually lets you do.