Stage 05 · current
A production boundary for legacy code
FastCGI, nginx, one stateful worker, bounded queues, systemd isolation, health checks, and a deployment that can coexist with Lasso 9.
Read stage 05 →Build notes from the compatibility line
The project, in stages
A chronological account of how scattered documentation became an executable contract, then a warm production worker.
Stage 04
Frameworks expose the real gaps
PageBlocks and LFB established the application fixture pattern. Knop expands it into old-style custom definitions and custom types.
Read stage 04 →Stage 03
From a list to 1,572 contracts
Each recovered feature gained a semantic expectation, including explicit unavailable behavior where emulation would be dishonest.
Read stage 03 →Stage 02
From a broad vision to one dependable runtime
The initial vision ranged from Lasso 1.x through 8.6. Production work concentrated on the last well-documented release while leaving the broader idea open for the future.
Read stage 02 →Stage 01
Recovering the language surface
Manuals, examples, definition stubs, archived projects, and source packages became a local evidence base.
Read stage 01 →Not the original binary
Same application language, different machine
Lairu Legacy does not contain the proprietary Lasso Server, SiteAdmin, LCAPI modules, or its historical process model. It recreates documented observable behavior in Rust and marks host-bound integrations unavailable when a faithful substitute is not present.
Read the detailed comparison