language intelligence · one semantic model

PLC code that understands the whole workspace.

2ot turns IEC 61131-3 source into a revision-bound semantic workspace for diagnostics, navigation, refactors and agent context—without routing interactive analysis through vendor runtimes.

workspace snapshot

One source of semantic truth

low-latency path
01
Editor / harness
LSP requests · 2ot context
02
Workspace model
files · overlays · revisions
03
Analyzer
diagnostics · symbols · CFG / dataflow
04
Common HIR
one cached project representation
05
Parser + source
revision-bound CST · ranges · source index
// interactive compiler intelligence
Parse once.
Reason across files.
Respond everywhere.

The language server is not a second compiler. It consumes the same project model so editor feedback, automation and command-line analysis converge on the same source relationships.

LSP
standard protocol
HIR
shared project model
CFG
semantic depth
project-aware language surface

Everything an interactive engineering loop needs.

Agent semantic context →
file + range

Diagnostics

Publish errors on the file that owns them, including cross-file project diagnostics.

workspace

Navigation

Definitions, references, document symbols and workspace symbols stay project-aware.

semantic

Refactors

Rename and code actions operate on semantic relationships rather than text search.

interactive

Completions

Completion, hover and signature help use compiler-known source context.

source-aware

Semantic tokens

Source classification follows parsed and resolved program structure.

compact

Agent context

A bounded 2ot context request packages selected language features for automation harnesses.

data flow

A revision enters once. Every consumer sees the same program.

Editor overlays stay distinct from disk state, project diagnostics retain source ownership, and target-specific compiler legalization stays downstream of the common language model.

01

Source revision

Disk files and editor overlays resolve to one workspace revision.

02

Common frontend

Parse, index and lower source once into revision-bound compiler facts.

03

Semantic model

Symbols, references, types, control flow and diagnostics share the same cached project model.

04

Language surface

Editors, scripts and agent harnesses consume standard LSP plus compact 2ot context.

agent-native by design

The same language intelligence can feed humans and agents.

A harness can request bounded diagnostics, hover, completion, signatures, symbols, code actions, definitions, references, rename information and semantic tokens instead of reconstructing context from logs or grep.

For agents →
fast path

No vendor IDE in the inner loop

Interactive diagnostics and semantic requests stay on the compiler/analyzer path. Siemens TIA Portal, Beckhoff TwinCAT and CODESYS remain stronger verification authorities when a workflow explicitly needs vendor evidence.

implementation note

The architecture is converging on this end state

The active LSP work already covers workspace indexing and editor overlays. The roadmap is finishing the shared, target-neutral project model and located project diagnostics before deeper semantic diagnostics become the normal production path.