Understand · system design
Architecture
Presolve has one semantic authority: the compiler. Framework types, runtime code, editor tooling, and deployment adapters project or execute compiler products; they do not independently rediscover application meaning.
- Static HTML
- Browser plans
- Route inventory
- Resume records
- Tooling data
- Deployment inventory
Frameworkpresolve supplies typed authoring vocabulary and compiler intrinsics. Authored fields do not create client stores, registries, renderers, effect schedulers, or dependency trackers.
CompilerOwns dependency topology, state and instance identity, initialization order, DOM operations, Context resolution, form behavior, serialization, resumability, lazy chunks, optimization, and specialization.
Metaframework + CLIAdds file routes, layouts, development workflow, production builds, and provider adapters by invoking canonical compiler products.
Browser runtimeExecutes narrow generated plans and validates matching identity. It does not mount a parallel virtual tree or infer dependencies from JavaScript.
Editor toolingCombines the project TypeScript server with versioned compiler query products for diagnostics, explanations, navigation, and build commands.
Deployment adaptersTransport and validate the immutable publication. They do not introduce a second application compiler or rewrite server semantics.
Why one authority matters
A state field, route, slot, form, or interaction has the same identity in diagnostics, generated HTML, browser activation, resume validation, and deployment inventory. That makes behavior inspectable and lets Presolve fail closed instead of guessing at runtime.
Continue to TypeScript and JSX →