# Covenant Design Doctrine

## Core identity

Covenant Systems uses warm Gruvbox paper, restrained terminal structure, Qeshet spectrum wayfinding, and source-aware document apparatus to make complex material navigable, verifiable, and calm.

## Meaning of the rainbow / spectrum

The spectrum is not decoration. It is:

- a covenant/signature mark;
- a wayfinding grammar;
- an indicator of section role;
- a symbol of structure, promise, continuity, and truth-seeking.

## Reading and cognition rules

- Make structure explicit before style.
- Chunk by question, claim, task, or source role.
- Use large text for true landmarks only.
- Use contrast and whitespace before color.
- Use color as a secondary cue, never the only cue.
- Make source visibility cheap: citations, notes, source status, and appendices should be easy to find.
- Motion must support state or identity, not pressure or distraction.
- Reduced motion must disable nonessential animation.

## Design stance

Covenant should feel:

- warm, serious, and structured;
- terminal-native but not app-gimmicky;
- scholarly but not bland;
- beautiful but not distracting;
- modular enough to generate with AI.

## Avoid

- generic default TOCs;
- status boxes that dominate the document;
- decorative rainbow body text;
- excessive horizontal dividers;
- meaningless UI pills;
- forcing a dashboard feel into academic papers;
- relying on hover-only interactions;
- using progress to pressure the reader.