Mixed Versions And Rollback

Always-on systems routinely execute more than one program revision. Atlox makes coexistence an explicit runtime condition rather than an accidental deployment window.

Pinned execution

An admitted function call, workflow, and effect uses immutable definition revisions. Work that has already started does not silently switch to a new body halfway through execution.

New requests may use the target revision while retained requests and workflows continue on an older revision.

Certified projections

Old and new code access one logical application world through revision-specific projections. Semantic history identifies continuing stored fields and records the transformations or policies needed where representations differ.

Target-only writes are enabled only when retained readers, rollback policy, and information-loss rules permit them.

Rollback is not time travel

Traffic rollback selects an older program revision for new work. It does not erase state committed by newer code, repeat external effects, or reconstruct information that was explicitly forgotten.

Compensation, data restore, semantic rollback, and roll-forward are different operations. The runtime reports which one is possible from the evidence it retains.