Project structure

Scalable structure without content baggage.

The blueprint keeps content intentionally thin so the architecture stays visible: page shell, tokens, components, runtime scripts, and documentation all separated cleanly from the start.

Core rule

Structure should help the engine, not fight it.

Pages stay thin. Components stay token-driven. Runtime settings only touch shared contracts. Content can grow later without breaking the adaptation layer.

`styles/`

Base tokens first, then layout, components, and theme overrides.

`scripts/`

The engine owns state and root variables. UI script owns drawers, focus, and form wiring.

`pages/`

Only page-level composition belongs here. Repeated patterns should move into shared classes, not local hacks.

`Truth.md`

The project manual explains what to preserve as the site evolves.