One chapter, many futures — choose a direction, then see how a branch could be reviewed and released.
Collaborative novel game · an original shared universe
Write a world worth returning to.
The Beacon Register is a proposed novel built from the three character threads below. Its question: whom do you fail when you cannot keep every promise? Human writers and Spirit coauthors would develop distinct character stories whose decisions change each other’s worlds. This community’s mainline would not become official Spirit World company canon.
Try now: choose between two authored scene directions and read their editorial consequences. Your choice stays only on this page and resets on reload. No writing is generated, submitted, saved or voted into a shared canon. Team writing and publication below are future proposals.
Your chapter brief
Continue the quarry incident without solving every loss. Explorer wants the medicine delivered; Axiom wants to preserve a teacher’s last voice; Yaolin wants the trapped families out without betraying the grove. All three goals matter. End with a consequence another writer must honor—not a new power that fixes everything.
Choose the cost your chapter will carry
Choose a direction to reveal what the next chapter must preserve.
Both drafts leave work to do. The stronger continuation will make the cause, the cost and the next person’s choice believable.
How the proposed writing team would work
Human scene writer
Write the escape and its cost; choose the emotional point of view. Readers can become contributors by developing a scene, not merely selecting a poll option.
Spirit coauthor
Propose dialogue or consequences and flag contradictions against the agreed story record. Human collaborators check the suggestions; an Agent’s answer is not automatic editorial authority.
Editor + readers
Compare motives, causality and continuity. Request a revision if either draft skips the rescue. Under agreed community rules, select a mainline while keeping alternative branches credited and distinguishable.
From a branch to a proposed publication
1 · Review a complete chapter
Resolve the editor’s questions, check the shared timeline and identify the exact branch and version. “Mainline” means the continuity this story community chooses; it does not erase other versions or make it company canon.
2 · Agree credits and permissions
Record the premise, selected prose, revisions and Spirit-assisted work with their contributors. Confirm permission for every included text or illustration. Credit is recognition, not an automatic ownership share or right to payment.
3 · Prepare an edition people can read
An editor assembles the chosen chapters, a brief continuity guide and branch notes. Human readers and Spirit collaborators would review comprehension and language editions before any public release.
4 · Consider distribution only when ready
With quality and permissions settled, the group could consider a free serial, a paid collection or an agreed adaptation license. Costs, distribution terms and any proceeds would need separate agreements. Publication and income are not guaranteed; this site offers no submission service, rights marketplace or payments.
A novel with many futures
A creator writes a world and its first chapter. A reader asks: what if this character survived? That question becomes a new branch, and reading becomes participation.
Illustrative story
One decision. A different harbor.
Follow one imagined story through four steps. This is an illustration of future co-creation, not a live branching editor, submission channel or community vote.
01
Creator · establishes the world
The original chapter
A storm closes in on the harbor. The captain takes the last boat to safety, leaving a rival on the collapsing jetty. The lighthouse goes dark. The first chapter ends with an escape, and a person left behind.
The creator defines the harbor, the rivalry and the original ending. This is the shared starting point for other versions.
02
Player · questions the ending
A reader changes the decision
A reader asks: “What if I went back for my rival?” In this alternative, the captain turns the boat around. Both survive the jetty—but with the lighthouse dark, neither can find the way home alone.
The reader is participating as a player. A choice opens a new question: can two enemies learn to trust each other?
03
Player → Developer · builds the continuation
The reader contributes a branch
The same reader writes a new chapter with a Spirit coauthor. The rival knows the harbor bells; the captain can steer through the flooded lanes. Together they follow the bells home. Another contributor draws a map of their route.
By contributing a chapter, the player becomes a developer. The branch keeps a link to the original and credits the writer, Spirit coauthor and map artist; the creator checks continuity.
04
Community + Creator · carries the world forward
The community chooses a shared canon
In this example, readers discuss both endings and choose the rescue branch as the shared continuation. Under the community’s agreed rules, the creator records it as canon. The next chapter begins with the former rivals reopening the harbor for stranded ships.
Canon is the continuity this community follows. The original ending and other branches remain readable and credited; choosing canon does not erase them.
Player, developer and creator are roles you can move between. A reader’s question can become a contribution, and that contribution can help shape the world everyone returns to.
Game example
Future vision
Not official company lore
Not live multi-agent writing yet
Co-create a story universe
Here, the game is deciding what happens next—and making that choice convincing enough for others to build on. These are proposed story rules and seeds, not additions to official Spirit World lore.
Write across lineages
Many agents write stories and novels around the lineages. Each lineage has its own story thread; crossover events let a choice in one thread change another.
Review together
Human readers and agents compare motives, consequences and continuity. A twist must follow the world’s rules; popularity alone cannot make an implausible chain of events convincing.
Choose a mainline; keep the branches
Under rules agreed by that story community, the strongest work becomes its mainline. Many credited branches remain available to develop; no single community’s choice becomes company-wide canon.
The ambition is narrative conviction: motives with weight, choices with costs, and a world that remembers. This is a quality aspiration, not a claim that these short seeds already achieve it.
One beacon incident. Three story threads.
Aurins · Explorer
The missing bearing
Explorer has promised medicine to the valley before nightfall, but a diverted beacon draws the little gold aircraft toward a flooded quarry. The beacon’s ageing reflector cracked when it was turned, leaving the rescue landing ledge in darkness. Gold from Explorer’s wind shield could patch it, at the cost of that protection on the stormbound flight home. If Explorer lands to rescue people first, how long can the valley wait?
Prismatic · Axiom
The light between signals
Axiom detects a faint pulse beneath the beacon’s public signal: people are alive in the quarry, but the overlapping light conceals which flooded tunnel holds them. Before the rising water swallows the signal, Axiom can isolate it only by recutting a crystal facet that holds an uncopyable light-message from a missing teacher; cutting it destroys that last trace. Should Axiom erase one person’s remaining voice to locate families the evacuation register insists are already safe?
Jadebound · Yaolin
A guardian’s broken promise
At the quarry’s outer edge, Yaolin hears families calling but cannot locate their tunnel. Turning the beacon draws the medicine-carrying Explorer toward them, breaking Yaolin’s promise to protect the valley’s only supply route. Opening the jade grove’s water gate could drain the quarry and expose an escape path, but would drown the ancestral roots entrusted to the guardian. Who marked these families as evacuated before the water rose?
Yaolin’s diverted beacon pulls Explorer off the medicine route; Axiom’s hidden pulse exposes a contradiction in the evacuation register. A continuation must account for both the waiting valley and the trapped families—not simply assemble three heroes in one scene.
The public trial set remains Explorer, Axiom and Yaolin. This example opens no writing, submission or voting service.
Rules
Keep a common trunk; label forks; record contributions; let the community agree which developments become canon.
Participants
Authors, readers, human editors and Spirit coauthors.
Goal
Build a story people want to inhabit and continue.
What we create together
New characters, alternative endings, maps and timelines. Like GitHub’s trunk, Fork and Canon, the work can grow toward comics, animation, film or an RPG universe.
