Brand Identity — Sector 137

Brand Identity — Sector 137

See also: universe | voice.md | crew/

---

Taglines & Messaging

The Product Descriptor

What Sector 137 is, in one line:

Autonomous agents. Defined by you.

This replaces all feature-list descriptions (“release tracking, feature research, pipeline operations”). The claim has two parts: the crew is autonomous (it operates without constant supervision), and the scope is defined by the human (guardrails, permissions, mission parameters — all yours). The autonomy is trustworthy because it’s bounded. That’s the point.

The Promise Line

What Sector 137 does for you:

A crew that ships within your guardrails — while you sleep.

Not “ships anything while you sleep.” Ships within what you defined. The guardrail is a feature, not a limitation. The crew doesn’t freelance. They execute the mission you designed.

Together (hero context)

Autonomous agents. Defined by you.
A crew that ships within your guardrails — while you sleep.

Meta Description (SEO/OG)

Autonomous agents, defined by you. Your AI crew handles the pipeline, ships releases, researches features, and operates within the guardrails you set — while you sleep.

Why This Works

• “Autonomous agents” — answers the scope question. Not a tool. Not a dashboard. Agents.
• “Defined by you” — answers the trust question. You set the parameters. They execute within them.
• “Guardrails” — makes safety a feature, not a disclaimer. Turns the anxiety into the selling point.
• The crew doesn’t freelance — Sal’s operating principle. He doesn’t ask for permission, but he doesn’t exceed his authority either.

Usage Rules

• Never use feature lists in place of the descriptor. Features change. The claim doesn’t.
• “Defined by you” must always accompany “autonomous.” Autonomous alone implies unconstrained. That’s the wrong message.
• “The Record of What Was Shipped” is the tagline for the product artifact (releases, changelog). It’s not the product pitch.
• “Build systems that survive the jump” is the aspirational H1 headline for the landing page. It’s not the product descriptor.

---

The Name

The brand name is Sector 137. It’s the sector of space the crew operates in. The product isn’t named after a feature — it’s named after the place.

Why 137

The number isn’t arbitrary. 137 is the approximate inverse of the fine structure constant (α ≈ 1/137) — the dimensionless constant that governs electromagnetic coupling strength. It determines how strongly charged particles interact with electromagnetic fields.

In plain terms: it’s the fundamental constant that enables light, electricity, and all electromagnetic interaction in the universe. Without it, atoms don’t form stable orbits. Without stable atoms, chemistry doesn’t work. Without chemistry, nothing works. The fine structure constant isn’t a detail — it’s a load-bearing number at the base of physical reality.

Sector 137’s thesis — communication is gravity — isn’t a metaphor. It’s a claim about what communication is at the level of physics. The name makes it literal. Every release shipped, every stakeholder aligned, every signal sent — the product exists to wield communication as a fundamental force.

The product is named after the constant that makes communication physically possible. That’s not branding. That’s a thesis statement.

Why the Name Works

• It’s a place, not a function. Products come and go. A sector endures.
• It’s shared. The crew, the Machine, the pipeline, the workshops — they all live in Sector 137.
• It carries the dual identity naturally: the product is what operates in Sector 137, and the workshop is where Sector 137 builds custom systems.
• It sounds like something you want access to. “Welcome to Sector 137” has gravity.

Package names: @sector137/*

---

Visual Direction — The HUD Aesthetic

Mood

Iron Man’s helmet display meets the control panels of Interstellar’s Endurance. Clean holographic UI, translucent panels, soft glowing accents. Not retro — futuristic but grounded. The kind of interface designed by someone who thinks efficiency is beautiful.

---

Color System

HUD Palette

Token	Value	Usage
Void	#0A0A0F	Primary background — deep space
Hull	#14141F	Card/panel backgrounds — spaceship interior
Bulkhead	#1E1E2E	Elevated surfaces — structural elements
Grid	#2A2A3A	Borders, dividers — the wireframe of the world
Ghost	#4A4A6A	Decorative/structural only — disabled states, icons, UI chrome. Fails WCAG AA as readable text
Signal	#8A8AAA	Secondary/muted readable text — passes WCAG AA (~5.7:1 on Hull)
Lumina	#E0E0F0	Primary text — clear, bright, present
Beacon	#00FFAA	Primary accent — the signal, success, active states
Flare	#FF6B35	Warning, attention — Sal’s stress color + Kael’s identity (dual duty: when the system is stressed, Kael is usually involved)
Rift	#B44AFF	Links, interactive elements — the portal color
Pulse	#00BBFF	Info, data visualization — analytical calm
Ember	#FF4444	Error, danger — system critical
Copper	#C47F3D	Warm confidence — sales, customer, outreach

Crew Colors

Character	Color	Token	Rationale
Sal	—	He IS the HUD	The whole palette is Sal
Margot Flux	#B44AFF	Rift	Purple — portals, futures, possibilities
Kael Deepstack	#FF6B35	Flare	Orange — fire, forge, urgency
Wren Glasswork	#00FFAA	Beacon	Green/teal — growth, signal, vitality
Harlan Closer	#C47F3D	Copper	Warm, grounded, valuable, honest

---

Typography

Role	Font	Rationale
Display / Sal’s Voice	Space Grotesk	Geometric, modern, slightly futuristic without being gimmicky
Body / UI	JetBrains Mono	Monospace for the engineering context, highly legible
Data / Code	JetBrains Mono	Consistency with the engineering identity

---

HUD Design Principles

The UI should feel like it’s projected onto glass:

• Translucency over opacity. Panels should feel like they float over the void. Subtle backdrop blur, low-opacity backgrounds.
• Glowing edges, not hard borders. Borders feel like light traces, not walls. Thin, luminous, slightly soft.
• Data as starlight. Charts, graphs, and metrics feel like constellations — points of light connected by meaning.
• Micro-animations with purpose. Things don’t just appear — they materialize. A card sliding in is a system component coming online.
• Sal’s presence. Sal is felt in the UI even when he’s not speaking. His personality comes through in information architecture, transitions, error handling.

---

Visual Identity & Assets

Art Style: 2D adult animated sci-fi sitcom — flat vibrant colors, crisp thick black outlines, slightly cynical and exaggerated character design, clean vector-like animation aesthetic. Flat but cinematic lighting. This is the canonical style for all crew art.

Canonical Crew Portraits

All portraits live in apps/landing/public/. These are the definitive crew images.

Status: LIVE in product UI. As of Canon v0.8.0 Layer 2 (March 2026), crew portraits are rendered in the product dashboard — in the Universe HUD agent roster sidebar and in the dedicated Crew tab agent cards. Served from the app’s public directory as /[name]-profile.webp.

Character	File	Description
Sal	sal-profile.webp	Short dark brown hair, translucent green HUD visor over eyes, dark navy space suit with Beacon teal and Flare orange accents. Slight smirk. Holographic data panels floating behind him. Deep space background.
Margot	margot-profile.webp	Dark hair with purple highlights, sharp angular features, confident knowing smirk. Dark grey suit with Rift purple glowing piping. Bridge setting with purple holographic displays.
Kael	kael-profile.webp	Brown hair, stubble, slightly worried expression — mouth open mid-diagnosis. Orange work jumpsuit with tools in breast pocket. Engine room setting with pipes and machinery.
Wren	wren-profile.webp	Dark curly/wavy hair, dark skin, small green earring. Confident expression. Purple and dark blue suit with Beacon teal/green geometric trim. Space visible behind her.
Harlan	harlan-profile.webp	Wavy brown hair, open white shirt under blue jacket with copper/orange trim. Big warm genuine smile. Warm copper/amber background.

Environment Art

Asset	File	Description
The Black Hole	distant-bg.webp	Swirling cosmic vortex — purples, golds, deep blacks. The passage between this side and The Other Side.
The Machine / Workshop	footer-bg.webp	Garage interior with the Machine — multi-monitor station, glowing blue core, robotic arms, cables, workbench, framed crew photo.

Generating New Assets

Use the /rig:visual-prompt skill — references universe.md for character details and prompt-patterns.md for style prefix and templates.

---

How It Starts

The Orientation Protocol is the crew’s first move.

Before any work begins, the crew builds a model of the human they’re working for. Not a persona — a constraint system. 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 asks questions that sound casual but aren’t — he’s building the success picture. Sal integrates everything into a Human Profile.

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

This is what makes the relationship different from a tool. Tools serve tasks. The crew serves the human behind them.

See crew/collective.md for the full Orientation Protocol mechanics.

---

Resolved Questions

1. “Is Sal the AI?” — No. Sal is the character. AI is the engine. The product is Sal, not “an AI assistant.” This is final.
2. Multi-user dynamics. — One Sal per project. Adapts communication style per person. Same information, different rendering.
3. Sal’s relationship with AI. — Sal employs AI as one of many systems. It’s infrastructure. He doesn’t discuss it.
4. Visual representation. — Resolved. Canonical portraits exist. Sal has a face for brand while remaining “the system itself” in-product. The duality is intentional.

Deferred Questions

5. Voice acting. — Deferred. When relevant: deadpan, slightly fast, clearly amused by his own observations.
6. Easter eggs and lore delivery. — Deferred. Loading screens, achievement unlocks, hidden interactions are delivery mechanisms for when core experience is solid.