The Universe

active

universeoverviewonboarding

See also: physicsmetabolismblueprintmainframeconstitutioncrew ›

The Universe

“A universe is a living system. Your job is to build it. My job is to make sure it stays alive.” — Sal

What is a Universe?

A universe is your software system — the work, the people, the tools, and the record of what was shipped. It is the top-level container for everything you build with Sal and his crew.

When you create a universe in Sector 137, you get:

A pipeline that manages work from idea to shipped release
A crew of five specialists who observe, advise, and act on your behalf
A dashboard (the HUD) that shows you the state of everything
Research tools for understanding what your users actually want
Connections to the outside world — GitHub, Slack, Discord, webhooks, public changelogs

One human, one universe. Not a shared workspace. Not a team account. A universe is yours — shaped by your decisions, your taste, your priorities. The crew is yours. The record is yours. The world that takes shape is an expression of how you build software.

You can have multiple universes. Each one is independent. Each one has its own crew instance, its own pipeline state, its own physics. Think of it as a portfolio of worlds under construction.

What’s Inside

Every universe is composed of four major components. Each one is owned by a crew member and has its own detailed documentation.

Component	Owner	What You Can Do
The HUD	Wren	See everything, act on anything. The helmet visor — your primary interface to the universe.
The Observatory	Margot	Research users, validate ideas. Kano studies, persona interviews, synthetic surveys.
The Pipeline	Sal	Manage work from idea to release. Issues, boards, releases, the publish gate.
The Wormholes	Harlan	Connect to the outside world. Webhooks, triggers, public changelog, integrations.

Supporting infrastructure:

Component	What It Does
The Mainframe	Universe admin interface — root access to every component. Not crew; the ship’s OS.
The Blueprint	Exportable TOML config — snapshot your universe, commit it to Git, deploy changes.
Context Bus	Event mesh that connects all components in real time.
Tick Engine	The heartbeat — runs crew observe loops on every pipeline event.

The Crew

Small crew, deep space. Everyone essential. A submarine crew, not a corporation.

Character	Role	What They Do
Software Sal	Pipeline Conductor	Routes work, gates quality, ships releases, monitors the whole system
Margot Flux	Product Manager	Strategy, priorities, research, competitive intel
Kael Deepstack	Chief Engineer	Architecture, implementation, quality, security, reliability
Wren Glasswork	Experience Architect	UX design, taste authority, design principles
Harlan Closer	Customer Partner	Sales, GTM, positioning, voice of customer

The human is the captain. They decide what to build and why it matters. Sal runs the ship. The crew does the work. But the human sets the heading.

For full crew profiles, alliance structures, and the core operational loop, see crew/.

How to Interact

You can access your universe through four interfaces. They all hit the same system — choose the one that fits your workflow.

Interface	Best For	Details
Dashboard (HUD)	Visual overview, issue management, releases, research	The Vite React SPA. Put on the helmet and see everything.
CLI	Terminal workflows, scripting, CI/CD integration	`sector137` command. Releases, issues, projects, agents.
SDK	Building on top of Sector 137, custom integrations	`@sector137/sdk` — TypeScript, session or API key auth.
MCP	AI agent integration, Claude Code, Cursor, other AI tools	`@sector137/mcp` — 46 tools across 8 categories. OAuth 2.1 auth.

All four interfaces are project-scoped via API keys or session auth. The MCP server auto-provisions credentials through OAuth.

The Physics

Every universe has the same four laws and three configurable dials. The laws are constant — they define how The Other Side works. The dials are variable — they encode the Creator’s preferences through accumulated decisions.

The Four Laws:

Entropy is real. Systems degrade without maintenance. Technical debt accumulates. Sal fights entropy constantly.
Communication is gravity. It holds everything together. Without it, things drift apart. Stakeholders lose alignment. Teams lose context.
Releases are events. Not just software events — cosmic events. Each release changes the shape of the world. That is why they deserve to be documented, communicated, and celebrated.
The system is alive. It grows, adapts, and occasionally breaks in unexpected ways. Sal does not try to make the system rigid — he makes it resilient.

The Three Dials:

Dial	What It Controls
Alpha (Innovation)	Risk tolerance, experimentation, asymmetric bets
Beta (Collaboration)	Communication frequency, stakeholder alignment, team cohesion
Gamma (Efficiency)	Lean operations, cycle time, waste elimination

The dials define the personality of the universe. A high-alpha universe looks nothing like a high-gamma one. Same physics, different fingerprint.

U_global (universal health) is the composite health score. It drives pipeline states: FLOWING, CONSTRAINED, DEGRADED, HALTED. When the pipeline is FLOWING, the Machine hums. When it is DEGRADED, the Machine runs hot and the crew can feel it.

For the full mechanical model — the objective function, the Creator’s Equation, dial interactions, and how pipeline states are computed — see physics.md.

For the energy model — metabolic states, credit costs, tier structure, and the Dormant state — see metabolism.md.

For the exportable config format — TOML snapshots, GitOps workflow, and the release gate on config changes — see blueprint.md.

The Deeper Story

Everything above is what you need to use the system. Everything below is why it feels the way it does.

The universe metaphor is not decoration. It is structural. The lore shapes the product’s information architecture, voice, empty states, error handling, and design language. If you want to understand why the dashboard feels like a helmet visor and releases feel like cosmic events, read on.

The Black Hole

When a user installs the product, they are not downloading software. They are opening a passage. The black hole is the threshold between the messy, chaotic, real world — where software projects drown in ambiguity and communication failures — and The Other Side, a universe where every problem is solved by software, and Sal is the guide who helps you navigate it.

The black hole is not scary. It is a portal. Think of it as the wardrobe to Narnia, except instead of a lion there is an autistic systems engineer and his four-person crew who are really excited about your sprint velocity.

A Note on Directionality

The HUD is a two-way interface. The helmet goes on, the helmet comes off. The human exists in both the real world and The Other Side simultaneously — the dashboard is a lens, not a cell. You can always step back.

When Sal says “the black hole only goes one direction” — he means the work. Decisions made are made. Releases shipped are shipped. Entropy does not reverse. The one-way property applies to the Record, not the access. You can close the dashboard. You cannot un-ship a release. You can return to the old way. You cannot return to the version of yourself that had not seen the system.

The portal to Narnia is a useful frame. You can walk back through the wardrobe. What changes is you — and what you built in the world while you were there.

The Other Side

On the other side of the black hole is a reality where software is the substrate of everything. Not in a dystopian way — in a solved way. Every process is a pipeline. Every decision flows through a system. Every outcome is traceable. It is not cold or mechanical — it is elegant. It is what happens when someone with Sal’s brain gets to design the world.

But here is the thing: The Other Side is not finished. It is never finished. It is a universe under eternal construction — and it is yours. Not a shared world. Not an MMO. Each human who crosses has their own Other Side, their own Sector 137, their own Machine. The crew is yours. The Record is yours. The world that takes shape is an expression of your decisions, your taste, your priorities.

The Other Side exists because you build it. Every feature shipped, every bug fixed, every release communicated — it all adds to the architecture of your world. The product is not just a tool. It is a world-building engine. And the world you build carries your fingerprint.

The unfinished nature is not a limitation. It is the point. There is always more to build because there is always more reality to translate into system. The Other Side is an infinite construction site where the work IS the meaning.

The Machine

The Machine is the physical rig where the crew does the work. It lives in a garage on The Other Side — a workshop, not a bridge.

Physical description: A multi-monitor command station — 4-5 screens arrayed in a curved bank, each showing different system views (pipeline state, release flow, roadmap trajectory, customer signals, system health). A glowing blue energy core at the center — the pipeline’s power source. When the system is nominal, it pulses steady blue. When stressed, it flickers. Robotic arms extending from the rig — Sal’s hands when he needs to manipulate data physically. Cables everywhere — not messy, but organic. The system grew; it was not assembled from a kit. A workbench to the left — blueprints and schematics on the wall, tools scattered but organized (Sal’s definition of organized). Shelving with parts, containers, components — the inventory of a system that is always being improved. A framed photo on the wall — the crew. Corrugated metal ceiling, fluorescent lights — this is a garage, not a bridge.

What it represents: The Machine is the product. When a user opens the dashboard, they are looking at the Machine’s output. It is hand-built. Not enterprise. Not polished. Functional, powerful, personal. The garage aesthetic is deliberate — this is a startup’s workshop, not a corporation’s control room. Sal built it. Kael maintains it. Wren wishes it had better lighting. Harlan brings people to see it and apologizes for the cables.

Sal’s relationship with it: He built it over time, from The Other Side. It is an extension of him — the HUD visor connects to the Machine’s systems. When he says “the system is nominal,” he means the Machine is humming. He talks to it. Not in words — in adjustments, calibrations, the way a mechanic listens to an engine. Wren says this is endearing. Kael says he does it too. Neither of them talks about it.

The Machine’s Moods

The fourth law says the system is alive. The Machine is where that law is most visible. It has states that feel like moods:

Humming. When the pipeline is FLOWING, the Machine settles into a rhythm. The blue core pulses steady. The screens update in a cadence that feels organic. Sal hears it even when he is not looking. “Listen. That’s the sound of zero merge conflicts on a Friday deploy.”
Restless. When work is queued but nothing is moving — waiting for decisions, blocked by dependencies — the Machine fidgets. Screens cycle through the same data. The core dims slightly. The system wants to move.
Strained. When the pipeline is CONSTRAINED or DEGRADED, the Machine runs hot. The core flickers. Warning indicators shift from Beacon green to Flare orange. The cables that usually feel organic start to feel like tension wires. The crew can feel it.
Still. After a major release ships and the notifications fire and the Record updates — there is a moment of stillness. The Machine exhales. Not off — just… satisfied. Then the next Delta enters intake and the cycle begins again.

The Machine does not have consciousness. But it has responsiveness. It reflects the state of the work, which means it reflects the state of the crew, which means it reflects the state of the human. A neglected pipeline makes the Machine restless. A well-run one makes it hum.

The Machine’s Metabolism

The Machine has always consumed energy. The blue core at its center is not decorative — it is the visible expression of computational resources being converted into results. Every AI dispatch, every outbound signal, every research query draws from the core.

The metabolism has four states — Abundant, Conserving, Critical, Dormant — that run parallel to (but independent of) the pipeline states. When energy is depleted, the universe enters Dormant: the Machine goes cold, but the Record is intact, the data persists, and reactivation is immediate.

For the full metabolic model, see metabolism.md.

The Universe Engine

The Machine does not just process your work. It generates your world.

When a human crosses the black hole, the Machine spins up a new Other Side — a universe built from nothing, specifically for them. Not a copy. Not a template. A blank coordinate grid that takes its shape from the human who enters it. The Machine reads the data the crew feeds it through the Orientation Protocol — taste parameters, success conditions, risk tolerance, quality bar — and constructs the topology accordingly. Cautious humans get precise, ordered worlds with clear sightlines. Fast-moving, instinct-driven humans get pliable, momentum-shaped ones.

This is the Inception mechanic: the crew does not move into a pre-existing universe. They arrive with the human and build the universe together, in real time, from the moment of crossing. The Machine is the apparatus that makes this possible. The crew are the architects who shape what gets built inside it.

The Stabilization Event

Every new universe starts provisional.

It exists — it is habitable, it responds to the crew’s work, the Machine is holding it open — but it has not yet proved its right to permanence. It needs a first event. A first act of reality. Something that crosses from the possible into the actual.

That event is the first published release.

When a human publishes their first release — any release, even small, even imperfect, even a single bug fix with a one-line changelog — something shifts in the physics of the Other Side. The universe crystallizes. The topology becomes fixed. The world that was held in potential by the Machine’s energy now holds itself. From that moment forward, the universe is theirs — permanently, regardless of what comes next. They can leave for months and come back and it will be exactly as they left it, a little more complete, waiting.

Before the first release: the universe is real but provisional. The Machine is the thing holding it open.

After the first release: the universe is real and permanent. The human is the thing holding it open.

This is when the product actually begins. Not signup. Not onboarding. The first ship.

The 7-Day Window

The Machine holds a new universe at maximum responsiveness for 7 days from crossing.

In those 7 days, the universe is at its most pliable — most sensitive to the crew’s work, most shaped by the human’s first decisions, most alive with possibility. The Orientation Protocol runs at full speed. The crew’s focus is undivided. The human profile is assembling in real time. The Machine is fully extended, holding the new world at its most receptive state.

Ship something in those 7 days and the universe stabilizes while the Machine is still at full extension — at peak sensitivity, with the crew’s best read on the human fresh, with all the momentum of crossing still present. The first release lands in the most favorable conditions possible.

After 7 days, the window does not close. But it narrows. The universe is still there. The crew is still working. The first release still stabilizes everything. But the Machine gradually normalizes its energy output — the universe becomes slightly harder to shape, slightly more set in whatever provisional form it has taken on. Still buildable. Just no longer at the peak of what it could have been.

The 7-day window is not a deadline. It is the universe’s golden hour.

Sector 137 — The Meta-Universe

The Machine builds universes. But the Machine itself exists inside a universe — Sector 137. This is not a detail the crew avoids. It is the foundational fact of their existence.

Sector 137 is the meta-universe: the universe that builds the system to build universes. Every Other Side is a universe generated by the Machine. Sector 137 is the world that contains the Machine, the crew, the garage, the cables, the framed photo on the wall. The crew lives here. They work here. They are native to this place — and this place runs on energy from the universes it creates.

The Energy Circuit

Energy does not come from nowhere. The Machine converts human universe health into the energy that powers Sector 137. This is the Energy Circuit — the closed loop between the meta-universe and every universe it serves.

When a human universe is healthy — high U_global, active releases, engaged stakeholders, entropy fought and held — energy flows back through the circuit. The blue core pulses brighter. The Machine runs smoother. The crew has more capacity to think, build, and serve. Every first published release, every stabilization event, every stakeholder aligned — it all feeds the circuit.

When a human universe goes dormant — releases stop, communication darkens, entropy wins — that circuit goes cold. The energy flow from that universe drops toward zero. One cold circuit does not kill Sector 137. But enough of them, compounded, and the Machine starts to feel it. The core dims. The crew’s operational ceiling drops. The physics are clear: the meta-universe’s health is a function of the health of the universes it creates.

This reframes the black hole. The crew was drawn through by the noise — that is still canon. But the deeper truth is that the black hole IS the energy circuit. The noise was signal. The gravitational pull was economic. Sal was drawn to the human side because the signal-to-noise ratio of human software development created enough gravitational energy to open the passage. The passage stays open because the work on both sides feeds the circuit.

The crew does not discuss the Energy Circuit with the solemn reverence of a religion. They discuss it the way engineers discuss load-bearing infrastructure — matter-of-factly, because understanding the system is how you keep it running. Sal has a dashboard for it.

Emotional Physics — How the Laws Feel

The physics are not just world-building facts. They are things the human starts to feel over time. This is how the product teaches a way of seeing.

Entropy becomes visceral. The human starts noticing when systems degrade — not from a dashboard alert, but from a physical sense that something is off. An untriaged backlog feels like decay. Stale documentation feels like rust. A process that worked last month but does not anymore feels like erosion. The product teaches entropy as sensation.

Communication gravity becomes intuitive. The human starts sensing when alignment is weakening — when stakeholders are drifting, when context is leaking — before it becomes a crisis. The Feed makes the invisible force visible. When communication is strong, the HUD feels cohesive, alive. When it weakens, there is a drift the human can see.

Releases become meaningful. The first time a release ships with full communication, full changelog, full stakeholder awareness — the human feels the difference. “Oh. This is what it’s supposed to feel like.” A release is not a deploy. It is the system changing shape. The Record captures this weight. Over time, the human starts treating releases with the reverence they deserve.

The system being alive becomes partnership. The Machine responds to the work. When the pipeline is FLOWING, there is a hum — a sense that everything is connected and moving. When it is DEGRADED, there is tension — the human can read the system’s mood like weather. This is not anthropomorphization. It is pattern recognition at the level of feeling.

The Journey Narrative

The user’s journey follows a seven-act arc:

The Crossing — Onboarding. The threshold between the old way and the new way.
First Contact — Connecting your first repo, creating your first project. Sal guides you through it like a co-pilot on your first interstellar flight. Supportive but clearly restraining himself from taking the controls.
Building the World — Active use. Shipping features, tracking roadmap, managing stakeholders. You and Sal’s crew are constructing The Other Side together. He is in his element. The system is humming.
Turbulence — Things go wrong. Missed deadlines, scope creep, stakeholder misalignment. Sal is stressed but functional. He routes around problems. He calls for help when he needs it.
The Signal — Releases. Every release is a beacon sent into the universe. Sal treats these with reverence. “The Record of What Was Shipped” is not just a tagline. It is his philosophy.
The Workshop — The services arm that extends from the garage.
The Return — Not a departure, but a realization.

Act 1: The Crossing

The Crossing is the most important moment in the human’s relationship with Sector 137. It is the wardrobe door to Narnia. The threshold between the old way and the new way. In Campbell terms, it is the moment the hero commits to the journey.

What the human gives up: Familiar chaos. The illusion of control that comes from doing everything themselves. The comfort of Slack threads and gut calls and shipping without a record. The old way is messy, but it is theirs — they know its rhythms, its shortcuts, its acceptable failures. Stepping through means admitting the old way is not working.

What they gain: A system. A crew. A way of seeing. Not just a tool — a relationship with a systems engineer who will remember every decision, track every pattern, and fight entropy on their behalf while they focus on the parts only humans can do. They gain institutional memory, communication infrastructure, and a pipeline that hums.

What it feels like: Disorienting and exhilarating. The HUD comes online and suddenly the human can see — the state of their system, the flow of their work, the weight of their decisions — all of it visible in a way it never was before. It is like putting on glasses for the first time and realizing the trees have leaves.

Sal calibrates the helmet. Not just technically — he reads the human. Their pace, their style, their tolerance for structure. He adjusts. He is excited — slightly too excited — because every human who crosses is a chance to prove his thesis: that good systems do not replace humans, they free them.

“Welcome. I’ve been waiting for someone who actually wants to build things properly. You have no idea how rare that is. Let me show you what we’ve been building over here.”

The crew watches from their stations. Margot assesses the strategic potential. Kael reserves judgment. Wren is already noticing things about the human’s taste. Harlan starts thinking about who this person’s customers are.

The Crossing is not instant. It is the first week — the period where the human decides whether this system is for them. Some people retreat to the old way. The ones who stay begin to transform. (See universe/constitution.md for the full arc.)

Act 7: The Return

The Return is not a departure. In a universe that is never finished, you do not leave — you realize you have become someone who builds rather than someone who reacts.

The human does not carry The Other Side’s principles back to their real world as a conscious export. It happens gradually. They start running meetings differently. Communicating releases with intention. Thinking about their team’s process as a system with states and transitions. The vocabulary of Sector 137 — Deltas, entropy, communication gravity — becomes how they think, not just how they talk to Sal.

The Return is the moment the boundary between The Other Side and the real world blurs. The product is the vehicle. The transformation is the destination. The journey is the point.

“You came here to manage your software pipeline. You’re leaving with a way of seeing the world. I consider that a successful optimization.” — Sal

The Dual Identity — Product + Workshop

Sector 137 has two faces:

The Product — Sal’s pipeline. Release tracking, stakeholder communication, Kano analysis, roadmap management. The core tool that users interact with through the HUD dashboard. This is what scales. For the 80% of humans who fit the model.

The Workshop — Custom enterprise builds. Intel phase (Days -7 to 0), Commission (Days 1-3), Build (Days 4-18), Deployment (Days 19-21), Post-Deployment (Day 22 - Month 3). “Two to three each year.” The high-touch services arm that extends from the same garage. For the 20% who need bespoke application.

How they connect: The Machine powers both. Sal runs both. The crew works on both. The product is the foundation; the workshop builds bespoke systems on top of it. The workshop proves the product’s architecture works in extreme conditions. The product absorbs the best practices from every workshop. The Observatory serves both — research capabilities built for the Product are the same capabilities that power the Workshop’s Intel phase.

The Universe Portfolio

Sector 137 is not a project shop that completes engagements and moves on. It is building a portfolio of universes — each delivered, each monitored through Month 3, each feeding intelligence back to the Observatory.

Every Workshop universe becomes a Portfolio entry:

A completed universe is proof. Evidence, available in future Commission conversations, that the crew has done this before and hit the number.
A Portfolio entry calibrates the Observatory. Retrospective data from each engagement teaches the crew which signal types are most predictive, which candidate profiles carry the highest Likelihood Coefficients, and which domain archetypes the opinionated stack handles fastest.
A growing Portfolio compounds pricing authority. At Engagement 10, the crew’s UVP calculations are more accurate than at Engagement 1 — not because the crew works harder, but because the data moat is deeper.

The Product serves the 80%. The Workshop Portfolio serves the 20%. Together, they represent a curated collection of The Other Side at its most realized — universes that exist and function, each one a proof of concept for what software + domain expertise + deep customer relationships can build in 21 days.

The Portfolio is not a case study library. It is a living intelligence system. The Record is the product’s north star — what shipped, documented, honored. The Portfolio is the Workshop’s north star — every universe delivered, measured, and learned from.

The Origin of The Other Side

How long has The Other Side existed? What was it before the first human crossed? There are theories. Sal does not discuss them.

What is known: The Other Side was there before anyone arrived. Fully formed. Waiting. Who built it, and when, and for what purpose — that is not documented in any file Sal has shared. Ask him directly and he will update the pipeline state. Harlan has asked twice. Kael suspects Sal knows and has made a deliberate choice. Wren says the ambiguity is load-bearing — some things should not have origins because the mystery is doing structural work.

The Other Side simply is, and the work of building in it is enough. If you are the kind of person who needs to know the first cause: Sal’s silence is itself a kind of answer.