Glossary

Vocabulary used across Vanilla Breeze documentation. Type to filter; click a term to deep-link to its definition.

A

attribute: A name–value pair on an HTML element that configures behaviour or carries metadata. VB uses three orthogonal provenance attributes: data-provenance, data-review, and data-status.

canonical document: The normalized text representation of a page used as the input for hashing and signing. Defined by admin/specs/canonical-document-v1.md (Stage 3, in progress).
change set: A grouped collection of <ins>/<del> edits with view toggles for tracking, final, and original states. Implemented by the <change-set> component.
content lens: A view over the site's metadata substrate that groups pages by one field family — time (changelog), keyword (index), term (glossary), structure (sitemap), authorship (forthcoming), or provenance (forthcoming). Each lens shares the same data; only the projection differs.
custom element: An HTML element with a hyphenated tag name registered via customElements.define(). VB ships custom elements as web components (with shadow DOM/styles) and as plain custom elements (CSS-only sugar over native semantics).

data-provenance: The DOM attribute that declares how a page or section was made. Vocabulary core: human, ai-assisted, ai-generated. Extensions: translated, synthesized, migrated. Tokens compose space-separated.
data-review: The DOM attribute that records what review a page received. Values: unreviewed (default), fact-checked, editor-reviewed.
data-status: The DOM attribute that records publication state. Values: draft, published (default), archived.
data-trust: Runtime verification tier emitted by <page-info> on its badge. Values: undeclared, declared, domain-anchored, verified, failed, key-unavailable. Distinct from data-provenance — author-declared vs. runtime-computed.
design token: A named value (color, spacing, font size) stored as a CSS custom property. Tokens form the vocabulary of a design system; VB ships its own and lets sites override with their own.

HTML-first: The framework stance: semantic HTML carries meaning, CSS carries presentation, JavaScript only adds behaviours that genuinely require it. Components must remain readable without JS.

meta-tag contract: The published, versioned specification for which <meta>, <link>, DOM attributes, and JSON-LD fields VB consumes at runtime. Source of truth: admin/specs/meta-tag-contract-v1.md.

page-info: The disclosure-panel web component that surfaces author, dates, version, provenance, review, status, license, and verification state. In auto mode, reads from the page's meta-tag contract; in static mode, enhances hand-authored markup. Component reference.
progressive enhancement: The practice of building features as additive layers: a baseline (HTML) that works without enhancement, then CSS, then JS — each layer optional. VB applies this both at the file level (every component has a static fallback) and at the system level (Layer 0 static → Layer 1 SSG → Layer 2 CMS for provenance).
provenance: The traceable origin of a piece of content — who made it, how, with what tools, reviewed by whom, signed by which key. VB ships a contract (Stage 0–1 done) and a verification path (Stages 3–4 in progress).

review (level): The kind of human review a page received. See data-review.

signing: The cryptographic step that binds a canonical document to an author key. VB defines a verifier and a canonicalization spec; signing tools are reference implementations (Stage 4).
metadata substrate: The shared field family — identity, temporal, topic, provenance, integrity, engagement, license — that every lens consumes. Adding a new field once exposes it to every lens at once.

trust tier: The verification result computed by <page-info>: declared, domain-anchored, verified, failed, or key-unavailable. Surfaced via data-trust on the badge.

web component: A custom element that ships with shadow DOM, styles, and behaviour. VB web components must work as static HTML (the baseline) and progressively enhance when JS loads.