### App vs Landing Page Rules

The surface type classified in Phase 1 determines which rule set governs layout. Mixing the two rule sets is the fastest way to produce a page that feels generic in one direction and cluttered in the other.

**Landing page rules** (marketing, product promotion, portfolio intro):
- Full-bleed hero, single composition, brand-first scale
- Narrative section sequence: Hero → Supporting imagery → Product detail → Social proof → Final CTA
- Each section does one job; cut the section if it cannot decide on one takeaway
- Atmospheric backgrounds encouraged (gradients, textures, layered depth)
- Motion used to reveal and orchestrate the narrative

**App and dashboard rules** (operator tools, data consoles, admin surfaces):
- Default to Linear-style restraint: calm surface hierarchy, strong typography, tight spacing
- Few colors. Usually one accent, one or two functional hues, the rest is neutral
- Dense but readable information. Operators scan headings, labels, and numbers
- Cards only when the card is the interaction (a selectable item, a sortable row, a drag target). No cards for purely visual grouping
- Prefer calm dashboard surfaces with a few well-defined regions instead of a bordered-box mosaic
- Prefer restrained gradients, selective borders, and a single accent color so the hierarchy stays clear
- Motion is minimal and functional: a focus ring, a row expand, a drawer slide. Not ambient flourish

**App litmus test**. If an operator scans only the headings, labels, and numbers on the page, can they understand what the page is showing them immediately? If they need to read paragraphs of body copy or decode ornamental UI to figure out what they are looking at, the page is failing its job.

**Landing litmus test**. If the user spends three seconds on the first viewport, can they name the product and describe the promise in one sentence? If not, the hero is failing its job regardless of how polished it looks.
