# Build brief: Brutalism

Resource base: https://mejohnc.org (or the preview host used to obtain this file).

Use this direction within the user’s requested project and existing design constraints.

## Illustrative use case, not project requirements
A project archive with oversized titles, underlined links, and no entrance sequence.

A web approach that exposes structure through plain typography, hard boundaries, and direct links. Its architectural namesake is an analogy, not a prescription for bad usability.

## Essential cues
- Visible structure
- Hard edges
- Unembellished controls

## Recipe
- Use explicit link text.
- Separate sections with rules.
- Make every action respond immediately.

## Optional decoration
Type, rules, and content can carry the page without images.

## Avoid
Confusing deliberate roughness with broken navigation, tiny text, or inaccessible contrast.

## Values and validation
Read [tokens](/territories/brutalism/tokens.json) and [acceptance checklist](/territories/brutalism/checklist.md). Use [the working example](/territories/brutalism/example/) to inspect color roles, spacing, hierarchy, and interaction states. It is a UI translation, not a reproduction of historical art. Tokens describe the base UI; [example CSS](/territories/assets/example.css) contains the style-specific composition and decorative layer. Preview navigation with `?navigation=top`, `?navigation=sidebar`, or `?navigation=tabs`; combine with `project`. Use [Compare](/territories/compare/) for mobile (390 px), tablet (820 px), and desktop (1440 px) viewports.

## Delivery
Preserve real content and existing working behavior. Check keyboard, narrow layout, error, empty, and success states. Report any departures from this recipe with a reason. Do not claim to have inspected a preview or run checks that you could not access.

Schema 1.0.0; revision f5fd78058ba2.