HTML Design

**The describing overlay.** Guidelines prose where executing configuration belongs; the pipeline consuming nothing (§1). **Identity plural-sourced.** The register living in three overlays independently; the twins drifting by construction (§1, §10). **The unwritten section.** Improvisation regions with a section number; completeness assumed from the sections that exist (§2). **Register-blind derivation.** Lower sections arguing with §3 instead of reading it; the constitution unconsulted (§3). **Values leaking structural.** The rebrand surface spreading into skeletons; the architecture's promise broken at the file (§4). **The growing inventory.** Signatures accumulating without replacement; fame divided per DKB-2.3 §3's arithmetic (§5). **Implicit match tables.** Claim-scale licenses living in heads; wolf-crying adjudicated by memory (§6). **Perishables un-audited.** Maps and certifications aging silently; occlusion and recompression failures with old dates (§7). **Customary authority.** Verdict rights by habit; the first deadline dissolving them (§8). **The era-less deployment.** Boundaries untagged; every trend analysis standing on sand (§8). **Overlay inheritance.** Brand B born from brand A's files; dilution and bleed built in at creation (§9). **The un-handoffable system.** Taste carried, configuration unwritten; the deployment dying with its authors (§9).

The overlay closes the engine's world, and the corpus: **Overlay plus library equals the world:** the engine's complete deployment context is this artifact plus the skeleton library (DKB-6.1 §10's containment): the tokens it may speak, the templates it may fill, the assets it may reference, the canvases it may target, the authorities it answers to: everything, and nothing else. Loading a deployment into the generation layer *is* loading its overlay, which makes the overlay's completeness (§1) the engine's safety envelope: the unwritten section is the envelope's hole. **The coordination seam, instrumented:** the three overlays (sales, content, design) share the identity core (§1), and the seam is audited: the register statements compared (the twins law verified per era: has the content voice's profile drifted from the visual register's positions?), the shared facts diffed (the offer facts per KB-4.3 §10 and the announcement templates' registry reads pulling from one source), and cross-overlay drift treated as a finding with the DKB-5.4 §8 adjudication (which overlay moved, was it authorized, and which is the reference): one deployment, three media, one identity, and the seam's health is what keeps the audience meeting one operation. **The first instantiation is the proof:** the corpus's definition of done includes its first overlay: the pilot deployment (DKB-5.1 §10's pattern) standing up section by section in the §2 order, the poster family instantiating first, the era log opening at day one: the universal corpus is complete when it is written, and *proven* when a deployment renders through it end to end: overlay to skeleton to pipeline to gates to certified store to feed, with every law in twenty-five docs either encoded in the artifacts or staffed at the stations. **The corpus's last operating implication:** the whole system, restated as its parts' relationship: the KB states the law, the overlay states the deployment, the library makes both executable, the pipeline makes execution deterministic, the gates make compliance arithmetic, the stations hold the judgment, the governance holds the pen, the telemetry holds the memory, and the engine, inside all of it, renders at volume what the deployment decided with care. Visual craft compounds a real message. The architecture exists so that what compounds is real.

The dark-theme B2B brand, whose fragments every worked example built, collected into its ten sections: **§3 Identity:** technical, premium, calm, sparse, engineered (the register the corpus's examples expressed); the twins reference to its content voice profile; the footer's two anchors from the brand facts. **§4 Tokens:** the forty-one decisions (DKB-2.2's worked example): charcoal ground family, five rungs, one accent with certified pairs per plane, the six-step scale at 1.333, the 4-base spacing progression, the effects set: stable and variable sets marked. **§5 Signatures:** the five-entry inventory (accent-on-payload, mono kicker with tick, two-anchor footer, dot grid, outlined display word) with the accent-period candidate tracking toward graduation; the ground stack (one radial, grid plus grain, no vignette, frameless); the lockup's three variants with thresholds. **§6 Archetype settings:** twelve certified templates' configs (DKB-6.1's manifest); the match table (identity claims: monument license; weekly lines: full stack); carousel lengths by lane. **§7 Platform:** three canvases declared, maps dated this spring, the checklist family's grain re-certification logged, naming grammar fixed. **§8-§9 Operations and governance:** the registry's schema and the one revocation-path test on record; the pinned environment at its current definition; the gate suite at its version with the emphasis-family interface fix era-tagged (DKB-5.4's investigation); authorities named; the origination line written; the era log carrying every boundary the corpus's examples generated. **§10 Profile:** extracted, baselined, the drift dashboard referencing it, the onboarding curriculum's state noted. **The test:** hand these files and the skeleton library to a team that has never met the deployment, and they can render tomorrow: which is what "written down" means, and what twenty-five documents were for.