# Minimal Status Footer

Schema: Design Details SECTION.md v3.2
Website: Orchid
Source: https://orchid.ai/
Source section IDs: 88d4ec78-516d-4ffe-b695-e3228ef4f88c
Status: AI analysed; vocabulary promotion is automated

## Builder's note

What makes it work:
- The brand block and links split cleanly: logo and a green status dot sit left, small link columns sit right, so the eye finds both at once.
- A two-tier type hierarchy, a serif wordmark over small sans link labels, keeps everything legible with almost no decoration.
- Generous 120px padding on all sides and an off-white canvas with dark navy text give the footer calm, quiet breathing room.

What a screenshot can't show:
- The recording shows only the page scrolling to the footer (about 22s to 28s); there is no hover or state-change motion, and no browser animations were detected.
- Measured link text is 18px at weight 500, with 18px line height, -0.2px letter spacing, and 8px gaps between items.

Borrow: Put one small live signal, like a status dot, beside the logo to add trust and life to an otherwise plain footer.
Leave alone: Don't copy the Louize serif wordmark, the exact navy and blue palette, or the specific status wording; use a free serif such as Cormorant or Newsreader and your own colors.

## Classification

- Type: footer
- Layout: Logo and status indicator aligned left, with multiple columns of small text links aligned right.
- Styles: minimal
- Confidence: 98%

## Purpose and structure

A very clean, sparse footer displaying a system status indicator alongside standard navigational links.

Visual signature: Sparse layout with a prominent green dot indicating system status next to the logo.

## Components

- Brand logo
- System status indicator
- Navigation link columns

## Typography

- Display: louize — 64px 500
- Heading: louize — 28px 400
- Body: lausanne — 16px 400

## Functional palette

- Canvas: canvas #FCFCFD
- Text: text #08152E
- Accent: accent #0A84FF

## Motion evidence

- 22.0–28.0s — The scroll reaches the bottom of the page revealing the footer. (95% confidence)

## Section quality

Overall: 56.29/100 (Competent)
Scored coverage: 85%

- Typography: 58 — Simple two-tier hierarchy: serif logo wordmark and small sans-serif link labels/headers. Clean and legible but a generic utility pattern with no distinctive typographic treatment beyond the site's standard fonts. Next tier: No typographic personality or hierarchy variation beyond size; would need distinctive treatment of column headers or status text to progress.
- Composition: 56 — Simple left-aligned brand/status block against right-aligned three-column link grid, generous whitespace. Functional and tidy but a very common footer layout with no compositional tension or unique arrangement. Next tier: Needs an unexpected structural choice (asymmetry, grouping, scale shift) to move past a standard utility grid.
- Motion: inconclusive — Only motion evidence is scroll reaching the footer; no specific timestamped interactive or state-change motion is described. Next tier: Need documented hover, link, or status-dot animation specifics to assess motion quality.
- Content: 55 — Status indicator plus standard navigation links integrate cleanly but content is purely utilitarian with no narrative or brand voice beyond the status message. Next tier: Would need content that does more than list links, e.g., supplementary brand statement or contextual info tied to status.
- Originality: 52 — A green status dot next to the logo is a mildly distinctive touch, but the overall layout is a conventional minimal footer seen across many SaaS sites. Next tier: Requires a more unusual structural or interactive idea beyond the status-dot detail to feel hard to substitute.
- Adaptability: 60 — Clear separable structure (logo/status block vs. link columns) with explicit spacing and color tokens, making skinning straightforward. Next tier: Lack of animation/interaction specs limits how confidently behavior could be separated from skin.

Strengths:
- Clean, legible column structure for navigation links
- Subtle status indicator adds a small functional detail

Weaknesses:
- Generic three-column footer layout common across SaaS sites
- No distinctive typographic or color treatment
- Lacks any documented interactive motion

Why it does not reach the next tier: The section is tidy and well-organized but relies entirely on a familiar footer pattern without any distinguishing structural, typographic, or motion detail that would elevate it beyond competent execution.

## Adaptation guidance

- Effort: Low
- Guidance: Reusable as a generic footer template; swap logo, link groups, and accent color while keeping the status indicator pattern for any site needing a system-status footer.

What transfers:
- Left-aligned brand/status block paired with right-aligned multi-column link grid
- Small live status indicator pattern

Dependencies:
- Specific font pairing (serif logo, sans-serif body)
- Exact color tokens for status dot and text

## Living vocabulary

- No reusable vocabulary candidates were supported by this section.

Only terms with status `active` enter the public taxonomy. Deferred and proposed terms remain available to later AI passes; rejected terms remain as provenance so they are not repeatedly reinvented.

## Provenance and limitations

- Section boundaries and naming: Gemini Pro visual observation
- Motion observations: Gemini Pro direct-video analysis
- Quality judgment: Claude
- Exact design facts: browser/CSS extraction at website scope
- Rubric: Design Details section rubric 3.2 (Typography 20%, Composition 20%, Motion 15%, Content 15%, Originality 15%, Adaptability 15%)
- No motion timestamps for interactive states
- No deterministic data on hover or link transition behavior

## Usage guidance

Use this section as design evidence. Create an original implementation; do not reproduce the source copy, assets, or proprietary composition exactly.

## Build blueprint v3.2

### Purpose and classification

- Canonical type: footer
- Source type: footer
- Structure: Logo and status indicator aligned left, with multiple columns of small text links aligned right.
- Layout: Logo and status indicator aligned left, with multiple columns of small text links aligned right.
- Styles: minimal
- Components: Brand logo, System status indicator, Navigation link columns
- Purpose: A very clean, sparse footer displaying a system status indicator alongside standard navigational links.
- Visual signature: Sparse layout with a prominent green dot indicating system status next to the logo.
- Place on the page: 7 of 7, after Call to action (`orchid-ai:cta_photographic_card`)

### Crop and composition

- Crop: 1200×468px; aspect ratio 2.564:1
- Page bounds: 7160–7722px of 7722px
- 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": [
    {
      "role": "card/subheading",
      "family": "louize",
      "stack": "louize, \"louize Fallback\", ui-serif, Georgia, \"Times New Roman\", serif",
      "size": "18px",
      "weight": "500",
      "lineHeight": "18px",
      "letterSpacing": "-0.2px",
      "sample": "Social",
      "element": "h3",
      "occurrences": 3,
      "sourceId": "font-2"
    }
  ],
  "siteRoles": [
    {
      "role": "display",
      "size": "64px",
      "family": "louize",
      "source": "computed",
      "traits": "Regular",
      "weight": "500",
      "evidence": "font-10: computed CSS at 1440×1000; AI role: 64px Louize serif used for the primary main heading in the hero section.",
      "sampleId": "font-10",
      "confidence": 1,
      "lineHeight": "67.2px",
      "letterSpacing": "-2.6px"
    },
    {
      "role": "heading",
      "size": "28px",
      "family": "louize",
      "source": "computed",
      "traits": "Regular",
      "weight": "400",
      "evidence": "font-1: computed CSS at 1440×1000; AI role: 28px Louize serif used for section headings like 'Connect with your stack'.",
      "sampleId": "font-1",
      "confidence": 1,
      "lineHeight": "30.8px",
      "letterSpacing": "-0.8px"
    },
    {
      "role": "body",
      "size": "16px",
      "family": "lausanne",
      "source": "computed",
      "traits": "Regular",
      "weight": "400",
      "evidence": "font-5: computed CSS at 1440×1000; AI role: 16px Lausanne sans-serif used for standard descriptive paragraphs.",
      "sampleId": "font-5",
      "confidence": 1,
      "lineHeight": "24px",
      "letterSpacing": "normal"
    }
  ]
}
```

### Contextual design review

```json
{
  "status": "client-review-required",
  "checks": {
    "hierarchy": "Does each eyebrow, label and text level add useful information or clarify a necessary decision?",
    "decoration": "Do borders, effects, motion and spacing explain grouping or express a specific idea?",
    "repetition": "Can repeated claims, descriptions or actions be removed without losing needed information?",
    "identity": "What visible relationship between this offer, actual copy, imagery, typography and space gives the composition a convincing identity? Name its contribution and losses; matching ingredients or sparse styling are insufficient.",
    "reference": "Does it retain the source's dominant explanatory effect, media role, type balance and quiet space, not just columns?"
  },
  "heroMedia": {
    "appliesWhen": "A hero relies on focal media. A reasoned no-image hero remains valid and is judged by its visible composition.",
    "plan": "Record the image/headline first impression, actual available asset and crop, source image contribution, replacement contribution and losses before studies.",
    "review": "Does the actual hero suggest an offer, audience and experience appropriate to the whole brief? Quiet copy space or a recognizable subject is insufficient. One activity may lead without depicting all offers; justify its emphasis and resolve misleading implications. Missing assets or uncertain essential effects remain unverified."
  },
  "optionMedia": {
    "appliesWhen": "A section uses imagery to help visitors distinguish choices.",
    "planPerChoice": [
      "visitor distinction",
      "observable image evidence",
      "available asset or unresolved dependency",
      "crop retaining the distinguishing detail"
    ],
    "review": "Inspect the actual images. Shared atmosphere, changed crops or matching cards do not establish choice-specific meaning. If that role fails, resolve assets, choose an executable alternative or record lost/unverified and reject. Text comparison can be valid; it preserves a different contribution."
  },
  "noteCheck": "Check editorial interpretations against the received image; retain conflicts and unknown states instead of inventing selection or image meaning.",
  "decision": "Judge brief fit and positive character separately from layout preservation. Compare actual renders/references; essential lost or unverified effects prevent proceed. Reject either or both weak directions after inspection.",
  "qualityCertified": false
}
```

### Typography preservation review

```json
{
  "beforeStudy": "Use the actual reference image and captured section values to describe what its typography contributes: letter proportions and width, weight and contrast, case, line breaks and text-block shape, scale, spacing and relationship to the image. Label visual observations separately from captured facts and unknowns.",
  "substitution": "Choose an available, permitted face for the brief. Explain any substitute by the source relationships it preserves and any deliberate change; a familiar family, a serif/sans category or a mood label alone is not a justification. Do not copy an unavailable proprietary font or ban a common family merely because it is common.",
  "finalCheck": "Compare the actual rendered headline and supporting type beside this reference at the intended viewport. Check the loaded face/fallback and visible proportions, weight, line breaks, scale, spacing, contrast and image balance. Revise or reject when an essential typographic contribution is lost or unverified; a layout match or a font name is not a typography pass.",
  "unknowns": [
    "Glyph proportions, optical weight, actual line breaks, text-block shape and type-to-image balance require inspection of the reference image.",
    "Actual rendered face, font availability/licensing and responsive typography are not verified by this response."
  ]
}
```

### 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": [
    {
      "value": "#00BC7D",
      "cssValue": "lab(66.9756 -58.27 19.5419)",
      "alpha": 1,
      "appliedAs": [
        "background"
      ],
      "occurrences": 1,
      "sourceId": "color-27"
    }
  ],
  "functionalPalette": [
    {
      "hex": "#FCFCFD",
      "name": "canvas",
      "role": "canvas",
      "source": "computed",
      "evidence": "color-1: computed rgb(252, 252, 253); AI role: Off-white #FCFCFD used as the primary background color for the page.",
      "sampleId": "color-1",
      "confidence": 1
    },
    {
      "hex": "#08152E",
      "name": "text",
      "role": "text",
      "source": "computed",
      "evidence": "color-5: computed rgb(8, 21, 46); AI role: Dark blue #08152E used for primary headings, solid text, and main button backgrounds.",
      "sampleId": "color-5",
      "confidence": 1
    },
    {
      "hex": "#0A84FF",
      "name": "accent",
      "role": "accent",
      "source": "computed",
      "evidence": "color-11: computed rgb(10, 132, 255); AI role: Bright blue #0A84FF used for links and active UI elements within the graphics.",
      "sampleId": "color-11",
      "confidence": 0.9
    }
  ]
}
```

### Design tokens

```json
{
  "radius": "Maximum border-radius for interactive elements; estimated 16px-24px for large feature cards.",
  "density": "Low density, favoring large typography and ample whitespace over tightly packed information.",
  "evidence": "Observed from the pill-shaped 'Get Started' buttons, centered hero layout, and distinct visual separation of feature sections.",
  "borderStyle": "Minimal borders, occasionally using very faint structural lines between list items.",
  "buttonStyle": "Solid dark background with white text, pill-shaped without visible borders or heavy shadows.",
  "cornerStyle": "Fully rounded (pill-shaped) buttons and badges, with large soft radii on feature image containers.",
  "contentWidth": "Centered single-column layout for text, expanding slightly for split-feature blocks.",
  "spacingRhythm": "Generous vertical spacing between sections, maintaining a relaxed, breathable rhythm."
}
```

### Reconstruction specification

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

- Root: 1440×562px; block; padding {"top":"120px","left":"120px","right":"120px","bottom":"120px"}; gap normal; background rgb(252, 252, 253); radius 0px.
- Observed gaps: 8px.
- Layout containers: 0; cards/surfaces: 0; media elements: 1; browser animations: 0.

#### Container, grid, and spacing

```json
{
  "viewport": {
    "width": 1440,
    "captureBounds": {
      "top": 7160,
      "bottom": 7722,
      "pageHeight": 7722
    }
  },
  "container": {
    "size": "1440×562px",
    "position": "x 0px, y 7160px",
    "display": "block",
    "positionMode": "relative",
    "padding": {
      "top": "120px",
      "left": "120px",
      "right": "120px",
      "bottom": "120px"
    },
    "margin": {
      "top": "0px",
      "left": "0px",
      "right": "0px",
      "bottom": "0px"
    },
    "gap": "normal",
    "columns": "not captured",
    "background": "rgb(252, 252, 253)",
    "radius": "0px",
    "border": "0px solid rgb(8, 21, 46)",
    "shadow": "none",
    "overflow": "hidden"
  },
  "spacing": {
    "observedGapsPx": [
      8
    ],
    "representativeContentWidthsPx": []
  },
  "columns": []
}
```

#### Cards and surfaces

```json
{
  "cards": [],
  "surfaces": {
    "radii": [],
    "borders": [],
    "shadows": []
  }
}
```

#### Media treatment

```json
[
  {
    "element": "svg · svg",
    "size": "117×28px",
    "position": "x 120px, y 7280px",
    "aspectRatio": 4.2,
    "objectFit": "fill",
    "objectPosition": "50% 50%",
    "radius": "0px",
    "overflow": "hidden",
    "source": "source not captured"
  }
]
```

#### 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
{
  "root": {
    "id": "ld-518",
    "gap": "normal",
    "tag": "footer",
    "rect": {
      "x": 0,
      "y": 7160,
      "width": 1440,
      "height": 562
    },
    "role": null,
    "label": "All systems operationalSocialX (formerly Twitter)LinkedInDiscordCompanyBlogBrandCareersFAQContact Us",
    "border": "0px solid rgb(8, 21, 46)",
    "margin": {
      "top": "0px",
      "left": "0px",
      "right": "0px",
      "bottom": "0px"
    },
    "radius": "0px",
    "shadow": "none",
    "columns": null,
    "display": "block",
    "padding": {
      "top": "120px",
      "left": "120px",
      "right": "120px",
      "bottom": "120px"
    },
    "overflow": "hidden",
    "position": "relative",
    "background": "rgb(252, 252, 253)"
  },
  "cards": [],
  "media": [
    {
      "id": "ld-523",
      "tag": "svg",
      "rect": {
        "x": 120,
        "y": 7280,
        "width": 117,
        "height": 28
      },
      "role": null,
      "label": "svg",
      "media": null,
      "radius": "0px",
      "overflow": "hidden",
      "objectFit": "fill",
      "aspectRatio": 4.2,
      "objectPosition": "50% 50%"
    }
  ],
  "bounds": {
    "top": 7160,
    "bottom": 7722,
    "pageHeight": 7722
  },
  "schema": "little-details-section-measurements-v1",
  "source": "saved DOM/CSS element and animation maps",
  "columns": [],
  "spacing": {
    "gapsPx": [
      8
    ],
    "representativeContentWidthsPx": []
  },
  "coverage": {
    "cards": 0,
    "media": 1,
    "animations": 0,
    "elementsInSection": 24
  },
  "surfaces": {
    "radii": [],
    "borders": [],
    "shadows": []
  },
  "animations": [],
  "capturedAt": "2026-09-21T04:24:40.088Z",
  "limitations": [
    "Values describe the captured desktop viewport and may change at other breakpoints.",
    "Transforms, sticky layers, and virtualized content can make the inferred section root approximate.",
    "Animations include browser-exposed Web Animations API state; CSS or script motion that was inactive at capture time may be absent."
  ],
  "viewportWidth": 1440
}
```

### Observed motion

1. **scroll** — The scroll reaches the bottom of the page revealing the footer. (22s–28s; 95% confidence). Recreate the interaction principle with project-appropriate timing and easing; the evidence does not guarantee source easing values.

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: 1440px 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

These categories describe evidence, not independent layers that can be swapped without changing the design. Study the complete reference system before adapting it.

- Preserve: content hierarchy, layout relationships, section rhythm, interaction purpose.
- Adapt: brand colors, font family, copy, imagery, icons, decorative details.
- Rule: These compatibility categories are coupled: fonts, color and imagery can carry the layout's design logic. Preserve or purposefully replace their contribution while creating original branding, copy, assets, and implementation details.

### Adaptation and dependencies

- Effort: low
- What transfers: Left-aligned brand/status block paired with right-aligned multi-column link grid; Small live status indicator pattern
- Dependencies: Specific font pairing (serif logo, sans-serif body); Exact color tokens for status dot and text
- Guidance: Reusable as a generic footer template; swap logo, link groups, and accent color while keeping the status indicator pattern for any site needing a system-status footer.

### Evidence readiness

- Coverage: 7/7
- Can build: Yes
- Missing facts: None


### Agent implementation prompt

Create an original footer section inspired by the design evidence titled “Minimal Status Footer”.

Purpose: A very clean, sparse footer displaying a system status indicator alongside standard navigational links.

Structure: Logo and status indicator aligned left, with multiple columns of small text links aligned right.. Source layout label: Logo and status indicator aligned left, with multiple columns of small text links aligned right.. Preserve the documented hierarchy and relationships; exact measurements were not deterministically captured.

Visual signature to preserve at the pattern level: Sparse layout with a prominent green dot indicating system status next to the logo.

Components: Brand logo, System status indicator, Navigation link columns.

Style direction: minimal.

Observed crop: 1200×468px (2.564:1). Treat this as evidence of composition, not a mandatory output size.

Typography evidence: {"role":"display","size":"64px","family":"louize","source":"computed","traits":"Regular","weight":"500","evidence":"font-10: computed CSS at 1440×1000; AI role: 64px Louize serif used for the primary main heading in the hero section.","sampleId":"font-10","confidence":1,"lineHeight":"67.2px","letterSpacing":"-2.6px"} {"role":"heading","size":"28px","family":"louize","source":"computed","traits":"Regular","weight":"400","evidence":"font-1: computed CSS at 1440×1000; AI role: 28px Louize serif used for section headings like 'Connect with your stack'.","sampleId":"font-1","confidence":1,"lineHeight":"30.8px","letterSpacing":"-0.8px"} {"role":"body","size":"16px","family":"lausanne","source":"computed","traits":"Regular","weight":"400","evidence":"font-5: computed CSS at 1440×1000; AI role: 16px Lausanne sans-serif used for standard descriptive paragraphs.","sampleId":"font-5","confidence":1,"lineHeight":"24px","letterSpacing":"normal"}

Color evidence: {"hex":"#FCFCFD","name":"canvas","role":"canvas","source":"computed","evidence":"color-1: computed rgb(252, 252, 253); AI role: Off-white #FCFCFD used as the primary background color for the page.","sampleId":"color-1","confidence":1} {"hex":"#08152E","name":"text","role":"text","source":"computed","evidence":"color-5: computed rgb(8, 21, 46); AI role: Dark blue #08152E used for primary headings, solid text, and main button backgrounds.","sampleId":"color-5","confidence":1} {"hex":"#0A84FF","name":"accent","role":"accent","source":"computed","evidence":"color-11: computed rgb(10, 132, 255); AI role: Bright blue #0A84FF used for links and active UI elements within the graphics.","sampleId":"color-11","confidence":0.9}

Typography measured inside this section: {"id":"font-2","size":"18px","count":3,"family":"louize","traits":"Regular","weight":"500","contexts":[{"tag":"h3","top":7280,"text":"Social","property":"font"},{"tag":"h3","top":7280,"text":"Company","property":"font"},{"tag":"h3","top":7280,"text":"Tools","property":"font"}],"fontStack":"louize, \"louize Fallback\", ui-serif, Georgia, \"Times New Roman\", serif","lineHeight":"18px","letterSpacing":"-0.2px"}

Colors measured inside this section: {"id":"color-27","hex":"#00BC7D","alpha":1,"count":1,"contexts":[{"tag":"span","top":7351,"text":"","property":"background"}],"cssValue":"lab(66.9756 -58.27 19.5419)"}

Exact section measurements from the saved element map: root {"rect":{"x":0,"y":7160,"width":1440,"height":562},"padding":{"top":"120px","left":"120px","right":"120px","bottom":"120px"},"gap":"normal","columns":null,"overflow":"hidden"}; spacing {"gapsPx":[8],"representativeContentWidthsPx":[]}; surfaces {"radii":[],"borders":[],"shadows":[]}; media [{"tag":"svg","rect":{"x":120,"y":7280,"width":117,"height":28},"aspectRatio":4.2,"objectFit":"fill","objectPosition":"50% 50%","radius":"0px"}]

Motion evidence: scroll: The scroll reaches the bottom of the page revealing the footer. (95% confidence)

Transfer these principles: Left-aligned brand/status block paired with right-aligned multi-column link grid; Small live status indicator pattern.

Dependencies: Specific font pairing (serif logo, sans-serif body); Exact color tokens for status dot and text.

Adaptation guidance: Reusable as a generic footer template; swap logo, link groups, and accent color while keeping the status indicator pattern for any site needing a system-status footer.

Study layout, typography, color, imagery and spacing as one coordinated source system. Record what creates its effect before producing a concept; preserve or purposefully replace each consequential relationship when adapting the business content and assets.

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