Process flow

The same board, speaking process engineering instead of software. Place vessels, pumps, valves, exchangers and instruments, and join them with streams and signals — a stream is a pipe and draws solid, a signal is an instrument line and draws dashed, exactly as it would on a P&ID. The types carry the rules: a utility comes from off-unit so nothing on the drawing feeds it, an instrument signals a valve and never a vessel, and a unit boundary groups equipment without ever being an endpoint itself. A control loop is a cycle by definition — a transmitter moves a valve, the valve moves the process, the process moves the transmitter — and this board draws it, which is the thing a graph tool that refuses cycles cannot do at all. Review then reports what a reviewer would ask: a vessel nothing feeds, a valve nothing controls, an instrument signalling something the vocabulary says it cannot. This plate is the argument that the vocabulary is data: it adds no code and changes no control, and every button, dropdown and toggle on the toolbar is the one the software-architecture plate declares, populated from this catalog instead.