FAQ
Simple answers for readers and authors.
This page explains what LoreBranch is for, how reading works, how writing works, what feedback does, how payments work, who owns the work, what stays private, and why both sides might want to use it.
Why readers use it
Read the story and the changes around it.
- You can read public stories right away.
- You can see what changed between releases.
- You can react to exact lines instead of leaving loose comments.
- You can follow the stories and writers you want to keep up with.
Why authors use it
Keep the story, the changes, and the notes together.
- You can draft in private and publish when you are ready.
- You keep a clear history of what changed and why.
- You can hold story facts, timeline notes, and decision notes in one place.
- You can let trusted people help without losing control of the story.
Quick paths
Reader path
Browse a public story, open a chapter, read it normally, then check what changed if you want more context. Sign in later if you want to follow the story or leave notes on exact lines.
Author path
Write in private, save drafts as you go, publish when ready, then use reader notes, your story guide, your timeline, and your decision notes to keep the next version clear and consistent.
Start here
What is LoreBranch?
LoreBranch is a story site built for works that keep changing. Readers can read the live story, see what changed, and leave notes on exact parts. Authors can write, publish new versions, and keep their story details organised in one place.
Who is it for?
It is for both readers and authors. Readers get a closer view of how a story grows. Authors get a cleaner way to write, publish, and manage feedback without losing older versions.
Do I need an account to use it?
No for basic reading. You can browse public stories and read public chapters without signing in. You only need an account when you want to follow a story, follow a writer, or leave feedback tied to the text.
For readers
What can I do as a reader?
You can browse public fiction, open a chapter, read it like a normal story, and check what changed since the last release. If you sign in, you can also follow stories and writers, and leave feedback on exact lines.
What makes reading here different?
You are not only reading the latest version. You can also see how the story changed over time. That makes it easier to follow the author’s choices, spot growth, and understand where reader feedback mattered.
How does feedback work?
Feedback stays attached to the exact part of the chapter it is about. You can leave a quick reaction, point out confusion, flag a typo, or suggest a better line. That means the author sees the note in the right place instead of digging through a long comment thread.
Can I help shape a story?
Yes, if the author wants that. Some readers become trusted readers. Their notes and suggestions carry more weight because the author has chosen to hear from them more directly. The author still decides what gets changed.
For authors
What can I do as an author?
You can create a series, write chapters, save drafts, publish new releases, and keep every important change in view. You can also manage your story guide, your timeline, and your notes about why certain story choices were made.
What is The Canon Engine?
The Canon Engine is the private story guide for your series. It works like a wiki for your world. You can keep track of people, places, groups, objects, rules, and other facts, so you do not lose track of what is true in the story.
What is the Decision Log?
The Decision Log is where you write down big story calls. You can note what changed, why it changed, and what idea won. That makes it easier to remember past choices and explain them to collaborators later.
What is the Timeline?
The Timeline is a visual list of events in story order. It helps you see what happened first, what happened later, and where parts of the story connect. You can use it to keep timing clear and avoid story mistakes.
What stays private and what becomes public?
Your drafts and working tools stay private to the people you have allowed into that story workspace. Public readers only see published chapters and the public reading view. They do not see your draft area.
How do the story tools help?
They help you keep details straight. You can store people, places, groups, objects, rules, and other story facts in one guide. You can keep the order of events in a timeline. You can also keep a simple record of big decisions, so later changes still make sense.
Can other people work with me?
Yes. You can bring in other trusted people to help with the story. Some can help edit drafts, and some can help publish, depending on what access they have. The point is to make collaboration easier without turning the story into a mess.
Why would I use this instead of a normal writing tool?
Because LoreBranch keeps the writing, the story facts, the timeline, the release history, and the reader feedback connected. You do not have to spread your work across separate notes, files, and comment chains just to keep up.
Practical questions
Can I get my work back out later?
Yes. There are ways to download your account data and a full copy of a story workspace. That matters because your writing should not be trapped here.
Who can publish a story update?
Only the people with publishing access for that story. Not everyone who can view or edit drafts can push a release live.
How do payments work?
When payments are turned on, LoreBranch uses Stripe to run checkout and payouts. Readers can support a series with a monthly payment or make a one-off payment. The money moves through Stripe rather than LoreBranch trying to process cards itself.
How much does LoreBranch take from payments?
LoreBranch keeps 10% of monthly support payments and 10% of one-off support payments. The rest is sent on to the writer through Stripe when payouts are set up.
Who owns the copyright to work on LoreBranch?
Writers keep ownership of their stories and other work. LoreBranch only gets the rights it needs to host the work, show it on the site, back it up, and run the service.
What if someone uploads work they do not own?
They should not do that. People should only post work they own or have permission to use. If there is a copyright complaint or another serious rights issue, LoreBranch may hide or remove the work while dealing with it.
What is the Slop Section?
It is a planned area for AI writing. The idea is simple: AI writing is already here, more people are using it, and some people want help expressing ideas because traditional writing is hard for them. A separate Slop Section gives that work a place to exist openly instead of being mixed into the main writing section.
Why have a separate area for AI writing?
Because it sets clearer expectations for readers and writers. People who want human-written work can stay in the main writing section. People who want to publish AI-assisted or AI-generated work would have a separate place to do that without pretending it is something else.
What if I need help or something feels wrong?
There is a support path for bugs, privacy questions, and safety concerns. If something needs attention, you are meant to have a real contact route instead of guessing where to report it.
Is LoreBranch finished?
No. It is still in beta. The core reading and writing flow is live, but the product is still being shaped. That is part of why this FAQ exists: the goal is to be clear, not pretend everything is final.