Clark IPE is the Integrated Production Environment — the first and primary product in the Clarkware family. It is a workstation-level application built on Eclipse Theia that brings job context, inspection, firmware, evidence capture, and network coordination into a single environment at the bench.
A conventional IDE brings together the files, tools, logs, and workflows a software developer needs. The IPE does the same for industrial production: it unifies work instructions, operator notes, machine interactions, firmware workflows, inspection criteria, audit trails, and coordination threads into one workstation environment.
Paper job travellers that get lost. Printed IPC binders that are never contextual. Separate PCs for firmware loading with no version tracking. Manual inspection logs in shared spreadsheets. Phone calls for cross-node coordination. The IPE replaces all of this with a single, coherent, networked workstation.
Theia is a professional-grade, open source framework for building IDEs and tools, maintained by the Eclipse Foundation. It is the same platform behind tools from Red Hat, IBM, Google, Arm, and EclipseSource. Clark chose Theia for seven specific reasons.
Theia's architecture is extension-first. Every feature, including core features, is implemented as an extension using InversifyJS dependency injection. Clark can build a production workstation that looks and behaves nothing like a code editor while building on a maintained, community-supported codebase. No fork required.
The frontend (TypeScript/HTML/CSS) renders the operator interface. The backend (Node.js) provides services: hardware device communication, broker connections, file access. They communicate via JSON-RPC over WebSockets. This separation means hardware drivers and network services live on the backend while the operator UI stays clean and responsive.
Language Server Protocol support means any language with an LSP server — C, C++, Rust, Assembly, Python — gains full IDE capabilities inside the IPE. For firmware work, clangd provides autocomplete, go-to-definition, and inline diagnostics without custom implementation.
Debug Adapter Protocol connects any debugger. OpenOCD's GDB server bridges to DAP, giving the IPE source-level hardware debugging: breakpoints, stepping, register inspection — all from within the same workstation, using the JTAG probe already on the bench.
Theia supports VS Code extensions at the plugin API level. Cortex-Debug, PlatformIO, ARM assembly highlighting, RTOS awareness plugins — the embedded development community's tools are available on day one without rebuilding them.
Theia AI (CODiE Award 2025) provides LLM communication, agent orchestration, prompt management, and tool-calling built into the platform. Clark uses this to build inspection agents, defect analysis agents, firmware advisory agents, and audit summary agents — all logged alongside human actions.
The IPE is designed to offer complete sovereignty and privacy to its operators. All data stays on the facility's own infrastructure. There are no built-in mechanisms that report data back to Clark, no telemetry, and no expectations that operators share anything with the network. If a facility chooses to connect to a Clark-coordinated network, data sharing is selective, operator-controlled, and governed by the facility — not by Clark.
Theia is governed by the Eclipse Foundation under the Eclipse Public License 2.0 — a commercially friendly licence. Unlike VS Code (Microsoft-controlled, cannot be white-labelled), Theia is specifically designed for this kind of product building.
The IPE presents five primary panels within the Theia shell. The layout is operator-configurable but defaults to a consistent arrangement.
The active job view. Displays work order, part number, revision, BOM, customer, and current traveller step. When a job is scanned in, the panel populates from the Clark platform. The traveller is a sequence of gated steps — the operator progresses by completing required actions and logging evidence. This is the digital replacement for the paper traveller.
Contextual IPC-A-610 inspection guidance. During inspection steps, the panel surfaces the applicable workmanship criteria for the assembly class. The operator logs each point as Pass, Fail, or Process Indicator. The Theia AI inspection agent can assist with defect classification from a description or photograph.
The integrated firmware environment. Monaco editor with clangd LSP for code intelligence, a flash interface connected to the physical JTAG/SWD programmer, and a binary version ledger recording exactly what was loaded to which unit. Every flash event is logged and published as a CFX message.
Chronological evidence log for the current job: scans, inspections, firmware loads, signatures, photos, and AI-generated notes. The operator captures photos and attaches them to job steps. AI summaries are generated on demand. This panel produces the compliance documentation.
Persistent bar showing operator ID, IPC certification status, active job, CFX broker connection, node ID, and cross-node job indicators. The Clark network context is always visible without navigating away from the active work.
Every significant IPE event — job opening, inspection completion, firmware flash, unit completion — becomes an IPC-CFX v2.0 message. The IPE maintains a persistent AMQP broker connection. Each node runs its own broker; node brokers connect to the Clark platform broker. IPEs work fully offline with a local broker and sync when connectivity returns.
The February 2025 CFX v2.0 release introduced human workstation message types: OperatorActivity, WorkInstructionCompleted, SignoffRequired. These are the IPE's most direct alignment point with the evolving standard. Clark also publishes a custom FirmwareProvisioned extension under the com.clark.ipe namespace for firmware traceability.
The IPE defines four specialised agents using the Theia AI framework. All agent interactions are logged alongside human actions in the audit trail.
Assists during IPC inspection steps. When an operator is uncertain about a condition, the agent queries the IPC criteria database and suggests the applicable criterion, classification, and disposition. The agent's recommendation and the operator's final decision are both recorded.
Reviews defect records against the job's historical pattern, suggests root causes and corrective actions, and generates structured defect reports in CFX format.
Available during firmware steps. Answers questions about target firmware, explains binary parameters, and identifies implications of version changes using DWARF debug information as context.
On job close, generates a structured summary: steps completed, inspection results, defects, firmware versions, operator IDs, and timestamps. The summary is appended to the job record for customer delivery.
Native application on a workstation PC. No browser, no network dependency for the frontend. Full hardware device access. The default for production workstations — fast, offline-capable, and the most deployable option for corridor nodes.
Frontend in a browser, backend on a local server. Suitable for shared workstations or thin-client deployments where multiple operators share infrastructure.
Lightweight read-only views (audit panel, network status) hosted as web pages. Useful for customer dashboards and management visibility without requiring hardware access.
The current build boots the Theia shell, renders the four primary panels, and supports profile CRUD. Task detail interaction and job workflow integration are next. The IPE is being developed against Theia 1.69.