Language specification
L expresses values, program structure and behavior through grammatical sentences. This specification describes the current language and its Rust target; start with the first program to see them together.
Scope and conformance
Section titled “Scope and conformance”The maintained repository contracts govern source bytes, ownership, declaration identity and execution. Lyger translates L into AML/logeme compositions; Logiceme generates Rust source; Cargo builds the native program. Running that program starts the orchestrator, which controls separate App processes. Generating source alone does not run it.
Reading the specification
Section titled “Reading the specification”The type reference answers two questions: what does this value represent? and what role does this word play in a sentence?
Table: scroll horizontally to read all columns.
| Family | What it describes | Examples |
|---|---|---|
| Primitive Types | Individual data values and managed references. | Text, Number, Truth, Thing, Bytes, Pointer, Null |
| Iterative Types | Collections and named-member namespaces. | List, Map, Dictionary |
| Lexical Types | Grammatical roles of words. | Nouns, Verbs, Adjectives, Adverbs, Articles, Prepositions |
| Applicational Types | Application structure and behavior. | App, Service, Class, Object, Function |
These are related dimensions: App is a noun grammatically and names an applicational type. Each page starts with the complete category table, including names with limited support.
Read lexical structure for literals and paragraphs, names and scope for binding and visibility, and grammar for sentence forms. Definitions, control flow, imports, and execution explain how those pieces become a program. Consult errors and the glossary for diagnostics and terminology.
The builtin reference documents implicit words; the standard library documents explicit imports. Native definitions use the separate logeme model and Rust target contracts.
Role, support, and evidence
Section titled “Role, support, and evidence”Tables distinguish executable behavior, recognized but incomplete forms, and internal representations. The evidence guide explains example labels and verification stages.
Code blocks marked l contain L; rust contains native fragments; text may contain grammar notation or AML. Native Rust syntax inside a definition does not become ordinary L syntax.
Language guarantees and target limits
Section titled “Language guarantees and target limits”Source ownership, binding and raw captured output follow the language/runtime contracts. Cargo layouts, Rust encoding and native library visibility describe the current target. Native macOS/Linux execution is supported; cross-compilation, in-code concurrency, general async source functions and automatic Deferred execution are outside this release. L manages ownership for its typed runtime values; opaque native definitions retain explicit Rust lifetime and generic contracts. Releases embed English resources and follow the pre-1.0 compatibility policy.
Sources and review
Section titled “Sources and review”See architecture, CLI/runtime semantics, validation policy, and the error model. Semantic mappings and the specification audit record source evidence and unresolved support boundaries.
Canonical source: docs/spec/index.md.