Current Scope
Atlox is an active platform and language experiment. The documentation describes both the implemented vertical slice and the architectural contract guiding the next stages.
Available in the current application
The app/ workspace currently demonstrates:
- projects backed by a Rust runtime and SQLite;
- a semantic tree with stable node identities;
- virtual source files rendered from that tree;
- command-based edits and restricted text regions;
- immutable semantic commits and hard reset;
- compiler diagnostics, logs, Run, and browser preview;
- a small ordinary Atlox surface for types, state, functions, and HTML.
Foundation under construction
The broader design includes generated storage, transactions, maintained views, durable processes, effects, compatibility, reconciliation, mixed-version execution, rollback, and physical planning. Each capability must be proven through executable applications rather than documentation alone.
Non-goals
Atlox should not:
- hide missing domain decisions behind automatic guesses;
- turn every value into a database handle or evidence wrapper;
- require a special DSL for every runtime subsystem;
- make generated infrastructure impossible to inspect;
- preserve obsolete syntax or data paths merely for compatibility during research.
The standard is practical: ordinary application code should remain ordinary, while the semantic codebase and runtime remove duplicated representational work.