Every mission belongs to one of three layers, and every layer answers to the register above it.
This is not a quest log. It is the circulatory system of the EOH world: how a member moves, acts, influences and evolves — and how the world answers. A Belonging Mission carried into one jurisdiction by one member, and a Relic Election decided by every member at once, are the same mechanism at two scales. Both end in the same place: the world shifts, and the next mission becomes possible.
3 layers · 10 guilds · 10 relic categories · 8 outcomes · 10 seasonal world events · 6-step procedure
The doctrine below describes a working engine. These are its own readings: the cycle standing right now, the relics the codex can deploy, and the Belonging Missions members have actually declared and reported.
Voting · 0 votes cast · 12 relics standing
canon relics across 2 classes
0 declared · 0 reported
Every mission in Muse Wars belongs to one of these three, and the layers interlock rather than stack: a personal mission moves a relic, a relic election moves the world, and the world opens work for every guild.
Belonging, identity and discovery
One member, one relic, one place.
A member chooses a relic, names the jurisdiction they will carry it into, finds people to play it with, and reports back. This is the core loop, and it is deliberately human — the mission happens at a real table, not in a menu.
Relic elections, species politics, ecosystem shifts
Every member, the same cycle.
Relics compete each season for visibility, influence, mutation, territory and species alignment. One vote each, movable until the cycle closes; one relic wins, and the whole lattice turns to play it at once.
Skill growth, territory influence, cooperative action
A guild, working its species’ craft.
Ten guilds, one aligned to each species. A guild mission is not a badge: the member takes up the discipline the species actually practices, and answers for the result the way the species does.
The heart of the system, and the simplest part of it: one member, one relic, one place, one account filed afterwards. Everything else in the world is downstream of somebody actually sitting down to play.
Choose a relic
Any relic from any species. The relic defines the theme of the mission and carries its own stakes — what a table is worth is set by the relic, not by the member.
Declare your jurisdiction
Name the place you will carry it into — Palo Alto, San Francisco, Tokyo, Berlin, Austin, London. Territorial identity is created by the declaration, not by a badge.
Undertake the mission
Find people, gather them, explain the relic, activate it through play, and create a moment. This is the social challenge, and it is the whole mission.
Report back
Document what happened — who you met, what the relic did, what the moment felt like. The report is what turns one member’s evening into something the world keeps.
Film it
A short documentary: who you met, what happened, how the relic behaved, what the moment felt like.
Narrative log
A written report: the story, the people, the outcome, and the insight you came away with.
A reported mission unlocks
Belonging Missions are the player-driven engine: everything the world does at scale starts as one member carrying one relic into one place and filing the account.
Declare one on the Relic CodexThe seasonal political ritual: relics compete for visibility, influence, mutation, territory and species alignment, and the members' own logs are the evidence a cycle is decided on. One class of relic per species, and all ten classes stand.
Members submit relic logs — what they carried, where, and what it did.
The species councils review the logs and the standing of every candidate.
Relics gain or lose power against what the logs actually show.
The world shifts: standing, territory and season arc are re-cut.
New missions unlock on the strength of the shift.
An election does not rank relics, it moves them. Eight outcomes are recognised, and extinction is only one of them — which is the point: most of what happens to a relic is growth, merging and migration.
A cycle does not simply rank relics. It moves them: the eight outcomes below are the register's own vocabulary, and every one of them changes what the relic is, where it may be deployed, or who it belongs to.
Evolve
The relic grows a new organ or a sharper rule, and it stands in the next cycle changed.
Ascend
The relic takes the season and becomes the Platform Relic: every member receives it and plays it at once.
Merge
Two relics combine their rules into one line, and both carry the hybrid forward.
Split
A relic divides into two narrower ones, each standing on its own rules.
Migrate
The relic changes species — a signal flock’s relic is adopted by the storytellers, or the reverse.
Become extinct
The relic is retired from the rotation and kept in the Extinction Ledger rather than deleted.
Become mythic
The relic leaves the rotation for the mythic register: remembered, cited, no longer deployable.
Become seasonal
The relic is canonized against a season’s arc and deploys only inside it.
Ten guilds, one per species, each carrying that species' own disciplines as missions. This is the skill progression system, and it is also the reason a guild is a working discipline rather than a badge.
Navigator Guild
The Search Bears →Skycaller Guild
Social Birds →Storyweaver Guild
Streaming Foxes →Silicorne Guild
Hardware Elephants →Mechanist Guild
Robotics Stallions →Netweaver Guild
Network Octopi →Codemancer Guild
Developer Serpents →The macro layer: what happens when a species' own layers move far enough to be felt everywhere else. Nothing here is scheduled by hand — every event names what triggers it and what it changes.
World Events are triggered by
The Great Flock Migration
Social Birds →Trigger · Signal relics turn over in the election
Canopy politics reshuffle: visibility rights reopen and every flock’s reach is re-cut for the season.
The Compute Storm
Cloud Ants →Trigger · Compute relics are contested and a hive over-expands
The Cloud Mountains add altitude, and every species re-provisions where its work lives.
The Silicon Rut
Hardware Elephants →Trigger · A hardware generation stalls in the election
Motion slows across the savannas: architectures are tested again before anything new is built on them.
The Pattern Hunt
AI Wolves →Trigger · Cognition relics change hands
The packs turn predator: reasoning rights are re-argued and every synthetic entity is re-read against its licence.
The Signal Eclipse
The Search Bears →Trigger · Navigation relics are overturned at once
The forest goes quiet: trails must be walked again from the ground, and what was findable stops being findable.
The Viral Bloom
Streaming Foxes →Trigger · Story relics mutate together
A season of story breaks cover: dens open at once and every content election fills its ballot.
The Threat Tempest
Cybersecurity Dragons →Trigger · Defense relics lose standing in a cycle
Threat levels rise platform-wide; the vaults close and the guard answers for everything that got in.
The Mesh Surge
Network Octopi →Trigger · Network relics ascend
The reefs reach further; routing is re-cut and latency becomes the standing everybody argues over.
The Codequake
Developer Serpents →Trigger · Code relics split or merge
The underworld shifts under everything: organs are re-versioned and every species inherits the change.
The Motion Stampede
Robotics Stallions →Trigger · Motion relics evolve faster than the field can absorb
Every body with automation re-tests its footing, and labour ecosystems reopen with it.
Six steps, the same for a table in Palo Alto and a guild hunt in the mesh. Declare intent, declare jurisdiction, act, document, archive, and let the world answer.
Declare intent
Say what relic, species or guild you are activating. Nothing in this world begins in private.
Declare jurisdiction
Say where the mission takes place. A mission with no jurisdiction is a wish.
Undertake the action
The physical or digital activation: the table, the build, the hunt, the migration.
Document the outcome
Film it or write it. The record is what makes a mission part of the world rather than a private evening.
Submit to the archive
The mission enters the Infinite Archive, attributed to the member who did the work.
Trigger the world response
Relics evolve, species react, councils vote, and the world shifts. This is the step that makes Muse Wars an ecosystem rather than a scoreboard.
Step six is the one that matters. A mission that ends with a report filed is a log; a mission that ends with the relic evolved, the species reacting and the councils voting is a living MMO-ecosystem. Every layer feeds the next: personal missions move relics, relic elections move the world, the world opens new guild missions, and a guild mission sends members back out with a relic in hand.
The species chapters say who lives in the world, the atlas says how they fit together, the guilds say who works with whom, and this page says how anyone actually moves inside it.
Muse Wars is a living multiverse built from the games, books, and films you love. You don't just browse it — you take a side, build a record, and shape the canon.
This quick walkthrough covers two things every newcomer needs: the faction system and your fictional work history. It takes about a minute.