WorkCase study
Compile
Principle compiler — turns plain language into verifiable design contracts.
A tool that takes any plain-language design principle and compiles it into tokens, anti-patterns, a review checklist, and a portable verification script. Built and locally verified. Self-documents to the 10-cell Lab anatomy. Demonstrates the Sources to Contracts to Tools chain. Pending hosting and publication.
Summary
Outcome · ready for review
Compile is the most complete tool in the set. The thesis is uncrowded — no existing tool compiles plain-language principles into verifiable design contracts. The seven-domain engine covers motion, color, typography, spacing, shape, interaction, and acoustic. The output self-documents to the 10-cell Lab anatomy. Nine verification tests passed. A security fix (local path leak in compiled output) was found and fixed through the verification gate. The only remaining work is hosting, packaging, and publication — no technical barrier remains.
Verification evidence
Build verification · 2026-07-13
Nine test principles compiled across seven design domains. All passed. A security audit found a local path leak in compiled contract output (embedding D:\DESIGNESY\DESIGN.md paths) — fixed to reference public designesy.org URLs. Verified clean after fix. The tool is ready for hosting.
Inputs used
Dimension findings
Each dimension: observation, judgment, action — Kit One format.
Purpose
Observation. Compile states a single thesis: a principle can be compiled into tokens, a test, and a checklist, the same way source code compiles into a binary. No existing tool does this — palette tools give swatches, Lighthouse checks performance, linters check syntax. Nothing takes a plain-language design principle and outputs a verifiable contract.
Judgment. Purpose is sharp and genuinely uncrowded. The tool demonstrates the Sources to Principles to Contracts to Tools chain in a way no competitor does.
Action · Keep. The thesis is the moat — do not dilute it by adding generic design-tool features.
Clarity
Observation. One input. Four output tabs: Contract, Verify, Review, Anti-patterns. A live preview shows compiled tokens applied to a UI skeleton. Exportable as a ZIP (contract.md, verify.js, tokens.css, README.txt).
Judgment. Clarity is strong. The tool does one thing and shows its work. The four-tab structure maps to the contract contents list.
Action · Keep the four-tab structure. Do not add tabs that do not map to contract contents.
Context
Observation. Self-contained single index.html, no framework, no CDN, no backend. Follows the Tile and Continuity deployment pattern exactly. Built and verified locally. Pending hosting on GitHub Pages.
Judgment. Context is ready. The deployment pattern is proven. The only blocker is hosting — no technical barrier remains.
Action · Host on GitHub Pages (LE-VAI/compile). Generate the OG image. Publish with the proven one-word + screen-recording format.
Inclusion
Observation. Dark default, reduced-motion safe, mobile responsive. System font stack. No required audio or motion. Compilation engine covers seven design domains: motion, color, typography, spacing, shape, interaction, acoustic.
Judgment. Inclusion is structural. The seven-domain coverage means acoustic and interaction are first-class, not afterthoughts. No other tool compiles acoustic tokens.
Action · Keep the seven-domain coverage. The acoustic domain is a Designesy differentiator.
System coherence
Observation. The compilation engine derives tokens from Designesy DESIGN.md v0.2.0. The output contract structure matches the Designesy contract contents list. The review checklist generates all eight Designesy review dimensions. The tool IS the Lab — its output satisfies the 10-cell Lab anatomy.
Judgment. Coherence is the strongest dimension. The tool is the pipeline made visible: a principle goes in, a contract comes out. The Lab anatomy mapping is self-documenting.
Action · Keep the DESIGN.md derivation explicit. When the contract moves to v0.3.0, update the compilation engine.
Durability
Observation. Full BRIEF documents intent, thesis, feel, what it does, the seven-domain engine, the Lab anatomy mapping, and the substitute test. STATUS.md tracks all build items (all marked built) and pending items (OG, hosting, screen recording, X staging, Lab Four registration). Nine verification tests passed.
Judgment. Durable as a built artifact. The documentation is the most complete of any tool in the set — it self-documents to the Lab anatomy.
Action · Host, generate OG, record, publish. The tool is ready; the packaging is what remains.
Delight
Observation. The delight moment is watching a plain-language principle compile into a structured contract with tokens, a verification script, and a review checklist. The live preview showing tokens applied to a UI skeleton makes the abstraction visible.
Judgment. Delight is earned — the tool makes the abstract concrete. Watching a principle become a contract is a genuine aha moment.
Action · Keep the live preview. The preview is the demo — it shows the tool thinking.
Responsibility
Observation. The tool includes a substitute test: four things you might do instead (ChatGPT, Figma tokens, Lighthouse, eslint) and why each fails to substitute. The security fix (local path leak in compiled output, found and fixed 2026-07-13) is part of the story — the verification gate caught a real problem.
Judgment. Responsibility is demonstrated, not claimed. The substitute test is honest about what the tool is not. The security fix shows the review process working.
Action · Keep the substitute test visible. Document the security fix as a verification-gate success story.