# The Atlas Ecosystem — Section Design Reference

Schema: Design Details SECTION.md v3.2
Source: https://atlasmotion.com/
Website: Atlasmotion
Section ID: 72b2a13a-badf-40a9-b0d5-ec7c8b286ad7
Status: deterministic evidence partially captured; editorial AI review pending

## Purpose

This is a process section on the Home page. Use the attached crop and measured browser facts to reconstruct its composition. Do not infer unmeasured source values.

## Layout

captured layout

## Visual signature

photographic, typographic, corporate, cinematic, technical-schematic treatment at 1440×1156px. The crop spans 12104–13260px of a 14619px page.

## Components

- Navigation Bar
- Hero With Background Imagery
- Primary Button
- Outline Button
- Footer
- Carousel
- Scroll Driven Narrative Sequence
- Persistent Grid Overlay

## Evidence note

The geometry, typography, colors, media, and animation parameters below come from saved HTML/CSS/browser evidence when present. Website-level roles are supplied separately. Editorial section judgment remains pending unless the MCP resolves this source ID to a promoted canonical record.

## Build blueprint v3.2

### Purpose and classification

- Canonical type: process
- Source type: process
- Structure: captured layout
- Layout: captured layout
- Styles: photographic, typographic, corporate, cinematic, technical-schematic
- Components: Navigation Bar, Hero With Background Imagery, Primary Button, Outline Button, Footer, Carousel, Scroll Driven Narrative Sequence, Persistent Grid Overlay
- Purpose: process section from the Home page of Atlasmotion.
- Visual signature: Captured visual surface with captured layout. Inspect the crop for image and content hierarchy.

### Crop and composition

- Crop: 1440×1156px; aspect ratio 1.246:1
- Page bounds: 12104–13260px of 14619px
- Guidance: Preserve the documented hierarchy and relationships; exact measurements were not deterministically captured.

### Exact typography evidence

The sectionScale values were measured inside this crop. The siteRoles values explain how those faces function across the source website; they must not replace section measurements.

```json
{
  "sectionScale": [],
  "siteRoles": [
    {
      "role": "display",
      "size": "150px",
      "family": "SuisseIntl",
      "source": "computed",
      "traits": "Regular",
      "weight": "500",
      "evidence": "font-6: computed CSS at 1440×1000; AI role: SuisseIntl at 150px, used for massive background text or large section headers.",
      "sampleId": "font-6",
      "confidence": 0.9,
      "lineHeight": "165px",
      "letterSpacing": "-4.5px"
    },
    {
      "role": "heading",
      "size": "64px",
      "family": "SuisseIntl",
      "source": "computed",
      "traits": "uppercase",
      "weight": "500",
      "evidence": "font-4: computed CSS at 1440×1000; AI role: SuisseIntl at 64px, used for primary statement text like 'THE PHYSICAL LAYER...'.",
      "sampleId": "font-4",
      "confidence": 0.9,
      "lineHeight": "58px",
      "letterSpacing": "-1.9px"
    },
    {
      "role": "body",
      "size": "24px",
      "family": "SuisseIntl",
      "source": "computed",
      "traits": "Regular",
      "weight": "500",
      "evidence": "font-7: computed CSS at 1440×1000; AI role: SuisseIntl at 24px, used for standard paragraph text describing processes.",
      "sampleId": "font-7",
      "confidence": 0.85,
      "lineHeight": "28px",
      "letterSpacing": "-0.7px"
    },
    {
      "role": "mono",
      "size": "14px",
      "family": "SuisseIntl",
      "source": "computed",
      "traits": "uppercase",
      "weight": "500",
      "evidence": "font-2: computed CSS at 1440×1000; AI role: SuisseIntl at 14px uppercase, used for UI labels, navigation, and structural markers.",
      "sampleId": "font-2",
      "confidence": 0.8,
      "lineHeight": "14px",
      "letterSpacing": "normal"
    }
  ]
}
```

### Exact color evidence

The section samples record where each computed value was used. Functional roles come from the website-level classifier and remain separate.

```json
{
  "sectionUsage": [],
  "functionalPalette": [
    {
      "hex": "#FFFDE0",
      "name": "text",
      "role": "text",
      "source": "computed",
      "evidence": "color-2: computed rgb(255, 253, 224); AI role: Off-white (#FFFDE0) used extensively for primary text, wireframes, and grid lines against dark backgrounds.",
      "sampleId": "color-2",
      "confidence": 0.95
    },
    {
      "hex": "#181818",
      "name": "canvas",
      "role": "canvas",
      "source": "computed",
      "evidence": "color-1: computed rgb(24, 24, 24); AI role: Very dark gray (#181818) used as the background color for technical and footer sections.",
      "sampleId": "color-1",
      "confidence": 0.9
    },
    {
      "hex": "#121211",
      "name": "primary action",
      "role": "primary-action",
      "source": "computed",
      "evidence": "color-4: computed rgb(18, 18, 17); AI role: Near black (#121211) used as the background for the primary CTA button.",
      "sampleId": "color-4",
      "confidence": 0.8
    }
  ]
}
```

### Design tokens

```json
{
  "radius": "Buttons and structural elements do not show measurable border-radius, maintaining sharp edges.",
  "density": "The layout is sparse and airy, prioritizing the background imagery and scroll animations, with text elements appearing in isolated blocks.",
  "evidence": "DOM data shows font-1 through font-5 mostly sizes 12-14px for UI elements alongside large 64px/150px headings. The grid lines and sharp UI elements confirm the technical aesthetic.",
  "borderStyle": "Thin, semi-transparent light lines (e.g., color-3) are used to draw the structural grid across the entire canvas.",
  "buttonStyle": "Buttons are typically sharp rectangles, either solid dark fills or outline styles with small, tight uppercase typography.",
  "cornerStyle": "Sharp corners are dominant, aligning with the technical grid aesthetic.",
  "contentWidth": "Content often spans the full width of the viewport (edge-to-edge imagery), while text blocks are contained within specific columns of the overlay grid.",
  "spacingRhythm": "Content is positioned against a persistent structural grid overlay, with large gaps between distinct scroll chapters to allow for animation sequences."
}
```

### Reconstruction specification

This is the implementation contract for the captured desktop viewport. Prefer section-specific facts here over general website descriptions.

- Root container was not deterministically isolated.
- Layout containers: 0; cards/surfaces: 0; media elements: 0; browser animations: 0.

#### Container, grid, and spacing

```json
{
  "viewport": {
    "width": null,
    "captureBounds": null
  },
  "container": null,
  "spacing": {
    "observedGapsPx": [],
    "representativeContentWidthsPx": []
  },
  "columns": []
}
```

#### Cards and surfaces

```json
{
  "cards": [],
  "surfaces": null
}
```

#### Media treatment

```json
[]
```

#### Browser-exposed animation parameters

```json
[]
```

### Measured geometry, surfaces, media, and animation

These raw values come from the saved element map and computed styles. Empty arrays mean the fact was not captured; they are not permission to invent source values.

```json
null
```

### Observed motion

No timestamped authored motion is attached. Use only restrained baseline transitions.

The browser animation records above are deterministic parameters captured from active browser animations. The timestamped observations describe what Gemini saw in the video. Treat them as complementary evidence. When either source is empty or they conflict, state the uncertainty instead of inventing timing or easing.

### Responsive contract

- Measured viewport: unknownpx wide.
- Mobile/tablet values: not measured by this section evidence unless a separate capture is explicitly listed.
- Preserve hierarchy and sequence; collapse simultaneous columns only where needed, maintain media aspect ratios, and verify touch targets and text wrapping at target breakpoints.

### Structure versus visual skin

- Preserve: content hierarchy, layout relationships, section rhythm, interaction purpose.
- Adapt: brand colors, font family, copy, imagery, icons, decorative details.
- Rule: Preserve the observed design logic while creating original branding, copy, assets, and implementation details.

### Adaptation and dependencies

- Effort: Not assessed
- What transfers: Documented hierarchy and composition
- Dependencies: None recorded
- Guidance: Adapt the pattern to the new product and content.

### Evidence readiness

- Coverage: 5/7
- Can build: Yes
- Missing facts: section-specific computed typography and color samples; section-level geometry, surfaces, media treatment, and animation parameters; timestamped authored motion
- Warning: Buildable with adaptations for these unsupported facts: section-specific computed typography and color samples; section-level geometry, surfaces, media treatment, and animation parameters; timestamped authored motion.

### Agent implementation prompt

Create an original process section inspired by the design evidence titled “The Atlas Ecosystem”.

Purpose: process section from the Home page of Atlasmotion.

Structure: captured layout. Source layout label: captured layout. Preserve the documented hierarchy and relationships; exact measurements were not deterministically captured.

Visual signature to preserve at the pattern level: Captured visual surface with captured layout. Inspect the crop for image and content hierarchy.

Components: Navigation Bar, Hero With Background Imagery, Primary Button, Outline Button, Footer, Carousel, Scroll Driven Narrative Sequence, Persistent Grid Overlay.

Style direction: photographic, typographic, corporate, cinematic, technical-schematic.

Observed crop: 1440×1156px (1.246:1). Treat this as evidence of composition, not a mandatory output size.

Typography evidence: {"role":"display","size":"150px","family":"SuisseIntl","source":"computed","traits":"Regular","weight":"500","evidence":"font-6: computed CSS at 1440×1000; AI role: SuisseIntl at 150px, used for massive background text or large section headers.","sampleId":"font-6","confidence":0.9,"lineHeight":"165px","letterSpacing":"-4.5px"} {"role":"heading","size":"64px","family":"SuisseIntl","source":"computed","traits":"uppercase","weight":"500","evidence":"font-4: computed CSS at 1440×1000; AI role: SuisseIntl at 64px, used for primary statement text like 'THE PHYSICAL LAYER...'.","sampleId":"font-4","confidence":0.9,"lineHeight":"58px","letterSpacing":"-1.9px"} {"role":"body","size":"24px","family":"SuisseIntl","source":"computed","traits":"Regular","weight":"500","evidence":"font-7: computed CSS at 1440×1000; AI role: SuisseIntl at 24px, used for standard paragraph text describing processes.","sampleId":"font-7","confidence":0.85,"lineHeight":"28px","letterSpacing":"-0.7px"} {"role":"mono","size":"14px","family":"SuisseIntl","source":"computed","traits":"uppercase","weight":"500","evidence":"font-2: computed CSS at 1440×1000; AI role: SuisseIntl at 14px uppercase, used for UI labels, navigation, and structural markers.","sampleId":"font-2","confidence":0.8,"lineHeight":"14px","letterSpacing":"normal"}

Color evidence: {"hex":"#FFFDE0","name":"text","role":"text","source":"computed","evidence":"color-2: computed rgb(255, 253, 224); AI role: Off-white (#FFFDE0) used extensively for primary text, wireframes, and grid lines against dark backgrounds.","sampleId":"color-2","confidence":0.95} {"hex":"#181818","name":"canvas","role":"canvas","source":"computed","evidence":"color-1: computed rgb(24, 24, 24); AI role: Very dark gray (#181818) used as the background color for technical and footer sections.","sampleId":"color-1","confidence":0.9} {"hex":"#121211","name":"primary action","role":"primary-action","source":"computed","evidence":"color-4: computed rgb(18, 18, 17); AI role: Near black (#121211) used as the background for the primary CTA button.","sampleId":"color-4","confidence":0.8}

No section-bounded typography samples were measured.

No section-bounded color samples were measured.

No saved element-map measurements were available; do not invent exact source spacing, card, media, or animation values.

Do not invent signature motion. Use only restrained baseline transitions if the product needs them.

Transfer the documented hierarchy and composition rather than source copy or assets.

No explicit dependencies were recorded.

Adapt the pattern to the new product and content.

Use new copy, imagery, branding, and implementation details. Do not reproduce the source website or its proprietary assets.
