A classic PLC project is often a one-way street:
Mechanics define something, electricians connect it,
and software developers try to somehow tie everything together.
With Selmo, that changes.
Because the behavior is described formally,
all parties can read and understand the same model.
The mechanic sees: “My cylinder is state 2.”
The electrician knows: “Here is the valve signal.”
The programmer no longer has to “interpret” anything.
This creates a shared understanding – and sources of error are drastically reduced.
