# THE ENIGMA FIELD
## Brand field guide · Version 1.0

**Draft working manual.** The connected amorphous, irregular multi-lobed teal point-cloud direction is approved. Supporting typography, color roles, layout, motion, clear space and small-use rules are proposed v1 working standards. The supplied logo files are raster references; no final vector master is available.

## 01 · Foundation

A strategic and technical studio building intelligent digital ecosystems for visionary and consciousness-led work.

**Positioning:** We take deeply specific human genius and build the digital field through which it can be understood, experienced, and shared at scale.

The exploration between technology and consciousness is core to the studio. We consider how intelligent systems can extend human possibility without flattening the people, ideas and practices they serve. This is not solely an agency or infrastructure proposition.

**Promise:** “We do not change your magic. We build the field that can hold it.”

**Invariant:** Protect what is generative while reducing what is arbitrary.

### The name
- **Enigma:** the distinctive gift or body of work that resists easy explanation. A depth to understand, not a problem to simplify away.
- **Field:** the connected environment of brand, systems, experiences, relationships and technology that allows the work to reach others.

### The method
1. **Unearth the Enigma:** listen, discover the work's essential character, and name the invariant that must remain intact.
2. **Engineer the Field:** give that character a coherent brand, experience and technical foundation, with AI and automation serving a clear purpose.
3. **Create Interconnection:** launch, listen to feedback and refine through use and real relationships.

### Service pillars
- **Clarity:** positioning, offer architecture, strategic direction, experience mapping
- **Expression:** brand identity, narrative, web design, digital storytelling
- **Intelligence:** AI agents, knowledge systems, thoughtful human-in-loop tools
- **Flow:** automation, onboarding, operations, connected client journeys
- **Reach:** launch, distribution, sustainable digital expansion

## 02 · Logo and usage

The connected node is one amorphous, irregular, multi-lobed form. Its identity comes from the relationship between its parts, not perfect geometry. Preserve the supplied silhouette and proportions.

- Use the **point-cloud raster** at large display scale, with strong contrast and uninterrupted space.
- Use the **flat raster symbol** for compact applications. Proposed minimum: **32px** in digital use. This has not completed optical testing; it is not a claimed production guarantee.
- Proposed clear space: **one quarter of the symbol's width on every side**, measured from visible bounds. Keep type, edges and other marks outside this boundary.
- The full concept study is the reference for the exact **THE ENIGMA FIELD** wordmark. Ordinary typeset brand text is not a substitute logo.
- Never distort, recolor, rearrange, regenerate, outline or add new glows and shadows to the master reference.
- Do not trace or present a generated SVG as an official vector master. Avoid enlarging raster images beyond useful resolution.

Assets:
- [Connected point cloud — WEBP](assets/connected-node.webp)
- [Flat transparent symbol — PNG](assets/connected-node-symbol.png)
- [Full concept and wordmark study — PNG](assets/connected-node-concept.png)

## 03 · Color

Primary teal is sampled from the mark. The supporting role system is a v1 proposal.

| Token | Hex | Use |
|---|---|---|
| color.ink | #050708 | Main dark background |
| color.panel | #0B1012 | Quiet inset surface |
| color.teal | #96FCEA | Primary accent and text on dark |
| color.ivory | #F4F7F7 | Primary text and light surface |
| color.muted | #A5B6B5 | Secondary text on dark |
| color.tealDark | #12685B | Accent text on ivory |
| color.line | #293738 | Decorative structural rules |

Dark surfaces dominate; use teal sparingly for the mark, emphasis and functional states. Do not set light teal text on ivory. Use dark teal instead. Never convey meaning by color alone. Target 4.5:1 body text contrast and 3:1 for large text and meaningful interface boundaries. Digital values are not approved print conversions.

## 04 · Typography

These local stacks are proposed working standards, not a finalized wordmark specification:
- **Display:** `"Avenir Next", Avenir, "Segoe UI", sans-serif`. Weights 500–600, short lines, generous space. Hero size 48–88px; leading 1.02–1.15.
- **Reading:** `-apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif`. Base 16px, leading 1.7, weights 400–600, reading measure near 68 characters.
- **Specification:** `"SFMono-Regular", Consolas, "Liberation Mono", monospace`. 12–14px for labels, code and technical reference, never long prose.

Scale: **12 / 14 / 16 / 20 / 28 / 40 / 64 / 88px**. Display tracking around -0.04em; no tracked body copy. Fallback fonts change the appearance across operating systems. Do not alter letterforms to simulate a wordmark. Localized typography remains to be reviewed.

## 05 · Layout and interface

Structure is a form of care. Give each surface one primary task and each element a reason to exist.

- Use a **4px spacing unit**: 4, 8, 12, 16, 24, 32, 48, 64, 96, 128px.
- Readable content maximum: **1120px**; body copy about **68ch**. Fluid gutters: **24–72px**.
- This manual uses a **248px** desktop contents rail, reduced to **220px** on compact desktops. At **800px** it becomes mobile navigation; at **540px** paired content stacks.
- Section spacing: **96px desktop / 64px mobile**.
- Use flat ink, quiet panels and fine **1px** rules. General radius **2px**; the illustrative app-icon tile uses **24px**. No elevation shadows or glass effects.
- Keep dots and point-cloud textures away from text surfaces. Whitespace carries hierarchy; avoid repetitive decorative cards.
- Actions use explicit verbs. Keyboard focus stays visible. Native controls, logical headings and semantic landmarks precede visual polish.
- On small screens, reflow the story rather than shrinking the desktop. Public reading and navigation work without JavaScript.

## 06 · Imagery and motion

Choose imagery that reveals relationships: human practice in context, material details of an idea, and intelligible systems. Use simple crops, a clear focal point and accurate captions. Respect consent and authorship.

Avoid generic robots, mystical stock imagery, decorative dashboards and unrelated glowing networks. Do not present generated likenesses or fictional documentary imagery as real.

Motion is functional: **160–240ms**, easing **cubic-bezier(0.2, 0, 0, 1)**. Use it to clarify state changes, not to perform novelty. Any future ambient drift must be very slow, optional and disabled under reduced motion. The mark remains still in this manual. Reduced motion removes transitions and smooth scrolling.

## 07 · Voice

1. **Expansive without being vague:** open possibility and explain what it means in practice.
2. **Grounded without being reductive:** make the idea understandable without stripping away character.
3. **Technical without fetishizing technology:** explain what a system enables and who retains control.
4. **Spiritually literate without claiming certainty:** respect lived experience without presenting metaphysical belief as established fact.
5. **Clear about what we know:** distinguish known, provisional and imagined.
6. **Protective of the human:** preserve agency, authorship, privacy and dignity.

### Illustrative copy pairs — not additional brand slogans

**Instead of:** “We unlock limitless potential with revolutionary AI.”

**Write:** “We connect the tools around your work so you can spend less time moving information between them.”

**Instead of:** “Our technology elevates your consciousness.”

**Write:** “We explore how technology can support attention and intentional practice, without claiming to define the experience.”

**Instead of:** “This system will transform your business.”

**Write:** “This is a proposed approach. We'll test it with the people using it before expanding its role.”

### Vocabulary

Prefer: build the field; illuminate the work; hold the complexity; intelligent infrastructure; conscious technology; connected ecosystem; distinctive human genius; scale without dilution.

Use “magic,” “energy” and “digital alchemy” sparingly, where the context earns them. They must not stand in for explanation.

## 08 · Applications

The web guide includes real HTML/CSS specimens, not live projects, approved templates or client work:

- **Website opening:** “Intelligent systems. Distinctively human work.” One opening thought, a clear studio description and one meaningful next step. This is illustrative application copy, not an additional approved slogan.
- **Proposal cover:** “Engineer the Field.” Ivory surface, dark text, dark teal accents, generous margins and visible service-pillar structure.
- **App icon:** the supplied flat symbol centered in a dark tile. Preserve clear space and undertake optical testing before production at small sizes.

## 09 · Downloads

- [Primary point-cloud raster](assets/connected-node.webp)
- [Flat transparent raster](assets/connected-node-symbol.png)
- [Full concept study](assets/connected-node-concept.png)
- [Working JSON tokens](tokens.json)
- [Implementation design contract](DESIGN.md)

No final vector master is included or implied.

## 10 · Governance

**Version 1.0 / Draft working manual.** The brand name and connected point-cloud direction are approved. The exploration of technology and consciousness is central. Supporting standards remain proposals.

Before production, resolve final vector artwork, wordmark specifications, optical size tests, production lockups and print color values. Do not invent substitutes to fill these gaps.

When adapting, start with the invariant. Preserve the mark and the character of the work. Document the proposed change and seek brand-owner approval before treating it as a new standard. Downloaded files reflect this edition; revisit the living guide before production.

**Protect what is generative while reducing what is arbitrary.**