The site is the demonstration.
StratusWorks sells the argument that efficient software costs less to run and lasts longer. A marketing site is a small system, so we hold it to the same discipline we sell, and we publish how.
Everything below is verifiable from your browser: view source, read the headers, measure the weight.
Web components without JavaScript.
- Every page ships zero executable JavaScript
- No script files, no inline handlers, no framework runtime. The only script element on the site is structured data.
- The component library is real custom elements
- Composition blocks are custom elements activated by declarative shadow DOM, which the browser parses as markup: element names without a runtime.
- Interactivity is the platform
- The mobile menu is a details element, the theme control is radio buttons read by CSS, form validation is constraint attributes. The platform absorbed what libraries used to do.
- The security headers assume the worst anyway
- The Content-Security-Policy is default-src none with no script source: even an injected script would not execute.
Three practices, byte-identical stylesheets.
- Three sites share two stylesheets, byte for byte
- StratusWorks, CloudLift, and ClarusTech carry identical CSS; an invariant check fails if any copy drifts from the shared source.
- One attribute swaps the brand
- Each practice sets a single attribute on its root element; six accent tokens change and nothing else. The logo geometry is identical, only the hued stratum moves.
- Design decisions live in a chain
- A design intent document generates design tokens, which generate the CSS custom properties the browser consumes; a check asserts all three agree on every colour in both themes.
- Both themes are authored, neither is a filter
- The dark theme has its own neutral ramp and accent pairs; every text and background pair clears the accessibility contrast bar in both.
Published figures the build must defend.
- The published budget is a claim the checks enforce
- The budget panel prints this page's own transferred weight; the toolchain re-measures on every run and fails until the panel and the measurement agree.
- The whole page fits in the budget
- HTML, both stylesheets, and all three self-hosted typefaces together stay under the published budget, a fraction of what a typical consultancy page ships.
- No third-party requests, so no consent banner
- Every asset is self-hosted, no analytics beacon runs, and the one cookie is a signed timestamp that protects the contact form. There is nothing to consent to.
- Figures we did not measure do not appear
- No invented case-study numbers, no illustrative statistics dressed as results. Where a figure is illustrative, the caption says so.
The verification is part of the artifact.
- The invariants are written down and numbered
- Zero script, strict headers, no third-party origin, two themes, one cookie, a resource budget, tokens-only styling: each is a testable statement, not a preference.
- The toolchain is zero-dependency Java
- Static checks, a dev server with production routing, a form roundtrip against the real runtime, and a browser harness that sweeps every page in both themes. Nothing is downloaded to verify the site.
- The same discipline is the service
- Budgets, boundaries, measurement, and decision records are what we bring to client systems; this site is simply the smallest system we run them on.
Want your system held to the same standard?
Tell us what you are building, changing, or trying to improve. We will help identify the first decision that matters.