What SymLan Is
A language framework for values that become usable only after a run resolves and validates them.
The Gap
Many computational workflows produce important values only after execution: clusters, attractors, embeddings, learned codebooks, sampled states, calibrated thresholds, and post-run registries. Conventional languages can store these values, but they rarely make the unresolved phase explicit.
SymLan makes that uncertainty part of the type discipline. A value can be declared, pending, or resolved. A pending vocabulary cannot be used as if it were already known.
Declared / Pending / Resolved
Declared
The source names a substrate model, run conditions, readout method, or validation threshold.
Pending
The program has a handle to a proposed value, but that value cannot be sent, exported, or asserted as resolved.
Resolved
The run has completed and the value has passed the declared measurement and validation gates.
Two Phases, One Program
Phase 1 - Arena Specification: declare a substrate model, constraints, run schedule, readout method, and acceptance thresholds.
Phase 2 - Vocabulary Use: operate only on values that have been resolved and accepted by validation.
Reference Backend
The current reference path is simulation-backed. Physical backends such as chemical oscillator arrays, VO2 devices, and photonic systems remain research targets and are not yet validated against the reference simulation path.
Why It May Matter
The useful core of SymLan is not a claim that a future substrate already exists. The useful core is a disciplined way to describe experiments where the vocabulary is unavailable until after a run, then require that vocabulary to pass explicit validation before it can be used.
Next
Read the Research Preview v0.3 for the conservative framing, then the Claims Ledger for evidence levels.