# Build brief: Cybercore

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 fiction anthology with terminal-inspired chapter labels and normal reading typography.

A broad internet aesthetic drawing on fictional hacker interfaces and digital dystopia. It is expressive fiction, not evidence that a product is technically sophisticated.

## Essential cues
- Dark field
- Neon accents
- Terminal-like detail

## Recipe
- Use monospace for actual structured information.
- Keep glitch effects in static artwork.
- Give real system states explicit labels.

## Optional decoration
Static digital artwork works; fake live telemetry does not add value.

## Avoid
Fake telemetry, flashing warnings, or presenting decorative code as real diagnostic data.

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