capabilities · architecture

A small gateway in front of isolated runtimes

The calling harness sees one routed surface. Compiler, protocol and vendor work stay separated behind it.

harness
agent / CI / script
2ot gateway
workspace routing + schema
compiler
check / transpile
protocols
LSP / MCP
vendor runtimes
Siemens TIA Portal / Beckhoff TwinCAT / CODESYS
COMPILER ISLAND

Parsing, semantics and emission stay independent from vendor SDKs

Fast diagnostics →
2ot compiler pipelineCompiler stages from virtual files through syntax, semantic analysis and target emitters, connected to the shared incremental database.vfssyntaxhir-defhir-tyanalyzertranspilertarget emittersbase-dbSalsa incremental query graph
2ot transpile
transpiler
IEC source → target source
2ot check --fast
compiler
low-latency diagnostics
2ot lsp
LSP service
language protocol
2ot mcp
MCP service
agent transport
build / pull / push
vendor runtime
target environment
CONSEQUENTIAL ACTIONS

Reasoning stays above the enforcement boundary

The architecture is evolving so mutation, deployment and actuation pass through explicit policy and transaction semantics before reaching vendor or controller backends.

01
intent
02
policy
03
transaction
04
evidence
05
receipt