The Covenant design system

One language. Different surfaces.

Warm editorial reading, precise technical detail, and an identity that stays recognizable in light or dark.

The current Qeshet study: continuity, with a source in view

The current arc-and-packet mark is an identity study, not a permanent logo decision. Its packet represents a source or unit of knowledge; fine structural lines connect the study to documents and navigation without implying that a source has been independently verified.

Use the full identity sparingly. A small mark can orient a page. A larger one can introduce the collection. Neither should compete with reading.

Qeshet, the Covenant Systems markNested spectrum arcs above a small source packet and three structural lines. A symbol of continuity, structure, and source traceability.
Qeshet · arcs, a packet, and structural linework.

Appearance is not a mode of thought

System follows your device’s light or dark preference. Light and Dark are optional overrides. Your choice changes colors, not the content or capabilities of the page.

Editorial, technical, and terminal are presentation registers. An article can be editorial in either theme. A terminal example is a separate surface, not the definition of dark mode.

Color has a job, not the last word

Gruvbox colors anchor the identity. Text-bearing variants are adjusted perceptually and checked against their reading surfaces. Labels, linework, and headings carry the meaning even without color.

Critical
Errors, danger, or a contradiction that needs attention.
Orientation
Identity, direction, and where to go next.
Structure
Findings, section structure, and important conclusions.
Evidence
Evidence and explicitly established verification states.
Analysis
Interpretation, relationships, and synthesis.
Sources
Citations, references, and original records.
Deep detail
Appendices, metadata, and implementation detail.

Meaning before rendering

Content, semantic roles, modules, and themes are separate. The current foundation generates ordinary HTML, a static search index, semantic metadata, and provider-neutral content records from the same public source model.

The component laboratory shows the implemented foundation. The module registry records each component’s purpose, states, accessibility requirements, and renderer.

Inspect the working components →

Sources & implementation notes 4

Public project references. Earlier design notes describe the original direction; implementation contracts describe this edition.

Back to the public collection