Welcome to the Jamverse
A gentle orientation before you dive into the stories — not a substitute for them, just a way in.
The Jamverse is one shared universe, not four separate ones — four story cycles, four genres, different corners of the same evolving world. The map between them is real, if incomplete and still being drawn: each new story, including whatever you write for this contest, adds a piece, and the whole shape shifts a little every time. No single law binds every story, and nothing stops a future piece from exploring new ground entirely. But one thread runs through a lot of what's published so far, worth naming as a way in: something gets built to protect people, or make them safer, fairer, easier to administer — a protocol, an algorithm, a role, a piece of folklore calcified into law — and it works. That's the uncomfortable part. Many of these stories start exactly where a system's own legibility — the fact that its rules can be read, delegated, audited, invoked — turns into the gap somebody slips a whole life through.
The Stockton Chronicles
Nearest-future of the four — Bay Area, three to ten years out, most young people priced out of the inner city and running their lives through co-op housing, patchy Basic Income, and an influencer economy nobody quite discloses. Liquid Democracy lets you delegate your vote to someone you trust, who delegates it again, cascading upward to people you'll never meet (The Caucus). Caduceus runs a biotech campus so procedurally clean it can absorb a body going missing without a ripple (Caduceus City). And if your job is Maestro — a human choreographing a client's live personalized story while a crew of Agents handle the routine beats — the algorithm isn't coming for your job, it already has a desk next to yours (Joan Henry vs the Algorithm).
Trainverse
The same thread, run sideways and put on rails: the UET-1 is a train from Lisbon to Laos, a moving special economic zone under three absolute rules — it has to stay moving, ECOROUTE never stops reading everyone's bio-band, and the moment it stops, it belongs to whatever jurisdiction it stopped in. Meet the Neutral Forge, a chip fab sworn to fabricate but never design, kept unownable by the Covenant — thirty-seven keys, nineteen jurisdictions, no single point of control (The Headless Empire). Or Mirage Handler, a wartime erasure protocol somebody has quietly repurposed for a kinder use (Signals in the Margins). Trainverse is also where the shared map gets literal, not just thematic: the route runs through two de-realized zones where identity gets scrubbed on entry, and one of them, the Zoothesia Operational Zone, is confirmed to run under the exact same rule that governs the Zoothesia cycle below.
Legends & Ledgers
Drop the technology, keep the protocol. A folkloric, dateless parallel America of logging camps, island theocracies, and travelling shows, where the strange rule isn't software, it's a piece of social fiction that outgrows whoever invented it. The Concord is a settlement so gently over-engineered that even its soil has opinions — a Consecration deciding what's allowed to take root (All You Can Do Here Is Leave). Across the water, Fortress Island gets written off as barely functioning — cover its unpoliced Lower Level market badly needs (T.R.O.(L.L.)). And the Concord Lumber Company runs, quite well, from behind an invented male overseer who was never a real person — until he started having opinions his author never gave him (The Big Man).
Zoothesia
The furthest extrapolation of the four: a city, Mayaford, where an algorithm called the Zoo decides, person by person, who you're allowed to perceive. Hide someone from enough people's Zoo and, functionally, they've been erased without dying. The system's own formal rule is Perception Must Preserve; the version people actually say out loud is Presence Must Preserve — the gap between a system's technical language and its PR is basically this cycle in miniature. People opt out sideways: Charntown is a whole settlement the Zoo simply doesn't route you to, foulmaxxing is deliberately making yourself disgusting enough to fall out of range, and a black-market Kapala-Halo lets you see through the filter if you can get one. Six stories take this from six angles, from a drug that switches the filters off for one night (Perception Must Preserve) to what the whole apparatus looks like a hundred and fifty years on (Minor Differences Repeating Forever).
What actually holds it together
Partly the map itself — Trainverse's route already runs through zones tied to two other cycles, and that kind of seam will likely keep showing up as the world grows. Even where the map hasn't caught up, a shape keeps recurring in several, though not all, of the stories: a population living, sometimes literally unseen, in whatever gap a well-run system left behind — a tent city, an underground market, a family of missing passengers. Someone who hollows out a role from the inside rather than confront it head-on — a woman running a company from behind a fiction, a guard who never files the paperwork, railway staff repurposing an old erasure tool. And, in a few places, a split between what a system is formally for and what it's actually doing — a rule and its slogan, a protocol and its use. Pull on any of these threads, or something else entirely, and you're adding to the same live, unfinished map.
You don't need all sixteen stories in your head to contribute — this page is the shortcut, the stories are the destination. Pick a cycle, or two if there's a seam between them worth pulling, like Trainverse's de-realized zones. The Codex has every named person, place, organization, object, and concept across all sixteen stories if you need to check a detail or borrow a piece of furniture. Each cycle's own page has its full toybox — the specific tech, rules, and thematic questions its author wants you playing with. Then go read a few stories, and build something the world hasn't seen yet.