Vaquum Design System

What the system is

The Vaquum design system specifies the face and voice of every reader-facing surface the firm produces. Face is the pre-cognitive register of the page — typography, whitespace, rule, and colour. Voice is the register the reading mind runs when it pronounces the words on the page. Both channels govern every element, always.

The system is defined as a closed set of parameters and a closed set of content forms. A surface is deterministic when every parameter carries a declared value the rendered output can be checked against. This page carries those declarations in its frontmatter, and the validator verifies the rendered surface against them.

What this site is

This site is the canonical instance of the system it describes, and not a description of something separate. The heading atom’s page is itself a heading, the tone page declares its own tone, and the neutral temperature page is written neutrally. The documentation and the artifact occupy the same surface.

Every surface is composed from 14 text atoms, 17 diagram atoms, and the modality forms for input, table, and record. Modules render content from markdown with typed frontmatter and compose it per the flavour of the module. Face tokens carry the closed sets of visual values in one versioned stylesheet. A style change is a single-file deploy, a module upgrade is a single worker update, and a content edit is a pull request that auto-merges and auto-deploys.

What comes next

The first slice publishes the index, the ontology, the nine face parameters, the eight voice parameters, and the 14 text atoms. Each page is a surface that declares its own values and is rendered by the module that matches those values. The validator runs on every build, gates merges, and keeps the closed sets closed. Further modalities — diagram, table, input, and record — extend the same contract.