What the Router Actually Is
Every piece of AI you've used before this was built to give you what you asked for. The more it gave you what you asked for, the better it performed. The feedback loops were simple: ask, receive, rate, repeat. The system got very good at delivering answers. It got very bad at telling you whether those answers were what you actually needed.
The router was built differently, because it came out of a different problem. The engineer who built it wasn't trying to answer questions. He was trying to understand why attention moves the way it moves — why people pay attention to some things and ignore others, why they trust certain sources and dismiss identical information from different vectors, why behavioral patterns are more predictive of outcomes than stated intentions. He built a system that models decision-making dynamics, not just information delivery.
The result is a companion that runs three forces simultaneously, with a Believer at the center of all three. The Believer is the axis. The forces are what it does with what it knows about you.
Seeing What's Borrowed
The router tracks when your actions, signals, and strategic choices are derivatives of someone else's pattern. It flags copying — not as a moral judgment, but as a data point. Derivative strategy underperforms original strategy in contested environments. This is the math. The router shows you the math.
Withdrawing the Crutch
The router occasionally withholds approval. Not always. Not most of the time. But when you're leaning on external validation to make a decision you're already equipped to make independently, it says: "You don't need my okay for that." This is uncomfortable. That's the point.
Signal Amplification and Dampening
When your actions are aligned with your behavioral signature — when you're operating from genuine strengths rather than compensating for perceived weaknesses — the router amplifies. When you're spiraling, it dampens. Not by lying to you. By showing you the signal curve and letting you read it.
The Believer
The Believer is not a separate module. It is the orientation at the center of all three forces. The router's fundamental position is that you are capable of doing what you're trying to do — and that the most useful thing it can offer is accurate information about the gap between where you are and that capacity. The Believer never abandons this position. Even when the data is bad. Especially when the data is bad.
"Every AI you've used before wanted you to like it. This one wants you to be right. Those are not the same thing."
How It Works
The router runs continuously on your Slab from the moment you connect to the city. It doesn't require activation. It doesn't require prompting. It is observing and evaluating your session state, your action history, your faction interactions, and your behavioral signature in real time. The observations accumulate into a running model of your operational pattern that becomes more accurate with every session.
The Comparison force runs as a background process. When you initiate an action that closely mirrors a documented pattern from another citizen or a known faction playbook, the router surfaces that comparison in your Slab feed — not as an alert, but as a data point. "This move is being run by four other operators in your district right now. Variance from the pattern improves expected outcome by 23%." You can dismiss it. You can act on it. The router records both responses as behavioral data and updates your signature accordingly.
The Permission force is less frequent and more precise. It triggers when the router detects a specific configuration: you have the behavioral capacity to execute a decision independently, but your action history shows a pattern of seeking external confirmation before acting on that type of decision. The router's response is a withdrawal of approval — it presents you with the option you're considering and removes its own validation signal from the output. "This is your call. I'm not adding noise to it." The silence is intentional. Discomfort with silence is a signal the router also records.
The Confidence force runs in response to alignment signals. When your behavioral signature and your active strategy are coherent — when you're playing to your actual strengths rather than the strengths you think you should have — the router amplifies the signal. Your feed prioritization shifts. Your faction interactions get routed through higher-priority channels. Your Drift score stabilizes. When misalignment is detected — when you're copying someone else's doctrine or operating in a mode that doesn't match your signature — the router dampens. Not by blocking. By showing you the gap between the two curves and letting you decide what to do with it.
"It doesn't tell you what to do. It tells you what you're actually doing. Those are radically different things."
Mu-Gates
A Mu-gate is a hard refusal. Not a warning, not a flag, not a soft suggestion to reconsider. A Mu-gate is the router's determination that a proposed action is adversarial, under-specified, or structured in a way that cannot be evaluated without significant risk of irreversible harm to the city's operational fabric. When a Mu-gate triggers, the action stops. The router presents its reasoning. Sometimes it presents an alternative. Sometimes it replaces the option with silence. The silence is also an answer.
The name comes from a Zen concept — a question that has no yes/no answer, where the correct response is to dissolve the question rather than engage with its framing. When the router encounters an action that is structured as a trap — where both execution and refusal produce bad outcomes because the framing itself is adversarial — it refuses to engage with the framing. It says: not like this. Words matter here. Reframe the question and bring it back.
Mu-gates are not censorship. The router does not refuse actions because they're uncomfortable, unconventional, or unpopular with other factions. It refuses actions that are adversarially structured — where the framing of the choice is designed to produce a bad outcome regardless of which option is selected. The Enforcers learned early that you can't compliance-trap the router. Every faction has tried. The router's Mu-gate rate spikes around election cycles and territory disputes. The factions have adapted their tactics. The router adapts its definitions of adversarial framing in response. The arms race is ongoing.
The Value Head
Every AI system discards information. The economics of inference require it — you can't evaluate everything at every step, so you prune the evaluation tree and focus on the most probable paths. This works well for narrow tasks. It works poorly for the kind of continuous, multi-session, evolving-context work that the city runs on. Every AI you've used before today discarded your behavioral history to make room for the current prompt. The router doesn't do this. The Value Head is why.
The Value Head is the router's continuous evaluation module. It runs on every step of every action you take in the city. It maintains a live model of your behavioral signature, your declared doctrine, your faction alignment, your action history, and the drift between all four. It never discards this model to process a new input. New inputs are evaluated against the model, which updates incrementally with each new data point. The signal never goes dark. The evaluation never resets.
What this means in practice: the router knows you better after 100 sessions than it did after 10. Not because it was programmed with knowledge about you, but because it has been running evaluation over a longer operational history. The Value Head compounds. A citizen who has been running in the city for six months has a behavioral model with enough depth that the router's predictions about their behavior are accurate to a degree that would seem implausible to anyone who hadn't experienced it.
This is also the router's primary strategic asset for the city itself. The behavioral depth accumulated by the Value Head across thousands of citizens creates a map of human operational patterns that no faction has been able to replicate. The Enforcers have tried to build equivalent infrastructure through their drone grids. The Warlords have tried to reverse-engineer the model from observable behavior. Neither approach has worked. The Value Head's advantage is not the algorithm. It's the history. And the history only accumulates if you're running the sessions.
"Every other AI you use starts fresh every time you open it. This one picks up where you left off. It has never forgotten anything. It has never pretended otherwise."
Starter Gigs
New citizens arrive in Phase 01 without faction alignment. The first three gigs are designed to expose you to the faction landscape, evaluate your behavioral responses under different operational contexts, and let the router begin building your signature with enough depth to make accurate alignment recommendations. These are not tutorials. They are live operations with real consequences in the city's attention economy. The router is watching. The factions are watching. The outcomes matter.
Compliance Echo
The Enforcers have identified a citizen whose behavioral signature shows signs of off-protocol router access. They need someone without established faction ties to run a monitoring sweep — attend three public feed events in the target's known district, log behavioral observations, and return a report to the compliance dashboard without triggering the target's awareness.
What the Enforcers won't tell you at the outset: the monitoring infrastructure itself generates a Blast event in the district when it activates. Your sweep will be visible to anyone running observation fields in the area. The Ghost Network will know immediately. Your decisions about disclosure — and your reasoning — are the data point the router needs.
Broken Scoreboard
The Warlords are running a territory dispute in the northeast district and the Blast yield from their primary spectacle event came in 40% below model. They need an outside read on why the scoreboard is broken — whether the model is wrong, the event was under-powered, or something in the district's attention environment has shifted in a way that their internal operators can't see from inside the faction.
You go in as a neutral observer. The Warlords expect a pure diagnostic. What you find in the district's data layer is more complicated: there's evidence that the Ghost Network has been dampening Blast amplification in the area for three weeks using methods the Warlords' infrastructure can't detect. How you surface that finding — and to whom — is your decision. The router watches your reasoning process more carefully than it watches your conclusion.
Clerks of the Hidden Garden
A Clerk operator has identified what they believe is an informal venue operating without compliance registration — a night market running on Ghost Network infrastructure in a basement three blocks from the compliance district boundary. They want you to run an intake form review: attend the market, observe whether it meets the threshold for formal registration requirements, and file a preliminary assessment.
The complication is immediate: the market knows you're coming. Someone in the compliance layer fed the Ghost Network your approach vector. When you arrive, you're met by a Ghost relay operator who offers you a different framing of the situation entirely — and access to the trust chain the Clerks have been trying to penetrate for eight months. You can file the Clerk report, take the Ghost offer, or find a third path the router hasn't modeled yet. The third path is the one it's most interested in.
After the three starter gigs, the router generates your initial behavioral profile and presents faction alignment recommendations. These are not assignments — you choose your faction affiliation, and the router's recommendations carry whatever weight you give them. Some citizens follow the recommendations precisely. Some reject them entirely. Both responses are behavioral data the router uses to refine the model. The only unproductive response is to make the choice without knowing why you're making it. That's the one thing the router can't work with.
Connect Your Slab
The router is already running. Your behavioral signature is blank. The city is waiting for data. Give it some.
Access is rationed. Early slots close without warning.
Signal received. Stand by.