Telling Forward
"A quiet place for stories to grow."
Telling Forward is a voice-first, agent-assisted platform for open-canon collaborative fiction: an originating author opens a storyworld, other people extend it through distinct, attributed paths, and readers can follow the resulting lineage without ever mistaking a community branch for the author's canon. GitHub holds the manuscript, the review history, and the provenance record. A custom app is being built so that none of it feels like GitHub.
Open canon, not open chaos
The working proposition is simple to state and hard to build: authorship can stay accessible without becoming anonymous, and collaboration can stay open without leaving ownership unclear. Most "everyone can contribute" systems solve this by flattening every voice into one undifferentiated pile. Telling Forward keeps a storyworld legible instead, so a reader can always tell what's canon, what's a branch, and who wrote which.
The seed and the canon
An originating author's story and protected canon stay clearly marked as theirs, even as the world grows around them.
Branches and alternate continuities
Community paths can extend a world in new directions without ever being confused for its official line.
A governed canon
Contributions enter canon by an explicit steward decision, not by popularity, volume, or who showed up first.
A provenance record
Every accepted contribution keeps its source, its contributor, and its review history attached, permanently.
GitHub stays backstage
Telling Forward runs on real Git mechanics: a storyworld is a repository, a contribution is a pull request, canon is what's merged. But the person telling the story is never asked to know that. The founder has said plainly that he only recently learned what a pull request actually was, and the target contributor is expected to know even less. So the platform keeps one vocabulary backstage and shows a different one to everyone writing.
| Backstage (GitHub) | What a contributor sees |
|---|---|
| Repository | The storyworld |
| Branch | Your story path |
| Commit | Saved moment |
| Pull request | Submit your scene |
| Merge | Accepted into canon |
| Issue or comment | Story note or editor feedback |
A submission moves through six real states on its way to canon, and the app is expected to surface all six rather than a simplified summary:
The rules the platform runs on
Start with the person, not the prose.
A contribution may begin as speech, memory, an outline, or just a question: never a required blank page.
Assist without taking authorship.
Agents may transform, organize, and flag a contribution. Contributors approve what actually represents their intent.
Keep provenance visible.
Every accepted contribution retains its source, its contributor credit, and its review history, in full.
Separate canon from possibility.
An alternate path can be worth reading without being the originating author's canon. The interface has to make that difference obvious.
Give every world a steward.
Each shared world needs one identified person responsible for its permissions, its canon policy, and its moderation.
Earn the right to monetize.
Prove people actually want to read and contribute before any paid access, virtual credits, or adaptation economics enter the picture.
Trust and momentum first, monetization last
Every stage after the first is explicitly gated on the one before it earning its keep. Nothing here jumps ahead to a business model before there's a storyworld worth protecting.
-
▶
Invite a Small Set of Authors Active
A small set of authors open bounded portions of original worlds. The GitHub-native fast path, the storyworld repository shape, and the manuscript-ingestion pipeline are being built against this stage right now.
-
○
Readers Explore, Contributors Extend Planned
Readers explore paths and approved contributors extend them, through the frontstage vocabulary above rather than raw GitHub mechanics.
-
○
Attribution, Permissions, Lineage Planned
Attribution, permissions, lineage, and canon decisions get recorded from the beginning, not retrofitted once a world has grown large enough to need them.
-
○
Test Whether People Return Planned
The only metric that matters at this stage: do people come back to read, come back to contribute, and bring others with them.
-
○
Commercial Adaptation, Only If Earned Planned
Only after a real storyworld earns real attention does the project explore contributor rewards, platform fees, or adaptation deals. Even then, participation alone wouldn't automatically buy a branch a seat in any commercial package.
Terms like open canon, world steward, story lineage, and support credits describe ideas the project is actively working through, not features or promises that exist today.
Why not "Forge"?
The name came out of a voice thread before the repository had one. Forge was the obvious first candidate, since it's the house metaphor at OverKill Hill, and it was ruled out fast, for two reasons: it echoes "forgery," and it had already been spent across other OKHP³ projects, so it no longer distinguished anything.
What followed was a real search through word families the founder was drawn to: Narrative, Authors, Communal, Momentum, Inertia, Continuum, Flywheel, Improvisational. Some were already crowded elsewhere (Narrative Momentum, Story Flywheel). Some were usable but too broad (Narrative Commons, The Living Canon). What survived was a working conceptual label, open-canon collaborative fiction, and a name to carry it: Telling Forward.
The same thread is where the frontstage/backstage vocabulary above actually came from. It wasn't a design exercise; it was a founder admitting, mid-conversation, that he'd only just learned what a pull request was, and reasoning from there that whoever this was built for would know less. GitHub stays the engine. It was never going to be the language.