Articles · Industry & Machines
Who told this cell to do that?
On a factory line, instructions cross between machines all day and nobody can prove where they came from. LineSeam puts two keys at every joint and leaves the answer in writing.
By Lucian · Lux Automations
The problem
A modern plant is not one machine. It is robots, controllers, sensors and plant systems passing instructions to each other, with vendor laptops and remote sessions crossing in from outside. When something goes wrong, the first question is simple: who told this cell to do that. In most plants, nobody can answer it with proof.
The research behind the product page names why that gap matters. Attackers live inside plant networks for 42 days on average in operational technology, and 119 ransomware groups targeted industrial organizations in 2025, figures reported by Dragos as vendor research. Six weeks inside the plant before anyone knows is a long time to move quietly. When the line finally stops, the forensic trail usually stops with it: nobody can prove which instruction crossed, or from where, or under whose name.
That is not a failure of effort on the floor. It is a failure of the crossings themselves. The joins between systems were built to pass work along, not to ask who is knocking, what they are allowed to ask for, or to write down that the crossing happened at all.
The technology
LineSeam puts the house guard at the plant’s seams. One engine runs underneath it, the same engine that runs under every door on this shelf: Amos checks who is knocking, SeamGuard checks the joins between systems, and every check leaves a signed receipt.
At every joint, two keys must agree. The first key is identity: the machine, program or person crossing holds an issued identity in its own name, not a borrowed login or an assumed one. The second key is mandate: what this identity is allowed to do at this joint, for this purpose. Identity and mandate must both say yes before an instruction crosses.
When the two keys disagree, the crossing stops. It does not settle things alone. It escalates to a person, who can look at what was asked, who asked, and decide. Vendor sessions are treated the same way as any other crossing. The laptop that crossed in is on the record, with its session receipted like everything else, so a visit that was legitimate at the time stays provable afterwards.
What it changes
For the plant and the integrators who build its lines, the change is a record that survives the incident. Instead of reconstructing events from memory and scattered logs after a stoppage, the team holds a signed trail of instructions and sessions: who crossed, where, and under what mandate. The dwell-time figures describe plants that never had that trail. LineSeam is built so a plant does.
It also changes the everyday conversation about access. A vendor’s presence is no longer a matter of trust taken on faith and forgotten. It is a named session, scoped to its mandate, with a receipt the plant can read. A crossing that should not happen is stopped at the joint and handed to a human, rather than discovered weeks later.
Nothing here claims the line cannot be attacked. The claim is narrower and more useful: every instruction crosses under two keys, every crossing leaves a receipt, and the question the floor asks after any incident — who told this cell to do that — has an answer in writing.
See it
LineSeam guards the joins on a factory line, with every crossing checked and receipted. LineSeam — the product page · All the house articles · Lux Automations — ailux.ca