{
  "id": 945530,
  "title": "Why We Parse Industrial Code Instead of Embedding It",
  "url": "https://urgent.news/2026/08/15/why-we-parse-industrial-code-instead-of-embedding-it",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-15T03:37:56.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/nodeblue/why-we-parse-industrial-code-instead-of-embedding-it-5dko"
  },
  "original_language": "en",
  "account": "Most industrial AI applications consist of a retrieval pipeline with a chat interface. The manuals are chunked, embedded, and placed into a context window; the top matches are then presented to the language model. While this approach demonstrates well, it breaks down when the question's answer relies on the current state of the machine. Nodeblue, an applied research lab, developed the Nexus system, which focuses on a different architectural decision: the language model is merely the smallest and least interesting component. The core issue was revealed through a test that compared eleven frontier models against a live production controller with a live edit present in the processor but absent from the archive. All eleven models confidently provided incorrect answers, relying solely on the archived version they had never seen before. When the same models were used on the Nexus engine, they accurately cited the correct rung. The models did not enhance their performance; they simply had access to a fact residing in the processor rather than a corpus. Parsing industrial control programs has four layers: deterministic parsing of ladder logic, structured text, AOIs, UDTs, tag databases, and device configurations into a resolved model. Every claim made by the model includes the corresponding rung, tag, or document, enabling professionals to verify the output. The system processes real exports from live floors, including files too large for chat interfaces, and employs OPC UA reads and subscriptions to access the running controller. This layer, involving physical, on-premise, and safety-gated work, is challenging for AI but necessary. Benchmarks conducted by independent controls engineers with no affiliation to the project yielded zero errors, confirming the model's accuracy. The Nexus engine's connectors are publicly available under the MIT license at github.com/Nodeblue-AI.",
  "summary": "Most of the industrial AI you have seen is a retrieval pipeline with a chat box on it. Chunk the manuals, embed them, stuff the top matches into a context window, let the model talk. It demos well. It falls apart the first time somebody asks a question where the answer depends on what a machine is doing right now. We are an applied research lab called Nodeblue, and the system we build is called…",
  "key_points": [
    "Nexus system prioritizes language model as core component",
    "Parses ladder logic, structured text, AOIs, UDTs, tag databases, device configs",
    "Benchmarks show zero errors with independent controls engineers"
  ],
  "editors_take": "Parsing industrial code instead of embedding it enables more accurate AI applications by providing direct access to a machine's current state, allowing for verifiable and reliable output from language models.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}