Tooling

The instruments that surround the Clef compiler: the language server and editor integration worked through day to day, and the package manager that puts source on the build path without a runtime in the way. The set widens as the toolchain does, toward verification and the evidence a certification lab re-checks.

Start with the editor path

Leveling Up With Lattice describes the current integration direction and the first working editor loop. The shared implementation design assigns the work across repositories and defines the regression gates. The initial server is hosted in .NET and presents Clef semantics from CCS; the forks’ inherited F# services still need that connection.

Part of the toolchainStart here
Language rules and compiler factsClef specification, CCS, Composer
VSCode client and its bindingslattice-vscode, lattice-vscode-helpers
Neovim/Vim and lexical highlightinglattice-vim, clef-grammar
Earlier language-service implementationClefAutoComplete, retained as protocol and migration reference
Analysis slots and regression caseslattice-analyzers, with an active slot inventory alongside its inherited rule corpus
Memory, IPC and network contractsBAREWire, with target declarations from Fidelity.Platform
Data formats and native binding generationFidelity.Data, Farscape
SDK and OpenAPI binding generation for F#/FableXantham, Hawaii; the near-term bridge for work such as FSharp.CloudEdge
Richer compiler and proof viewsAtelier, with the WrenHello WebView example and Partas.Solid frontend bindings

The first Lattice gate needs the compiler and editor path. The other projects provide inputs or later consumers; they are not all dependencies of a basic editing session. Conclave is the platform for intelligent distributed systems in Cloudflare; BAREWire is the glue connecting its components.

The earlier AutoComplete proposal is retained as historical background. Its FSAC setup examples are superseded by the current CCS-backed integration.