stnd.buildSTANDARD MANUAL2026-07-15

1.4 Engineering Philosophy

The structural invariants and dualistic architecture of the Standard Framework.

1.4 Engineering Philosophy

“A system must be rigid enough to prevent collapse, yet invisible enough to allow life.” — Standard Technical Directives, 2026

The Standard Framework (@stnd) is engineered as an industrial-grade spec. It borrows its rigor from the structural manuals of the 1970s—such as the NASA or EPA Graphic Standards. It does not suggest; it dictates. It establishes absolute boundaries within which chaos and creativity can safely operate.

This document serves as the architectural manifesto. It outlines the engineering invariants that guarantee the system’s resilience, scalability, and aesthetic precision.

The Duality: The Grid and The Garden

The architecture is built upon a deliberate duality:

  1. The Standard (stnd.build): The mechanical grid. Unforgiving, mathematically absolute (anchored in the golden ratio (\varphi)), and completely modular. It is the sterile laboratory environment where layout, performance, and security rules are enforced without exception.
  2. The Garden (stnd.gd): The organic outcome. A chaotic, living ecosystem where human thought, notes, and communities intertwine.

The Garden can only flourish because the Standard provides an indestructible trellis. If the framework leaks, the garden dies. Therefore, the framework’s architecture is defensive by design.

Architectural Invariants

1. Vertical Slices over Horizontal Layers

The system abandons the traditional MVC monolith in favor of Vertical Slice Architecture.
Features (e.g., sitemap, toast, account) are self-contained within packages/modules/. A module encapsulates its own UI (.astro/.svelte), its own logic (virtual:stnd/hooks), and its own integrations.

  • The Guarantee: Complete decoupling. A module can be removed by deleting its directory. There are no cross-domain side effects. If a feature fails, the blast radius is confined to its slice.

2. Edge-Native and Stateless

The backend is designed exclusively for Cloudflare’s Edge (Workers, D1, R2, KV Cache).

  • The Guarantee: Extreme global scalability with near-zero latency.
  • The Mechanism: Connections to the database (Kysely-D1 via Better-Auth) are dynamically bound per-request. The system explicitly forbids Node.js singletons, preventing state-leakage between parallel requests across edge nodes.

3. CSS-First, Zero-JS by Default

We reject the modern impulse to wrap every HTML element in a JavaScript framework.

  • The Guarantee: Minimal payload, instant Time-To-Interactive (TTI).
  • The Mechanism: UI elements (buttons, badges, inputs) are pure CSS classes mapped by @stnd/styles. Components (Svelte/Astro) are strictly reserved for complex state management (e.g., DialogManager, Command Palettes) utilizing Svelte 5 runes ($state, $effect) for surgical DOM updates without VDOM overhead.

4. Provide / Inject State Management

Prop-drilling across the Astro Server/Client boundary is an anti-pattern.

  • The Guarantee: Absolute separation of Astro Islands.
  • The Mechanism: @stnd/store implements a reactive nanostores registry on the client. Modules provide services (provide('user', userStore)) at boot, and isolated Svelte islands inject them (inject('user')). The components remain perfectly agnostic of each other.

Conclusion for the Auditor

The Standard Framework is not a prototype; it is an industrial tool. It enforces zero technical debt by aggressively purging backward-compatibility shims. It trades developer flexibility for absolute system predictability.

By understanding these constraints, one understands why the system can confidently support 10,000 active instances on a negligible resource footprint. We build the rigid box so that the mind can wander freely inside it.