NIMOS / ENGINES / LSPIntelligence
← THE BUILD SYSTEMLSPIntelligence
THE CODE READER
Language Server Protocols & Code Intelligence
The language servers that let an agent read types and diagnostics instead of guessing.
DRAWN BY THE HOUSE
One mark per engine, on one grid, in one hand.
5
TOOLS
OPENCODE
WIRE
PARTIAL
THIS BUILD
LSPs are wired in the editor; qa/proof.md records no project diagnostic snapshot.
THE PROOF LEDGER →WHAT
What it is
Five tools: TypeScript language server, the extracted HTML/CSS/JSON servers, Tailwind language server, Tailwind Oxide and tree-sitter.
WHY
Why it exists
An agent that greps is an agent that guesses. Diagnostics, symbols and definitions before an edit are what separate typed work from prose.
HOW
How it runs
The LSP block in the OpenCode config, eight servers wired and verified. tree-sitter handles surgical parsing when a file is too large to read whole.
WHEN
When it runs
Always on. Especially refactors, TypeScript projects and Tailwind systems.
WHO
Who owns it
CEO owns the reader; Research watches servers and grammars; Build keeps per-project config; Data snapshots diagnostics; Ops repairs the queue.
TOOLS
The registry
The engine manifest is the source of truth. These are its entries, including the ones that are not used on this build — the proof ledger says which is which.
typescript-language-server
lspFull TypeScript intelligence, completion schemas and real-time type checking.
vscode-langservers-extracted
lspSeparate HTML, CSS, JSON and ESLint diagnostics servers.
tailwindcss-language-server
lspStrict CSS token verification and auto-completions for Tailwind setups.
@tailwindcss/oxide
npmNext-gen high-speed compilation engine accelerating massive styling workflows.
tree-sitter-cli
binStructured concrete syntax trees — parse agents read/edit code without breaking brackets.
5 registry entries. The proof ledger on the Gantry page says which of them this build actually used.
RUN
Run it
ENGCTL / THE ENGINE FLOOR
$ engctl show lspintelligence$ engctl awaken lspintelligence$ engctl install lspintelligence --dir ./site`engctl` is the registry control surface. `awaken` checks wiring before it activates a cell; `install` writes the parts into a project.
PROOF
On this build
PARTIAL
ALL ELEVEN ENGINES →LSPs are wired in the editor; qa/proof.md records no project diagnostic snapshot.
N/A and PARTIAL are stated, not hidden. The ledger is generated from this project, not from a template.
LIMITS
What this does not claim
PARTIAL in the proof: the editor wiring exists, but qa/proof.md records no project-level diagnostics snapshot. The next step is to write one.
The engine is the how. The brief is the start.