# Utilitarian

Schema: 1.0.0 · Content revision: f5fd78058ba2
Resource base: https://mejohnc.org (or the preview host used to obtain this file).

A task-oriented approach that makes information easy to compare and actions easy to repeat. Density is useful only when it reduces work for the reader.

## Visual family
Modernism & structure. Editorial family: shared visual vocabulary, not a claim of common origin.

## Visual cues
- Explicit labels
- Aligned data
- Predictable controls

## Build it
1. Align numbers and show units.
2. Keep filters near the results.
3. Use status text alongside color.

## Example
An operations queue with owner, state, age, and one clear next action per row.

## Typography
Use a legible sans-serif and tabular numerals for comparable values. Reserve monospace for identifiers.

## Practical consequences
- Starting projects: Internal tool, Publication. These are suggestions, not restrictions.
- Reading/layout: compact; quiet visual emphasis.
- Asset work: Real labels, units, and status data matter more than imagery.
- Complexity: low. Mostly standard CSS; imagery may still need preparation.

## Limits
Hiding important actions in icon-only menus or showing more metrics than a decision needs.

## Reading the collected reference board
The examples use restrained grids, alignment, and clear numerical detail. They are mostly graphic layouts; a useful operational interface also needs task-specific information and controls.

## Context
Contemporary screen interpretation. The recipe is a modern web adaptation.
No single inventor or exact founding date is asserted for this interpretation.

## Implementation files
- [page](/territories/utilitarian/)
- [guide](/territories/utilitarian/guide.md)
- [brief](/territories/utilitarian/brief.md)
- [tokens](/territories/utilitarian/tokens.json)
- [checks](/territories/utilitarian/checklist.md)
- [example](/territories/utilitarian/example/)
- [versionedGuide](/territories/v1/utilitarian/guide.md)
- [versionedTokens](/territories/v1/utilitarian/tokens.json)