The biggest fear behind creator-approved fan fiction is usually not the fan fiction itself.
It is loss of control.
If writers are invited into the world, will readers confuse their stories with canon?
Will fan-created characters start dictating what the original creator can do?
Will approval be treated like ownership?
Will rules drift over time?
City Pixels designed Authorized Worlds around the opposite principle:
Open the sandbox. Keep canon yours.
Authorization has a defined meaning
Inside an Authorized World, approval means the fan writer has permission to create within the published rules.
It does not mean the project is official continuity.
It does not mean the creator has endorsed every creative choice.
It does not give the fan writer ownership of the underlying world.
And it does not give the world owner automatic ownership of the fan writer's original character or prose.
Those distinctions are the foundation.
Without them, "authorized" can become dangerously vague.
Non-canon is permanent by default
Authorized fan projects are clearly non-canon.
Popularity does not change that.
Featuring does not change that.
Time does not change that.
A million reads would not change that.
If a rights holder later wants to bring an idea or character into official continuity, that requires a separate real-world decision and, where appropriate, a separate agreement.
That protects the canon from accidental drift.
Rule versions preserve context
Creators also need the ability to change a fan program over time.
Maybe a protected character becomes available after a book release. Maybe a location has to be removed from fan use because it will become central to the next novel. Maybe content rules change.
The problem is that a new rule should not rewrite history.
Authorized Worlds preserve rule versions so the system can know what a fan writer accepted when a project was approved.
That creates a record of consent and expectation.
For a long-running creative community, that can prevent arguments that would otherwise depend on memory and screenshots.
Fan writers cannot casually absorb one another's creations
A shared world can create a second control problem: fan writers using other fan writers' characters.
City Pixels blocks that by default.
A writer cannot simply decide that another participant's original character appears in a fight, romance, cameo, death scene, quotation, or off-page event.
Each fan project remains its own non-canon continuity unless separate permission exists.
This keeps the world open while preventing a free-for-all around participant-created material.
The creator can protect future canon
A creator can also define forbidden or protected elements.
That matters for working authors.
The world may contain information the audience has not seen yet. A character may be reserved for a sequel. A location may hide a major reveal.
An Authorized World can open only the parts of the fictional property that are safe for participation.
The creator decides where the fence goes.
Controlled fandom can be more inviting than vague tolerance
Fans often do not know what a creator thinks about fan fiction.
Is it welcomed?
Ignored?
Resented?
Allowed only under certain conditions?
An Authorized World can answer those questions directly.
That clarity can make participation more comfortable for fans and creators alike.
Writers know the rules.
Readers know the work is non-canon.
The rights holder knows the program can be slowed, paused, or closed to new applications if management becomes too heavy.
Control and participation are not opposites
That may be the most important idea behind Authorized Worlds.
Creators are often presented with a false choice:
either control the fictional property tightly,
or invite community participation.
City Pixels is trying to build a middle path.
The creator keeps canon.
The fan writer keeps their original contribution.
The rules are explicit.
The boundaries are visible.
And the audience gets a structured place to participate.
That is not surrendering the story.
It is giving fandom somewhere to grow around it.