# Build brief: Conceptual Sketch

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 product concept page with an annotated flow and clearly marked open questions.

A deliberately unfinished visual treatment that makes ideas and relationships easy to discuss. Sketchiness can communicate a draft state, but should not conceal the status of real functionality.

## Essential cues
- Loose line
- Annotations
- Visible structure

## Recipe
- Use annotations to explain actual decisions.
- Keep labels typeset and readable.
- Mark unfinished or hypothetical features explicitly.

## Optional decoration
Original annotations or a simple diagram can supply the sketch layer.

## Avoid
Presenting an incomplete workflow as working or making every line so irregular that relationships become ambiguous.

## Values and validation
Read [tokens](/territories/conceptual-sketch/tokens.json) and [acceptance checklist](/territories/conceptual-sketch/checklist.md). Use [the working example](/territories/conceptual-sketch/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.