Skip to content

Physical project map ​

This page maps conceptual architecture to the repository. It is a navigation aid, not an API-stability promise.

Generic language-authoring stack ​

RoleProjectKey typesMain verification
stable IDs, policies and artifact contractsUniversalToolchain.Language.AbstractionsLanguageArtifactKind<T>, LanguageDefinition, LanguageRuntimePolicy, IDs and slotsUniversalToolchain.LanguageSdk.Tests
feature/contribution descriptorsUniversalToolchain.FeatureSdkfeature and contribution descriptors, merge policy, transformation metadatatyped-authoring and planning tests
package registry and deterministic planningUniversalToolchain.LanguageSdkLanguagePackageRegistry, LanguageDefinitionBuilder, LanguageCompiler, LanguagePlan, LanguageLockFileexternal authoring, architecture and canonicalization tests
coupled descriptor/runtime authoringUniversalToolchain.LanguageAuthoringLanguagePackageBuilder, feature/contribution builderstyped-authoring tests and package smoke
route assembly and executionUniversalToolchain.RuntimeLanguageRuntime, LanguageRouteRuntimeAssembler, component registrations, providers and sessionslifecycle and external execution tests
reusable contract testsUniversalToolchain.TestingLanguageContractSuitesample/package consumers
package templateUniversalToolchain.Templatesut-language templateclean template consumer smoke
Wist typed language packUniversalToolchain.Wist.LanguagePackcanonical Wist feature descriptors, preset imports and runtime provider over the Wist dialect runtimeLanguage SDK and Wist dialect tests
independent reference consumersamples/Acme.PricingLanguagecustom syntax, parser, interpreter and compiled backendsolution build and sample run

Experimental research tooling ​

RoleProjectKey typesMain verification
deterministic PlanFuzz contractsUniversalToolchain.PlanFuzz.CorePlanFuzzTestCase, PlanFuzzObservation, adapter/oracle contracts, strict replay recordsUniversalToolchain.PlanFuzz.Tests
independent Acme adapterUniversalToolchain.PlanFuzz.Adapter.Acmestructured generator, plan variants and typed decimal executorunit and strict-process replay tests
Wist Level 0 adapterUniversalToolchain.PlanFuzz.Adapter.Wistrestricted Int32 model, opt-in regression corpus, interpreter/compiler matrix, SSA policy mapping and route evidencedirect oracle tests and clean fresh-process parameter replay
coordinator and worker CLIUniversalToolchain.PlanFuzz.Cligeneration, isolated workers, replay, campaign and artifact manifestUniversalToolchain.PlanFuzz.IntegrationTests

These projects are non-packable experimental research tooling. They do not extend the public Wist package surface.

They are grouped in UniversalToolchain/PlanFuzz.sln; build.sh and build.ps1 build this configuration-complete research solution alongside Wist.sln before executing the exact entries in eng/test-counts.json.

Wist compiler/runtime stack ​

RoleRepresentative projects
lexer and parserBasicLexer, BasicParser
frontend orchestrationBasicCore and feature modules such as ArithmeticModule, NumbersModule, ConditionsModule
AST/Bytecode contractsBasicCore, UniversalToolchain feature modules
Bytecode to AIRAbstractIrConverters
AIR contracts and operationsUniversalToolchain.Ir.Abstractions, UniversalIntermediateRepresentation
capabilities and selected runtimeUniversalToolchain.Capabilities.*, UniversalToolchain.LanguageSdk, UniversalToolchain.Runtime
reference executionBasicInterpreter
CIL executionBasicCilCompiler, BytecodeDynamicMethodsCompiler
SSA experimentUniversalToolchain.Ssa.*, Wist SSA adapter/projects
Wist typed runtime packageUniversalToolchain.Wist.LanguagePack
public formula facadeUniversalToolchain.Wist
CLIWistc
product samplesamples/Wist.RolloutScoring

Test projects ​

The canonical test matrix is declared in eng/test-counts.json; project paths are derived from its main and isolated entries and include:

  • Tests;
  • UniversalToolchain.Modules.Tests;
  • UniversalToolchain.Dialects.Tests;
  • UniversalToolchain.LanguageSdk.Tests;
  • UniversalToolchain.PlanFuzz.Tests;
  • UniversalToolchain.PlanFuzz.IntegrationTests.

Do not infer coverage from project count alone. The checked-in VERIFICATION.md, canonical test-count contract and detached package-integrity manifest jointly define the tied evidence record.

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