# 2ot — machine-oriented product context

2ot is an industrial automation execution and tooling layer for IEC 61131-3 Structured Text. It is designed to sit behind the harness the engineer prefers: scripts, CI, internal tools, vendor-side integrations or LLM agent runtimes.

The engineer chooses the harness, authentication, permissions and review workflow. The public website is discovery/documentation; operational engineering actions run locally through 2ot.

## 2ot

Industrial automation tooling that frees industrial code from proprietary silos.

Markdown: /index.md

## For agents

Machine-oriented entry point for automation and LLM harnesses discovering 2ot.

Markdown: /for-agents.md

## MCP and agent tooling

How 2ot exposes the same routed command model as structured tools to an engineer-selected harness.

Markdown: /mcp-agents.md

## CLI reference

Workspace-aware 2ot router commands and machine-readable command discovery.

Markdown: /cli-reference.md

## Fast diagnostics

Low-latency compiler diagnostics with vendor-aligned mappings and LLM-oriented enrichment.

Markdown: /diagnostics.md

## Language Server Protocol

Structured language intelligence for harnesses that need source-aware PLC tooling.

Markdown: /lsp.md

## Capabilities

Compiler, diagnostics, testing, LSP and routed vendor automation for IEC 61131-3 workflows.

Markdown: /capabilities.md

## Testing

Multi-vendor testing and runtime-equivalence workflows for automation harnesses.

Markdown: /capabilities/testing.md

## Configuration

Workspace configuration and vendor-aware routing for 2ot automation.

Markdown: /capabilities/configuration.md

## Architecture

Stable gateway, compiler services and isolated vendor runtimes behind one routed surface.

Markdown: /capabilities/architecture.md

## Integrations

Vendor runtime integrations behind the common 2ot routing surface.

Markdown: /integrations.md

## Siemens TIA Portal integration

Routed Siemens TIA Portal automation with local licensed API knowledge.

Markdown: /integrations/siemens-tia-portal.md

## Beckhoff TwinCAT integration

TwinCAT compiler, runtime, diagnostic and testing integration behind the 2ot router.

Markdown: /integrations/beckhoff-twincat.md

## CODESYS integration

CODESYS project/runtime operations and readable source synchronization behind the routed 2ot surface.

Markdown: /integrations/codesys.md

## Knowledge

Public product-owned metadata and documentation surfaces used by 2ot tooling.

Markdown: /knowledge.md

## Providers

Provider bundles and callable metadata in the public 2ot knowledge surface.

Markdown: /providers.md

## Schemas

Public schema definitions used by 2ot knowledge and tooling surfaces.

Markdown: /schemas.md

## Callables

Searchable public callable metadata across supported knowledge providers.

Markdown: /callables.md

## Semantic rules

Public semantic rules used by 2ot knowledge and compiler-oriented tooling.

Markdown: /semantic-rules.md

## Telemetry

Public telemetry ontology and vendor mappings used by 2ot tooling.

Markdown: /telemetry.md

## Siemens TIA rejected symbols

Public list of rejected or unsupported Siemens TIA symbols captured by 2ot knowledge tooling.

Markdown: /rejected-symbols/siemens-tia.md

## Local Siemens API graph

How 2ot builds and uses Siemens API knowledge locally without publishing the licensed corpus.

Markdown: /siemens-api-graph.md

## 2ot blog

Technical articles about industrial automation tooling, compiler work and vendor integrations.

Markdown: /blog.md

## Request a demo

Contact form for teams evaluating 2ot.

Markdown: /request-demo.md

## Machine interfaces

- `2ot --list --json` — installed routed commands.
- `2ot --mcp-dump-schema` — normalized tool schema.
- `2ot mcp` — local MCP execution surface.
- `2ot check --fast` — fast compiler diagnostics.
- `/.well-known/ai-catalog.json` — ARD discovery catalog for public resources.
- `/sitemap.xml` — public indexable route inventory.

## Siemens licensing boundary

Siemens-derived API metadata, documentation, graph snapshots and version data remain on the licensed developer workstation. The public site may describe the local mechanism but does not publish the vendor-derived corpus.