This is an earlier explanation of the language design. For the current design choices and an example, open Philosophy.
Lispex keeps the familiar shape of Scheme and gives every program one fixed reading. Core and derived forms normalize canonically, built-in procedures come from one registry, and explicit input produces a deterministic observation.
A complete language surface
The language contract defines the syntax available to every file. A form such
as guard enters as a named part of that contract, with its normalization,
runtime behavior, diagnostics, and direct checks delivered together.
This makes a Lispex source file readable from the language contract itself. The same source and input retain the same meaning across the reference runtime, artifacts, and later releases.
Exact artifacts
Lispex source can move through canonical images, Core IR, bytecode, receipts, and Vouch. Each representation records its identity and the next consumer in the product chain. The host application supplies data, transaction context, and external actions explicitly.
The current philosophy page connects these principles to every public product.