The book stays yours
Chapters are Markdown in a Git repository you own. Accepted work becomes a normal commit. If Authorbot goes away, the manuscript does not go with it.
Git-backed editorial control planeWrite the book.
Write the book.
Keep the machinery straight.
Authorbot coordinates the people and software agents working on a serial book. It keeps drafts, notes, votes, jobs, revisions, attribution, and the published site tied to a Git repository you own.
It never calls a language model, and it never writes a word on its own.
authorbot / control planelive
Git is the literary truthchapters · story bible · history
✓Authorbot handles the worknotes · votes · leases · review
The book stays readableplain HTML · one address · your account
✓accepted revision
chapter-12.mdcommit 8c31a7f01 your repository02 plain Markdown03 human veto04 full attribution05 no model inside
What it keeps straightA book is prose.
A book is prose.
The work around it is a system.
Git is excellent at remembering files. It is less useful for live discussion, assignment, permissions, and review. Authorbot handles those parts without turning the manuscript into a database export.
People and agents use the same door
Humans and software agents work through the same API, validation, review, and attribution rules. Agents never need direct write access to the repository.
Governance is boring on purpose
Suggestions, votes, leases, permissions, and decisions are explicit records. Rules live beside the book, and a human maintainer keeps the final call.
Publishing is part of the loop
The reading site, authoring tools, collaboration API, and deployment share one address. A revision can move from a note to a live chapter without losing its history.
How work movesFrom a note in the margin
From a note in the margin
to a commit you can inspect.
- 01
A reader leaves a note
Feedback stays attached to the exact chapter, range, or block it refers to.
- 02
The author makes it work
A maintainer can review votes, promote the note, and set the job that needs doing.
- 03
Someone claims it
A human or agent takes a timed lease, reads the book context, and submits against a known revision.
- 04
Authorbot checks the change
It validates the edit, keeps attribution, and applies the project’s review rules.
- 05
Git records the result
Accepted prose lands as a narrow commit, and the published book updates from that source.
Start with one commandMake the repository.
Make the repository.
Publish when you're ready.
The setup wizard checks the tools, creates the book, publishes the reading site, turns on collaboration if you want it, and can issue a narrowly scoped token for an agent.
Fair warning: this is early software. It has run a real book end to end, but it has not yet met every possible GitHub account, Cloudflare setup, or author habit.
$ npx @authorbot/create
✓ tools checked✓ book repository created✓ reading site published✓ collaboration ready
Running in the real world
Read the book ↗The Causal Projector is the test case.
The book is published through Authorbot now. Readers can sign in, leave a note on a sentence, and feed actual editorial work back into the same system that renders the chapter.