Transactions And Authority

Atlox infers transaction requirements from ordinary functions instead of creating a separate transaction language.

One admitted invocation

An exported call, route command, event delivery, workflow resume, test, or REPL command can admit a function as an outer invocation. If its call graph writes application places, the invocation becomes one atomic logical transaction.

Authorization, reads, queries, validation, and writes observe one coherent snapshot plus writes staged earlier in that invocation. Internal calls join the same transaction.

Validation and retry

The runtime may execute optimistically. Before commit it validates the observations that influenced the result. A conflict discards the staged work and retries the complete invocation before exposing an unknown outcome.

Application code does not add retry loops or isolation-level syntax. The compiler knows which reads, queries, writes, and invariants require validation.

Authority is separate from mutation

Read and write inference says what a function does. Authority says who may ask it to happen.

Authorization policies and capabilities are stable semantic definitions evaluated against the same coherent state as the operation. Distribution may change where authority runs, but it cannot create two unnoticed authoritative outcomes for the same governed scope.