Specifications¶

The public reference pages below render the maintained spec sources under docs/specs/. That keeps the full spec text searchable in the docs site instead of sending readers to GitHub.

Which spec should you open?¶

Question	Open
“What does IEC Structured Text itself allow?”	the language chapters `01` through `09`
“How does truST execute ST programs?”	10 Runtime Semantics
“How is the runtime platform structured?”	11 Runtime Engine
“What does the bytecode container look like?”	12 Bytecode
“How does debugging behave?”	13 Debug Adapter
“How does the editor/LSP layer behave?”	14 LSP
“How does ladder fit into truST?”	15 Ladder Diagram and 16 Ladder Profile truST
“How do the visual editors map onto one runtime model?”	17 Visual Editors Runtime Unification
“What is the current SFC scope?”	SFC Profile
“How are CONFIGURATION / RESOURCE / TASK declarations modeled?”	18 Configurations, Resources, and Tasks
“What files make up a truST project?”	19 Project Model
“What is the machine-facing runtime contract?”	20 Agent API v1
“What is the deterministic harness wire protocol?”	21 Harness Protocol
“How do source discovery and project-scoped commits behave?”	22 Developer Workflows
“Which connector status values are canonical?”	23 Connector Status
“What evidence is required for release claims?”	24 Release Evidence
“How are MQTT tag mappings configured and published?”	32 MQTT I/O

Use specification pages for exact behavior and contracts. Use Program for task-oriented programming docs.

Specification Set Overview¶

Language¶

Runtime¶

Tooling¶

Visual Editors¶

Integration¶

Published Source Index¶

This public site publishes the specifications listed above. Later internal contract specifications remain maintained in docs/specs/ but are not part of the public reference set.