City Pixels began with a discovery problem.
How can readers find writers they do not already know?
The map, Story Trails, bookshelves, reader follows, Beyond the Map, Ask Readers, and Authorized Worlds all approach that problem from different directions.
The next major opportunity may be deeper:
help the author manage the fictional world behind the stories.
That is where the planned NovelOps integration comes in.
The first premium concept: an automatic author wiki
The initial idea is not to ask artificial intelligence to write the novel.
It is to ask the system to read what the author has already written and help organize it.
Characters.
Locations.
Organizations.
Objects.
Relationships.
Events.
Terminology.
Timeline facts.
The platform could extract proposed wiki entries from the author's stories and books, then present those entries for approval.
The operating rule is simple:
NovelOps proposes. The author establishes canon.
Why this belongs inside City Pixels
City Pixels already knows how stories relate to authors, books, cities, Story Trails, and potentially shared fictional worlds.
A canon wiki adds another kind of relationship:
how the facts inside the work relate to one another.
That moves the platform from external discovery toward internal creative infrastructure.
The reader sees the story.
The author gets tools to understand and maintain the universe behind it.
The wiki should be author-controlled
Automatic extraction is useful only if the author remains in charge.
A system can misread sarcasm, rumors, unreliable narrators, dream sequences, alternate timelines, or deliberately false statements.
So extracted facts should begin as proposals.
The author can approve, edit, merge, defer, or reject them.
Approved entries become part of the author's canon knowledge base.
That is more trustworthy than an AI-generated encyclopedia pretending every sentence is true.
Source tracking makes the wiki valuable
The strongest version of the feature would not simply say:
"Character X was born in 1988."
It would say where that fact came from.
Story.
Chapter.
Revision.
That gives the author an answer to one of the most frustrating continuity questions:
Where did I establish that?
For writers managing series, that can save enormous amounts of rereading.
Contradictions can become useful warnings
Once approved canon facts exist, NovelOps can compare new writing against them.
One story says the school opened in 1974.
Another says 1976.
A character's eye color changes.
A relative's age no longer makes sense.
The system does not need authority to fix the contradiction.
It needs to surface it.
The author decides whether the new version is a mistake, a retcon, an intentional contradiction, or evidence that the earlier assumption was wrong.
Public and private knowledge can coexist
Not every canon fact should be visible to readers.
An author wiki could eventually separate public entries from private entries.
Readers might see character profiles, locations, and approved lore.
The author might privately store secrets, future reveals, hidden relationships, and timeline notes.
That creates a premium author tool and a potential reader feature from the same underlying data.
The bigger transformation
If City Pixels successfully adds NovelOps tools, the platform changes category.
It is no longer only:
"publish here and get discovered."
It becomes:
"publish, understand your audience, manage your canon, organize your world, and create discovery around the work."
That is closer to an author operating system.
The roadmap is intentionally focused
The first NovelOps integration does not need to include automated drafting, full novel generation, or every possible continuity tool.
The automatic wiki is powerful enough on its own.
Do one thing well:
turn an author's existing writing into an organized, author-approved canon knowledge base.
If that works, timelines, relationship maps, continuity checks, series bibles, recaps, and other professional tools can grow from the same foundation.
City Pixels began by asking where stories live.
NovelOps may help authors answer a different question:
What, exactly, lives inside them?
*Note: NovelOps integration is a planned premium direction, not a currently launched City Pixels feature.*