The Difference Between Noveletta and a Wiki

Both are knowledge bases; Wikis consist of documents while Noveletta is a graph, here's the difference and impact of that distinction

Ahoy. Before we get into my nerd speak of node counts and chapter stamps, let's discuss why 'knowledge' is no trivial thing to cement.

[citation needed] is the internet's most polite way of saying prove it. Two square brackets, one raised eyebrow, "interesting, what's the source?", no hard feelings. It is also, entirely by accident, the best short summary of what happens when you ask a wiki to be a story's memory. Not because wiki editors do not cite. They cite beautifully. It is because a citation is something a human being has to remember to add.

The official Wandering Inn wiki's page for Erin Solstice, the main character, carries 272 citations for its ten volumes of story, 15 Million words, and all footnoted by hand, by people doing it for love, at 2am, for free. That's superfan love, it's the beauty of internet if you ask me!

Noveletta's Erin has 2,679 records from Volume 1 alone. Not because I am a better editor than 779 volunteers (I am profoundly not) but because in my graph data structure, a record cannot exist without a chapter attached to it. The citation is not added at the end. It is the column the whole thing hangs from. It's a fundamentally different infrastructure to storing knowledge than a wiki.

Two numbers. A whole architecture's worth of difference.

In praise of the humble wiki

First things first, I LOVE WIKIS! I think what Wikipedia has done is one of the most utopian technologies created this century. Wikipedia is, without exaggeration, one of the most inspiring things that has ever been put on the internet: crowd-run, ad-free, and stubbornly non-commercial for decades in a culture that monetized the word "friend." I cherish wikis, I cherish crowd contribution, I cherish open source. It is amazing what the wiki framework has done for the world's knowledge but that doesn't mean it's a perfect tool for all knowledge.

The Wandering Inn's official wiki is 5,858 articles and 124,461 edits from 779 registered accounts. Nine years of volunteer labor by estimates. Nine of those accounts are active right now as of me writing this. Nine people keeping the lights on in a library the size of a small town, and doing it well enough that I could measure my own work against theirs quantitatively which says a ton about its quality as well.

What I am less fond of is what tends to happen next — when a fandom's labor of love gets wrapped in three autoplay ads for bathroom tile, and quietly re-pointed at ad buys instead of at readers or at the author who wrote the thing in the first place. That is not a wiki problem. That is a landlord problem.

But even a perfect wiki — ad-free, lovingly tended, staffed by saints — runs into the same limitation and ceilings, and it is not a people problem. It is a data structure problem.

A wiki is a collaborative static document editor. That is the whole technology. It is a shared text file with an excellent haircut and a version history, and for the world's knowledge — where the unit genuinely is an article about a thing — it is perfect. For a living story, where the unit is a thing that changes as you unravel it chapter by chapter, it is the wrong shape. Documents have no chronology or temporal awareness of the reader. Their pages are, by design, static to a point in time and for stories that often means the end and I'm not trying to learn Darth Vader is Luke's father in Episode IV.

Wikis are ingenious but they are the wrong data structure for stories.

Flip between the two. Nothing about the story changed — only the shape it is stored in.

Encyclopedia Galactica Lite

What if instead of a grand compendium to preserve all knowledge of the Galactic Empire on the remote planet Terminus I could just read my book and look up characters without spoiling them? Isaac Asimov's Encyclopedia Galactica is a fun inscription for wikis and Noveletta alike ignore the [REDACTED SPOILER]. What would it take to not just catalog knowledge but make it usable? Well that's what Noveletta set out to do with a knowledge graph architecture tailored to how stories are written, chapter by chapter.

A knowledge graph is a data structure that defines data and its relationships: Nodes and Edges to be technical. Nodes are the things — a person, a city, an inn, a class, a skill, a species. Edges are how they touch — who said what, who was where, what changed, what became true. Then the part that makes it a Noveletta graph rather than a whiteboard of crazy strings: every single edge carries the chapter it came from, #ledgerized.

Read that bottom row out loud and you have read a database query. Two nodes, one verb, one timestamp and that is the entire trick... just repeated 15,680 times.

Let's ground what this actually looks like for the Wandering Inn:

Volume 1 is 64 chapters and 439,749 words — roughly 3% of the series. Here is what came out of that 3%:

Broken out: 177 characters, 111 classes, 89 locations, 71 concepts, 53 skills, 49 groups, 49 creatures, 37 spells, 31 items, 29 species. Plus 2,466 appearance records, 239 chapter events, 111 typed relations, and about 255,000 words of derived content — summaries, fact prose, and explanations of what changed and why.

None of those are pages. Not one. They are rows, and every row knows where it came from so when we compose a page for Erin it knits all the needed rows together up to the chapter you've read and thus it's forced to be spoiler safe.

Eight nodes out of 696. Every line is a row in a table, not a hyperlink someone remembered to type.

Spoilers are the Enemy, not today Iago!

Humble boring brag but I'm very proud that the system fundamentally blocks spoilers, it's a really neat and challenging data problem to solve! Yay, go me!

All 14,873 fact, quote, state-change, appearance, and event records in Volume 1 carry a chapter index. Every view in the product can therefore be cut off at wherever you are in the series. That's not something a document based wiki can do. Not even the metadata on the page links can contain spoilers! Opening that page as a Volume 1 reader is not a spoiler risk. It is the whole series at once, with a table of contents.

To be scrupulously fair: a wiki can do spoiler tags to blur sensitive content, and some do. But it is a courtesy — applied by hand, sentence by sentence. In a graph, the chapter is a control. It cannot be forgotten, because nothing can be written down without it.

Drag the chapter. The knowledge base forgets on command — which is a thing only a database can do.

Show your work

Density is the honest way to compare a three-percent slice against nine years of accumulated effort, so: per million words of source text, Noveletta produces about 1,580 entities and 310 words of derived prose. The official wiki averages about 420 articles and 140 words per million.

Or the blunt version: 177 characters catalogued from Volume 1 alone, against 1,897 character pages for the whole ten-volume series.

The fair head-to-head is Volume 1 against the wikis' Volume 1 sections, since their pages cover everything:

Even measured against their whole-series pages, Volume 1 alone reaches about 46% of the official page's word count — from 3% of the story.

Extrapolate to all fourteen million words of the Wandering Inn and the napkin math says roughly 11,000–22,000 entities, 260,000 quotes, 90,000 structured facts, and about 4.4 million words of derived prose — all in structured, spoiler-safe form. This is not a brag about outpacing volunteers because again the wiki is an entirely different structure and for its purpose doesn't demand the depth that Noveletta's features do. My hope would be that those amazing volunteers would find a home and feel empowered bringing that labor of love to Noveletta some day and I plan to continue to design features that make the immersion of contributing to a wiki that much more valuable in Noveletta.

What a wiki page cannot do

This is where the magic happens, not in the raw data or how much more text a graph can structure but what can it really do. Unlike wikis, this data is USABLE! I am actively extending it into new features and even new products in ways a wiki can't reach.

Behind the scenes, I'm spinning an unforeseen future of the dream operating suite for authors with this as its backbone. A retinue of new tools that can not exist without this core; all of them lenses on the same ledger, none of them possible without it. Ignore my silly names for them, they are my internal codenames... for now hehe.

Is this the future? IDK yet but let's find out together

I told you I started this for my mom, obsessed with The Wandering Inn, drowning happily in a cast she could not quite hold onto. That is still true, but in meeting authors and seeing this come to life I am seeing the bigger impact it will have on the authors and their worlds I cherish.

If you write long-form fiction, I'm begging, pleading, on my knees that you give me a shot. I'm trying to learn as much as I can about what authors are struggling with and I believe fully in this technology at its core to unlock unforeseen solutions but I need real people, writing real books, to give me feedback and try something new together.

So here is the offer, plainly: bring me your serial and I will add it: every character, every named place, every promise you made in chapter 12 and have to keep in chapter 400 — and your readers get a knowledge base that never spoils anyone. We can review it together, brainstorm crazy new ideas together, and build things literature never dreamed of. and no matter what you keep your story. You always keep the story.

Oh and I'm doing this for free, I have too much to learn to try to monetize this right now but I can promise you one thing, IT WILL NOT BE ADVERTISING! I'll write more on this if you want to follow the journey but even if it means moving slow I am not fundraising, I am building this with spare time and a meager hope that this could become a fulltime job one day because I love reading, I love writing, I love the world of fiction and literature and it would be my dream to live it in this way combining my skills and passion. So please, come one, come all, come afraid, come curious, I need input and I need authors.

Noveletta · a spoiler-safe knowledge base for web serials · built solo, on open seas.