Stage 03 · Conformance
From a feature list to 1,572 contracts
Recognition tests answer “can it be named?” Semantic tests answer “does it do the right thing?” The project requires both.
One contract per recovered feature
The generated suite covers substitutions, members, commands, processes, containers, constants, symbols, delimiters, and data types. Each case supplies executable source plus an expected output, error, response header, status, or state effect. Structural and syntax-only features assert their parse shape and tokens.
Unavailable is a behavior
Some Lasso features were thin entry points into proprietary connectors, server administration, or host components that cannot be reproduced faithfully from public evidence. Those 49 surfaces are still recognized. They return explicit, tested unavailability instead of silently succeeding or producing invented behavior.
Release gates
The broad manifest is backed by focused Rust integration tests for databases, files, sessions, security, cryptography, XML/XSLT, image and PDF work, mail protocols, networking, threading, numeric formatting, FastCGI framing, queue pressure, recovery, and soak behavior.