The Whole Application Model

Atlox treats an application as one logical system rather than separate backend, frontend, worker, and infrastructure projects.

The ordinary source kernel remains small:

type  immutable logical values
let   immutable lexical bindings
var   mutable places whose owner determines lifetime
fn    computation with inferred reads, writes, suspension, and effects

Routes, exports, authorization boundaries, external effects, and adapters add explicit boundaries where the outside world requires them. They do not create unrelated programming models.

What belongs to the model

A complete application includes:

• logical values and durable places;
• functions, queries, and browser output;
• authorization and invariant definitions;
• durable processes and external effects;
• compatibility and retention promises;
• semantic edit history;
• physical objectives such as latency, freshness, locality, and durability.

Not every item needs a dedicated source keyword. Some are inferred from ordinary code, and some are attached through semantic editing or explicit boundary declarations.

What does not belong to application meaning

Tables, indexes, partitions, cache entries, processes, and network protocols are physical realizations. The runtime may replace them without changing the logical value or function observed by application code.

One semantic revision can therefore compile into several target programs and physical plans while remaining one application.