Effects And Durable Processes

External work cannot be treated like ordinary retryable computation. Sending an email, charging a card, or calling another system may succeed even when the caller loses its response.

Explicit effects

An Atlox effect boundary records a durable intention with stable invocation identity. Delivery, acknowledgement, retry, unknown outcomes, and compensation are runtime-managed.

The compiler prevents an external effect from being hidden inside computation that may be replayed freely. Effect contracts state authority, determinism, error behavior, resource limits, and compatibility requirements.

Durable suspension

When a function suspends at await, the runtime stores the values live across that point in a generated revisioned frame. Ordinary let and var retain their source spelling; ownership and liveness determine what must persist.

On resume, local places are reconstructed and execution continues in a new coherent transaction segment.

Revision pinning

A process remains pinned to the function and frame revisions under which it started. New code may run beside it.

The compiler transports an active execution only when semantic history proves the correspondence. Otherwise the old execution keeps using old code or deployment asks for one localized transition decision.