Skip to content

Start here ​

UniversalToolchain is a modular .NET compiler/runtime framework. Wist is its reference language and packaged formula API. The repository also exposes a separate External Language Authoring SDK for independent non-Wist languages.

Choose the correct surface ​

You need to...Use
validate restricted numeric formulas and compile typed delegatesUniversalToolchain.Wist; start with First Program
create an independent language package with your own syntax artifacts and backendsUniversalToolchain.LanguageAuthoring; start with Language Authoring Quickstart
configure a shipped Wist language/runtime surfaceWist .wistdialect profiles; start with Dialect Files
add syntax to the existing Wist frontend pipelinesupported Wist compiler-module contracts; start with Choose an Extension Type
understand implementation boundariesPhysical Project Map and Lowering Walkthrough

Core model ​

text
Wist application path
source -> Wist frontend -> Bytecode -> AIR -> optimizer/backend -> typed delegate or execution result

Generic language-authoring path
package descriptors + runtime registrations -> LanguageDefinition -> LanguageCompiler -> LanguagePlan -> LanguageRuntime -> typed artifact route -> exact backend executor

The generic SDK does not force every language through Wist AST, Bytecode or AIR. Those are Wist/framework artifact protocols, not universal mandatory stages.

Current maturity ​

  • The package currently verified from NuGet.org is UniversalToolchain.Wist 0.1.0-alpha.1.
  • The repository source candidate is 0.1.0-alpha.7; it is not published on NuGet.org.
  • Both are alpha surfaces for controlled evaluation and prototypes, not stable 1.0 contracts.
  • Generic language authoring is a low-level alpha with typed routing, deterministic planning and runtime lifecycle contracts.
  • Restricted composition is not a hardened sandbox.
  • Public evidence and current gaps are tracked under Evidence and Release Status.

Public developer manual. Internal reviews, proposals and maintainer material live under internal-docs/.