Celaya Solutions Research
Build with the lab
Celaya Solutions / Brand Identity System

Make
Coherence
Visible

Brand Guidelines v1.0

Founded El Paso, TX Identity Version 1.0.0 Primary Font JetBrains Mono Primary Color #FF6B35 Classification Internal + Partner Use
01 / Brand Philosophy

What we're
actually building

Celaya Solutions is an independent applied intelligence research lab rooted in El Paso, Texas. We build infrastructure for coherence to examine itself. Every design decision either supports that mission or it doesn't.

Coherence as Prime Function

Systems thinking is not a method here, it's the substrate. Every visual, every interaction, every word should reduce cognitive friction and increase signal clarity. If it doesn't make something more legible, it doesn't ship.

Precision Without Ceremony

Industrial-grade precision, zero bureaucratic polish. We document carefully and speak directly. The work is hard enough; the brand should not create additional overhead. Clarity is the only luxury we permit ourselves.

Border Intelligence

Born at the intersection of two cultures, two economies, two ways of thinking. We don't occupy a single lane. The brand reflects cross-domain fluency: technical precision and human warmth, rigor and invention.

Edge-of-Chaos Operations

We operate at the boundary of what is currently possible. The brand must hold its shape under entropy. Robust, not rigid. Principled, not precious. Identity that survives contact with real conditions.

Note These four principles are not marketing language. They are operational reality. Every brand decision should trace back to one of them. If it can't, reconsider it.
02 / Color System

Colorblind-safe.
High-contrast. Intentional.

Every color in this palette was selected for accessibility, legibility, and semantic weight. Nothing is decorative without purpose. The palette is designed to remain coherent under deuteranopia, protanopia, and tritanopia simulation.

Core Palette
Signal Orange
#FF6B35
Primary action, emphasis, brand anchor
Proof Green
#06D6A0
Confirmed states, code, system output
Alert Yellow
#FFBE0B
Warnings, highlights, caution states
Pure White
#FFFFFF
Primary text, foreground content
Void Black
#000000
Canvas, background, negative space
Neutral Scale
#0A0A0A
Surface 01
#111111
Surface 02
#1A1A1A
Surface 03
#242424
Border
#3A3A3A
Inactive
#6B6B6B
Muted text
#9A9A9A
Secondary text
Token
Usage Context
Never Use For
Signal Orange
Primary CTAs, active nav, brand headers, alert outlines, hover states on key elements
Body text, backgrounds, success indicators
Proof Green
System output, code syntax, success states, confirmed status, live data indicators
Error states, primary CTAs, large background fills
Alert Yellow
Warnings, pending states, highlight annotations, data spikes, caution badges
Error states, body text on white, decorative use
Pure White
All primary body text, headings on dark backgrounds, icon fills
Backgrounds, borders, low-emphasis elements
WCAG All foreground-to-background color pairings must meet WCAG AA (4.5:1 for normal text, 3:1 for large text). Signal Orange on Void Black passes at 4.6:1. Never use yellow text on white or orange on white in production interfaces.
03 / Typography

Language is
infrastructure.

Three typefaces. Each carries a distinct cognitive weight and context. JetBrains Mono is the identity anchor, reflecting our roots in code, precision, and measurable systems.

JetBrains Mono Identity / Code / Labels
ABCDEFGHIJKLMNOPQRSTUVWXYZ
abcdefghijklmnopqrstuvwxyz
0123456789 !@#$%^&*()

Used for: labels, tags, code blocks, data readouts, nav items, timestamps, hex values, all system-layer communication.
Weights in use: 300 (light data), 400 (default), 500 (labels), 700 (emphasis).

Syne Display / Headlines / Brand Voice
The Lab That Thinks
Make Coherence Visible.

Used for: page headings, hero text, section titles, marketing headers, product names.
Weights in use: 400 (subheadings), 600 (section titles), 800 (hero display). Tracking: -0.02em to -0.04em at large sizes.

DM Sans Body / UI / Prose
We build systems that make coherence visible and actionable. Based in El Paso, operating at the edge of industrial electrical infrastructure and applied intelligence research. Cross-domain by design, not by accident. Precision without ceremony.

Used for: body copy, UI labels where mono is too technical, documentation prose, descriptions, captions.
Weights in use: 300 (captions), 400 (default body), 500 (UI emphasis). Line-height: 1.6 to 1.75 for readability.

Type Scale
Display XL
Celaya
Syne 800 / 5–7rem
Display
Research Lab
Syne 800 / 2.5rem
Heading 1
Make Coherence Visible
Syne 700 / 1.75rem
Heading 2
El Paso Proof Engine
Syne 600 / 1.25rem
Body
Building infrastructure for coherence to examine itself.
DM Sans 400 / 1rem
Label
System Status / Active
Mono 500 / 0.7rem
Caption
v1.0.0 / 2026-01-01
Mono 400 / 0.6rem
Rule Minimum body text size is 14px (0.875rem) in all interfaces. No exceptions for captions, footnotes, or metadata. Readability is a core accessibility commitment, not a nice-to-have. 
/* CSS Custom Properties — paste into any Celaya project */
--font-mono:    'JetBrains Mono', monospace; /* identity layer */
--font-display: 'Syne', sans-serif;        /* brand voice */
--font-body:    'DM Sans', sans-serif;      /* communication */

--text-xs:   0.6rem;   /* 9.6px  — captions, timestamps */
--text-sm:   0.7rem;   /* 11.2px — labels, tags */
--text-base: 1rem;     /* 16px   — body */
--text-lg:   1.25rem;  /* 20px   — subheadings */
--text-xl:   2rem;     /* 32px   — section headers */
--text-2xl:  3.5rem;   /* 56px   — display */
05 / Voice and Tone

Speak like
someone who built it.

Celaya Solutions voice is direct, technical, and rooted. We earned our vocabulary in data centers, lab sessions, and city council meetings. The brand does not perform expertise. It demonstrates it.

Voice Characteristics

The water demand numbers don't match the permit data. We published the analysis. Here's what we found.

Direct. Evidence-first. No hedge.

CORTEX runs 14 agents across manufacturing ops. Built in 6 hours. Still running.

Specific. Earned confidence. No fanfare.

We don't know yet. That's why we're building the instrument.

Honest about uncertainty. Active, not passive.

This is infrastructure for communities that have been told to accept permanent problems.

Rooted. Mission-clear. Emotional without sentiment.
Never Sound Like This

We leverage cutting-edge applied intelligence solutions to empower stakeholders with actionable insights and synergistic outcomes.

Corporate filler. Zero information density.

We're so excited to announce our innovative new platform! Stay tuned for more amazing updates!

Hype without substance. Performative enthusiasm.

Please be advised that the aforementioned system may potentially facilitate certain operational efficiencies...

Over-hedged. Legal-speak in the wrong context.

As a thought leader in the applied intelligence space, we believe disruption is key to transforming the paradigm...

Credential-signaling instead of demonstrating.
Voice Attributes
Attribute What It Means What It Does Not Mean
Direct Lead with the finding. No preamble. No softening when clarity matters more. Blunt without empathy. Dismissing nuance.
Precise Use the specific word. Name the number. Date the claim. Version the system. Technical jargon as gatekeeping. Precision for its own sake.
Rooted El Paso is not background detail. It's the operating context. Reference it with intent. Localism as a marketing angle. Fabricated authenticity.
Curious We're building instruments, not products. The brand reflects genuine inquiry. Performed wonder. Optimism detached from reality.
Honest Name the unknowns. Acknowledge limitations. The work is documented, not spun. Self-deprecation as humility performance. Hiding real capability.
Em dash rule No em dashes in any Celaya Solutions content. Use colons, commas, periods, or parentheses. This applies to all public-facing copy, documentation, code comments, and internal communications. Enforce it in linters, templates, and review checklists.
06 / Component Library

Reusable parts.
Consistent signal.

All UI components derive from the same four properties: dark background, high-contrast text, orange as the primary activation color, mono type for system-layer communication. Deviations require explicit justification.

Buttons — Primary / Secondary / Ghost
Active Verified Pending Archived
Status Tags / Badges
Text Inputs
Info Hash anchored to Solana devnet.
Warn Signature mismatch detected.
Callouts / Alert Banners
hash: sha256
chain: solana-devnet
ts: 1706745600
Code Blocks / Data Readouts
CORTEX / Agent Status
SENTINEL
● Online — 14 agents active
Data Cards / Agent Panels
Motion System

Motion confirms state, not spectacle. Every animation should answer: does this help the user understand what just happened? If no, remove it. Hover over cards below to preview.

Slide In
0.4s cubic-bezier(0.4, 0, 0.2, 1)
Fade Scale
0.3s ease-out
Spring Pop
0.5s cubic-bezier(0.175, 0.885, 0.32, 1.275)
Spacing Scale
space-1
4px
space-2
8px
space-3
12px
space-4
16px
space-6
24px
space-8
32px
space-12
48px
space-16
64px
space-20
80px
Grid System
12-column / Max-width 1100px / Gutter 24px / Side padding 40px
1
2
3
4
5
6
7
8
9
10
11
12
Data Visualization Standards
Grid Surplus vs Demand — EP44 Corridor (Illustrative)
Demand
Surplus
197%Q1
100%Q1
164%Q2
100%Q2
184%Q3
100%Q3
211%Q4
100%Q4
Rule Data visualizations always use the core palette only: orange for primary metric, green for confirmation/baseline, yellow for warnings/outliers. Never use gradients on data series. Axes must be legible at 1x scale. All charts must be colorblind-tested before publishing.
07 / Accessibility

Coherence is
for everyone.

The EPPE was built specifically for communities without institutional access. Accessibility is not a compliance checkbox. It's the mission made operational. Every interface ships WCAG AA minimum.

White on Black
21:1 AAA
Orange on Black
4.6:1 AA
Green on Black
8.6:1 AAA
Yellow on Black
12.7:1 AAA
Gray on Black
3.2:1 AA lg
Requirement Target Scope
Contrast (text) 4.5:1 min All interfaces
Contrast (large text) 3:1 min All interfaces
Touch target size 44px min Mobile
Focus indicators 2px orange ring All interactive
Motion (reduced) prefers-reduced-motion All animations
Font size minimum 14px All text
Alt text All non-decorative All images
Keyboard nav Full coverage All interactive
08 / Exceptional Behavioral Standards

How Celaya
Solutions behaves.

Brand identity is not only visual. It's the pattern of decisions we make when no guidelines specify. These are the non-negotiable behavioral commitments that define Celaya Solutions in practice.

01 / Credibility
Evidence Before Claims
We publish the analysis before the press release. Every public statement links to the underlying data, hash, or methodology. Sealed Envelope Protocol: hash before publish. No claim exists without its proof.
02 / Privacy
Identity Protection by Default
Sources, collaborators, and community members are identified by initials or variables only in all public content. No backdoors to individuals. Same ethic Apple applies to encryption, applied to human identity.
03 / Ownership
IP Documented in Real Time
All significant builds are timestamped, versioned, and anchored. GitHub commit history is evidence. Solana blockchain is witness. We operate with the assumption that what we build has value and document accordingly.
04 / Access
No Sign-Up, No Tracking
EPPE and civic tools ship with no accounts, no analytics, no third-party tracking. Photos never leave the device. Coherence infrastructure for communities that have been surveilled enough already.
05 / Community
El Paso as Operating Context
We don't describe El Paso as an "underserved market." It's home. Every civic tool is designed for actual people we know with actual problems we've watched persist for decades. The work is personal before it's professional.
06 / Research
Surprise Over Market Fit
Research instruments optimize for discovery, not conversion. We build things to find out what happens. If it turns into a product, fine. If it turns into a paper, fine. The lab exists to extend what's knowable, not what's sellable.
07 / Consistency
Systems Speak, Not Silos
31+ instruments share a visual language, naming convention, and architecture philosophy. CORTEX, CLOS, MORTEM, EPPE, and Project Jupiter look like they came from the same mind because they did. The brand is the connective tissue.
08 / Communication
Direct First, Diplomatic Always
We say the thing. We don't bury a finding in hedges. We don't soften a data discrepancy with marketing language. We can be warm and still be precise. We can be direct and still be respectful. Both, always.
09 / Integrity
Version What You Change
If a document, system, or claim changes, it gets a version number and a changelog. We don't silently edit history. If we were wrong, we say so explicitly. Integrity is the minimum viable trust infrastructure.
09 / Naming Conventions

Names as
cognitive anchors.

Product and system names in the Celaya Solutions ecosystem follow patterns that signal function, scope, and intent. Names are chosen to be memorable, typeable in code, and pronounceable in conversation.

Pattern Examples Use For Convention
Single Word / Acronym CORTEX, CLOS, EPPE, MORTEM, SIGNAL Core platforms and research instruments ALL CAPS, noun, evokes function
Code Name Project Jupiter, Operation Meridian Civic research and multi-phase initiatives Title Case, "Project" prefix optional
Agent Names SENTINEL, WATT, COMPASS, RACHEL, Juniper Individual applied intelligence agents within a system ALL CAPS or Title Case, role-evocative
Feature / Protocol Sealed Envelope Protocol, Proof Engine Named technical methods or civic standards Title Case, noun phrase
Personal Brand C-Cell, Ghost, Celaya Chain Protocol Creative and public persona work Mixed; align with context
Critical In all public-facing content, never reference personal identifiers beyond initials or established public names. This applies to all documentation, social posts, civic submissions, and partner materials. Protect collaborators and sources with the same rigor applied to the EPPE's no-tracking architecture.
10 / Document Standards

Everything that
ships gets versioned.

All Celaya Solutions documents, systems, and public communications follow consistent versioning and metadata standards. If you edited it, version it. If you published it, hash it.

Version
Date
Changes
Status
v1.0.0
2026-01-01
Initial brand guidelines release. Full color, type, logo, voice, and component system.
Current
Document Metadata Standard


Document:    [Full Title]
Version:     v1.0.0
Author:      Celaya Solutions
Contact:     hello@celayasolutions.com
Date:        YYYY-MM-DD
SHA256:      [hash of canonical content]
Chain:       solana-[mainnet|devnet]
Tx:          [transaction signature if anchored]
License:     All Rights Reserved / Celaya Solutions
Content Type Format Hash Required Archive Location
Civic research / data analysis HTML (GitHub Pages) Yes — Sealed Envelope Protocol celaya-solutions GitHub org
Technical documentation Markdown / Notion Recommended Internal repo + Notion
Legal / IP documentation PDF + DOCX Yes Encrypted storage + attorney
Public social content Platform native Optional Screenshot archive
Brand guidelines (this doc) HTML Yes celaya-solutions/brand