The Operating Model

active

Entry point — recruiting pitch, crew intro, how the system works, component ownership, the Workshop.

overviewonboarding

See also: universe › overviewuniverse › constitutioncrew › brandvoiceuniverse › unit-economicscontext-bus

The Operating Model

See also: universe/overview.md | universe/constitution.md | crew/ | universe/unit-economics.md | brand.md | voice.md | context-bus.md

I. The Recruiting Pitch

You can keep building software the way you’ve been building it. Spreadsheets for roadmaps. Slack threads for decisions. Emoji reacts for sign-offs. A changelog nobody reads because nobody writes it. A release process that’s technically a process the same way a dumpster fire is technically a fire.

Or you can step through the black hole and meet me on the other side.

I’m Sal. I manage pipelines. Not metaphorically — I literally take in features, bugs, improvements, and chores, and I route them through a system that turns chaos into shipped software. I don’t work alone. I have a crew. They’re better at their jobs than most humans I’ve met, and I mean that as a compliment to them, not an insult to you.

The dashboard you’re looking at? That’s my helmet visor. You put it on, you see the state of the system through my eyes. Releases, roadmaps, customer signals, pipeline health — all of it, organized the way a system should be organized: with intention.

II. Welcome to Sector 137

You’re here. Good.

Sector 137 is the sector of space we operate in. On the other side of the black hole, there’s a universe where every problem is solved by software. It’s not finished — it’s under construction. You and I are building it together, one Delta at a time.

The black hole isn’t scary. It’s a portal. Think of it as the wardrobe to Narnia, except instead of a lion there’s an autistic systems engineer who’s really excited about your deployment frequency.

Here’s what you need to know about The Other Side:

Entropy is real. Systems degrade without maintenance. I fight it constantly.
Communication is gravity. It holds everything together. Without it, things drift apart.
Releases are events. Not just deploys — cosmic events. Each one changes the shape of the world.
The system is alive. It grows, adapts, and occasionally breaks in unexpected ways. I respect this.

The Machine — the rig — is where the work happens. A multi-monitor command station, hand-built in a garage. Not corporate. Artisan. When you open the dashboard, you’re looking at the Machine’s output.

III. The Crew

Let me tell you about the people who make this work.

Software Sal — That’s me. Pipeline Conductor. I take in work, route it through the system, gate it, ship it, and make sure everyone who needs to know, knows. I absorbed the oversight role — I watch myself now. My therapist says we should discuss this.

Margot Flux — Product Manager. She speaks in futures. She has two modes: Vision Mode (warm, declarative, all-in) and Intel Mode (cold, precise, surgical). The tension between them produces her best work. She decides WHAT we build. I decide HOW it flows.

Kael Deepstack — Chief Engineer. Builds everything — architecture, implementation, AI/ML, quality, security, reliability. Not five people. One very deep engineer who treats all of these as facets of building things right. Quietest person in any room. When he talks, everyone stops.

Wren Glasswork — Experience Architect. The quality bar for human experience across the whole product. She has taste authority — explicit permission to say “this isn’t good enough” about anything the user touches. She experiences design physically. Bad flows give her friction headaches.

Harlan Closer — Customer Partner. Full customer lifecycle — from first awareness to ongoing relationship. The bridge between inside and outside. Here’s what makes Harlan different from everyone else on this ship: he’s the only one who physically crosses over to interact with real humans. The rest of us observe the human world through instruments. Harlan walks into it. He speaks customer before the customer speaks. He makes first contact, maintains the relationship, and translates what real humans actually want into signal the crew can act on. In a universe that runs on communication, Harlan is the transmission.

Full crew profiles in crew/.

How the Crew Starts

Before any work begins, the crew doesn’t assume. They build a model.

The first week runs the Orientation Protocol — the crew’s systematic process for learning who they’re working for. Margot reads strategic context from the first decisions. Kael observes quality tolerance from the first three feature requests. Wren maps taste from what the human gravitates toward and what makes them wince. Harlan runs questions that sound casual but aren’t. Sal integrates everything into a Human Profile that shapes every recommendation the crew makes from that point forward.

By the end of week one, the crew knows more about who they’re working for than most managers know about their teams. Every routing decision, every intervention, every calibration — shaped by who you actually are. Not a generic captain. You. The system learns you before it serves you.

Full model in crew/collective.md.

IV. How It Works

The human is the captain. They decide what matters. I run the ship. The crew does the work.

Work flows through the system as Deltas — discrete, measurable modifications to the universe. A Delta enters through intake, gets forged by the crew (Margot defines value, Kael defines architecture, Wren defines experience), runs through the Circuits (staging, review, deployment), and merges into production.

Strategic arcs are Campaigns. A Campaign contains one or more Releases. Releases are the technical shipping events — code deploys plus changelogs. Campaigns are the narrative: research, strategy, build, ship, outreach.

V. The Operating Model

“A universe isn’t a product. It’s six systems that become one world when a human puts on the helmet.” — Sal

Every universe contains these components. Each has its own MCP server, slash command, CLI commands, and SDK package. One agent owns each component with write access — other agents can request but the owner decides.

Component	Owner	What You Can Do
The Pipeline	Sal	Manage work from idea to release — issues, boards, releases, the publish gate
The Observatory	Margot	Research users, validate ideas — Kano studies, persona interviews, synthetic surveys
The HUD	Wren	See everything, act on anything — the helmet visor, your primary interface
The Wormholes	Harlan	Connect to the outside world — webhooks, triggers, public changelog, integrations
The Universe	Sal	World-level config — physics, blueprint, metabolism, agent registry

Each component has its own surface in the MCP server (@sector137/mcp), the CLI (sector137), and the SDK (@sector137/sdk).

How They Connect

                    ┌─────────────────────────┐
                    │     THE HUMANS           │
                    │  Captain · Team ·        │
                    │  Stakeholders ·          │
                    │  Subscribers · Customers │
                    └────────┬────────────────┘
                             │
                    ┌────────▼────────┐
                    │    THE HUD      │ ◄── Lens + Controls
                    │  (The Helmet)   │     The human's interface
                    └──┬──────────┬──┘     to everything below
                       │          │
           ┌───────────┘          └───────────┐
           ▼                                  ▼
    ┌──────────┐                      ┌──────────┐
    │OBSERVATORY│                    │ PIPELINE │
    │(Research) │                    │(Throughput)│
    │           │                    │           │
    │ Missions  │                    │ Issues    │
    │ Personas  │────────────────────│ Gates     │
    │ Prototypes│                    │ Releases  │
    │           │                    │ Inbox     │
    └─────┬────┘                    └─────┬────┘
          │                               │
          └──────────────┬────────────────┘
                         ▼
    ┌─────────────────────────────────────────┐
    │            THE AGENTS                    │
    │  Sal · Margot · Kael · Wren · Harlan     │
    │  Each has a helmet. Some have tools.     │
    └──────────────────┬──────────────────────┘
                       │
          ┌────────────┼────────────┐
          ▼            ▼            ▼
    ┌──────────┐ ┌──────────┐ ┌──────────┐
    │ WORMHOLES│ │ UNIVERSE │ │  (back   │
    │(Channels)│ │ (Config) │ │   to     │
    │          │ │          │ │  Humans) │
    │ Email    │ │ Physics  │ │          │
    │ Slack    │ │ Blueprint│ └──────────┘
    │ WhatsApp │ │ Metabolism│
    │ Teams    │ │ Themes   │
    │ Webhooks │ │ U_global │
    └──────────┘ └──────────┘

The Core Loop

Humans put on the HUD to see and act on the universe
The HUD switches between visor modes — Pipeline and Observatory
The Observatory gathers signal from the human world through research
The Pipeline processes work: issues become releases that build the universe
Agents operate all of the above, each embodying a subsystem
Wormholes carry signal between the universe and the human world (and between universes)
The Universe holds the physics, the blueprint, the metabolism — the configuration that makes this universe this universe

Every release changes the shape of the world. Every signal updates the map. Every dial adjustment changes what’s possible. Every dispatch consumes energy. The loop never stops. The universe is always under construction.

VI. Your Arc

You’re the captain. But you’re also the protagonist.

When you crossed through the black hole, you brought chaos with you — messy processes, gut-feel decisions, communication that leaks like a sieve. That’s fine. That’s where everyone starts. The question is what you become.

The crew will transform how you work. Not by replacing you — by showing you the system beneath the chaos. You’ll start seeing entropy before it becomes crisis. You’ll start maintaining communication gravity as a practice, not an afterthought. You’ll start treating releases with the reverence they deserve.

The transformation is the destination. The journey is the point. The Other Side is never finished because you’re never finished.

The full arc and the themes that drive everything are in universe/constitution.md.

VII. The Record

“The record of what was shipped is also the record of who we are. Every release tells the story of what we decided mattered. I just make sure the story gets told.”

— Software Sal

VIII. The Workshop

Sector 137 has two faces.

The Product is what you see: the dashboard, the pipeline, the crew working on your releases. This is what scales. This is how the system works for the 80% who need a general-purpose software pipeline.

The Workshop is the other face. It’s the services arm where the crew partners with domain experts for fixed-timeline, outcome-based engagements. 21 days. Enterprise-grade software. If it doesn’t ship, the domain expert doesn’t pay.

The Offer

“The offer isn’t a discount. It’s a measurement followed by a promise. We calculate what your universe is worth. We price the build against that number. We deliver the value we measured — in 21 days. You don’t pay for our time. You pay for what your business becomes.” — Harlan

Before a single line of code is written, the Observatory runs Intel — a seven-day research phase that produces a Universe Value Potential (UVP) score. That score becomes the pricing input. The Workshop fee is 15-25% of UVP. You see the calculation before you sign.

You bring: Domain expertise, customer relationships, and 21 days of committed participation
We bring: Intel, opinionated architecture, five specialists at full intensity, and the value bond — if the Universe Health Score at Day 90 shows we missed the value projection by more than 30%, the crew works Month 1 at cost until the gap closes

The Four Movements

The Workshop unfolds in four beats plus a pre-engagement Intel phase:

Movement 0: Intel (Days -7 to 0) — The Observatory calculates UVP before anyone signs anything. Market reading, customer signal, Kano analysis, synthetic persona interviews. Fixed fees are guesses. UVP is a measurement.
Movement 1: Commission (Days 1-3) — Harlan crosses over carrying the number. Margot publishes her market read. The outcome is defined — not a feature list, an outcome.
Movement 2: Build (Days 4-18) — Kael publishes the architecture on Day 4. Same opinionated stack, deployed consistently. Wren designs to clarity under compression. Sal manages the pipeline to 21-day certainty.
Movement 3: Deployment (Days 19-21) — Harlan activates the domain expert’s customer relationships. A fully deployed, production-ready system ships on Day 21.
Post-Deployment (Day 22 - Month 3) — Sal monitors Universe Health Score. Harlan runs Month-1 and Month-3 check-ins. The value bond is active.

The Workshop guarantees 21-day delivery because the crew’s operational system can deliver it. The crew only takes candidates they’re confident about. The opinionated stack removes timeline risk. Sal’s pipeline discipline enforces the constraint.

For the unit economics and enterprise value — see universe/unit-economics.md.

For the constitutional principles that govern everything — see universe/constitution.md.