Align SignalGrid branding to runtime decision-layer positioning

README.md

@@ -12,6 +12,16 @@
 - **Who we serve:** Regulated and high-consequence frontline organizations.
 - **Why it matters:** Better risk control, operational resilience, productivity, and accountability without workflow-breaking friction.
 
+## Brand and presentation direction
+
+SignalGrid branding is being aligned to a premium enterprise style that matches the current product framing:
+
+- Warm charcoal foundations, off-white typography, and muted teal accents
+- Minimal, architectural visuals with restrained risk-state colors
+- Runtime decision-layer positioning (not a generic identity/security dashboard)
+
+See [docs/BRAND_SYSTEM.md](docs/BRAND_SYSTEM.md) and [startup/branding/brand.md](startup/branding/brand.md) for current guidance.
+
 ## The problem we solve
 
 Shared and mobile devices in hospitals, warehouses, and other regulated environments are often used by multiple people across shifts and locations. Traditional controls often assume static trust, creating operational and security gaps between identity, device posture, context, and enforcement.

docs/BRAND_SYSTEM.md

@@ -0,0 +1,88 @@
+# SignalGrid Brand System
+
+## Positioning Line
+
+**SignalGrid is a runtime decision layer for Zero Trust orchestration in shared and mobile frontline environments.**
+
+## Tone
+
+- Serious, calm, and operationally credible
+- Clear and precise over promotional language
+- Enterprise-forward without jargon inflation
+- Confident while respecting MVP/demo claim boundaries
+
+See [Claim boundaries](./CLAIM_BOUNDARIES.md) for allowed and disallowed language.
+
+## Visual Principles
+
+1. **Architectural clarity** — structured layouts, clear information hierarchy.
+2. **Minimal surface noise** — remove decorative clutter.
+3. **Trust through restraint** — premium style via proportion, contrast, and spacing.
+4. **Decision-centric emphasis** — visual focus aligns to trust outcome and context.
+
+## Color Palette
+
+### Core Palette
+
+| Role | Token | Hex |
+|---|---|---|
+| Primary background | Warm Charcoal 950 | `#15181B` |
+| Secondary background | Warm Charcoal 900 | `#1D2226` |
+| Primary text | Off-White 100 | `#F3F1EC` |
+| Secondary text | Off-White 300 | `#D8D4CC` |
+| Brand accent | Muted Teal 500 | `#4F8C87` |
+| Accent hover | Muted Teal 400 | `#6FA7A1` |
+
+### Functional State Palette
+
+| State | Hex | Guidance |
+|---|---|---|
+| Allow | `#5E8F73` | Positive/compliant outcomes |
+| Review / Step-up | `#B08B57` | Elevated trust checks or caution |
+| Deny | `#A15B5B` | Risk-critical or blocked outcomes |
+| Neutral border | `#2A3136` | Dividers and low-emphasis boundaries |
+
+## Typography Guidance
+
+- **Primary:** Inter (400, 500, 600, 700)
+- **Secondary:** IBM Plex Sans for technical callouts and dense integration snippets
+- Use sentence case for UI copy and section headings
+- Keep line lengths readable (roughly 60–90 characters where possible)
+- Avoid futuristic display fonts or novelty typefaces
+
+## Logo Direction
+
+Primary path:
+- Abstract S/G monogram or decision-core symbol
+- Geometric, minimal, and scalable
+- Strong negative-space behavior
+
+Constraints:
+- Must work at favicon sizes
+- Must work in monochrome
+- Must avoid shield, padlock, badge, or clichéd cyber icon language
+
+## What to Avoid
+
+- Neon cyberpunk color treatments
+- Generic “security dashboard” motifs
+- Shield/badge/lock logo clichés
+- Overclaiming “production-ready” status in visual captions or marketing copy
+- Visual inconsistency between repo docs, demo views, and website surfaces
+
+## Repo / Website / Demo Usage Rules
+
+### Repository docs
+- Keep positioning consistent: runtime decision layer + orchestration.
+- Use safe claim language consistent with MVP/demo boundaries.
+- Prefer clean diagrams over decorative marketing graphics.
+
+### Website and landing pages
+- Lead with problem-to-outcome narrative for frontline environments.
+- Emphasize deterministic decisions and auditable context.
+- Avoid promises about compliance or production SLAs without validation.
+
+### Demo visuals
+- Keep overlays and labels minimal and enterprise-readable.
+- Highlight decision inputs and resulting actions clearly.
+- Label simulated elements as simulated where applicable.