Skip to content

Glossary

These terms describe L and its implementation. They should not be replaced automatically with superficially similar terms from other programming languages.

TermMeaning
LexiconA selected natural-language grammar and configured vocabulary; English eng is the bundled choice
LexemeA word definition with grammatical role, inflections, and possibly source/native behavior
TokenOne source occurrence, retaining spelling, role, provenance, and binding
Sentence / statementSource grammatical unit terminated by the implemented punctuation rule
ClauseAn action and its owned subject/object/modifiers within a statement
PhraseA grammatical relation, commonly introduced by a preposition
SubjectThe source entity being declared or acted upon; pronoun antecedents use defined subjects
PredicateThe action/condition portion associated with a statement
ObjectAn operand or related entity in a grammatical action
ParagraphPhysical source grouping separated by blank lines outside literals/comments
Lexical scopeAn environment owning name bindings; distinct from physical layout and activation
ActivationA particular runtime execution context with its own planned local storage
DescriptorA source adjective definition constraining nominal targets and supplying construction/wrapper rules
AliasA binding edge preserving canonical identity of another declaration
Source unitA builtin, program, or dictionary ownership boundary
Source occurrenceA particular original or included file occurrence with import ancestry
DictionaryEither a collection/namespace value or an indexed vocabulary source unit; context distinguishes them

For these terms in actual L, read the annotated basic program. In The App Prints message, App is the grammatical subject and message is the grammatical object. A capitalized Object source category instead denotes the file-owning construction shown in the Class/Object example. A paragraph example shows why physical paragraphs and lexical scope must also be distinguished.

TermMeaning
AppApplication value and executable process target
ServiceSource organization within App construction; standalone declarations create no package or process
ClassRecursive module/source group, not a process or paragraph
ObjectSource-file unit, not an automatic runtime object scope
MainCanonical builtin descriptor selecting the bounded runnable entry construction
BasicBuiltin descriptor composing an App around a Main Service
ProcessSource-defined composition of supplied operation/body syllables
FunctionSource-defined callable composition; distinct from native Func metadata
OrchestratorGenerated entry executable controlling target processes and outer source instructions
InvocationOne accepted launch attempt and its immutable final result/continuation ownership
ContinuationParagraph-associated effects activated once by the first Await of an invocation
OutputFinalized raw captured stdout of the selected invocation
ErrorSelected process operation/invocation failure, separate from compiler lerrors

The App example puts Basic, Execute, and Output in context. Compare it with the explicit App lifecycle example and execution chapter: standalone Service declarations create no package or process, and awaiting a launched target owns its finalized result and continuation.

TermMeaning
LThe source language and its Go implementation/tooling
LygerFrontend compiling L through bindings and typed plans into AML/logeme markup
AMLAssembly Markup Language; structure/settings/content markup, not machine-code assembly
Observable AMLFrontend inspection view retained alongside backend-ready framing
Canonical backend AMLFramed input supplied to the backend without post-hoc source rewriting
Logiceme / logemeGo assembler/source-generation implementation in logiceme/
ExecutableBackend API source bundle; the object is not a running application
LucidTemplate language interpreting native source fragments
Logeme / segmentOne alphabet unit with logical ownership and target template
SyllableA vowel-centered composition with permitted optional determinants/qualification
SequenceSyllables combined/integrated/grouped using *, ^, and parentheses
GlyphBackend representation of a selected syllable and its children
Logeme systemOne target's segment templates and supported composition rules
MetaMetadata supplied to a glyph; allowed fields depend on the concrete form
Func / Prop / OpNative metadata records for functions/properties/operations, not new L types by implication
ConjoinmentTyped child-role input to a native composition
GenerationProducing source/artifacts; does not establish native compilation
Native compilationBuilding generated sources; does not establish runtime behavior
Runtime witnessActual supervised execution with observed output/lifecycle behavior
AcceptanceThe repository's unfiltered gate and protected-input checks for one revision/host

The target-independent model pairs B/A declare/declaration, D/E calculate/calculation, G/I evaluate/evaluation, F/O define/definition, H/U describe/description, K/W operate/operation, P/X iterate/iteration, M/Y instantiate/instantiation, and C/V execute-asynchronize/execution-asynchrony. These meanings guide composition; only the concrete frozen forms listed in the Rust reference are operationally supported.

Definitions follow architecture, source contracts, logeme model, AML, and Rust reference. The glossary is explanatory; its short definitions do not broaden a supported interface.


Canonical source: docs/spec/glossary.md.