Introduction

Atlox is a language and runtime for complete applications. Code, durable state, browser output, and deployment evolve through one semantic program rather than disconnected source, schema, API, and infrastructure snapshots.

One application, many representations

An application feature is usually repeated as source types, database tables, API messages, client state, cache rules, background jobs, authorization checks, and deployment configuration. Those artifacts describe the same product decision, but developers must keep them connected by hand.

Atlox makes the logical application the source. Ordinary types, places, functions, and views state the values and behavior developers care about. The compiler and runtime derive storage, transactions, maintained data, protocols, replicas, and deployment work from that meaning.

A semantic codebase

The program is stored as stable semantic structure. Text is a readable projection. The compiler knows when a change is a rename, a new field, a new meaning, or an unresolved decision.

Definitions and references keep identity independently of names, files, and source positions. Accepted edits form an immutable history. Incomplete work can remain in an edit session without replacing the last accepted program.

Deployment is compilation

When deployment compilation succeeds, the runtime has enough information to begin the transition without a separately written migration project.

If a change needs domain knowledge that Atlox cannot infer, compilation reports a localized obligation. The developer resolves that question where the change was made. A clean semantic commit then produces reconciliation, compatibility, rollout, rollback retention, and cleanup behavior.

Atlox does not remove real databases, indexes, workers, messages, or containers. It changes who authors them: developers state application meaning, while the platform owns replaceable physical representations.