One worker. One workshop.
Perceptron is not the output of a committee. It is written, tested, signed and supported by a single pair of hands — and the file below is open for inspection.
FILE №1
Scott Waters
Twenty years of building and operating production systems taught me which tools professionals are actually missing — so I build them. My work spans iOS and mobile apps, ERP and network tooling, field-ops software, and AI-driven development pipelines, from embedded devices to full web platforms. Reliability isn't a value statement; it's what happens when the person writing the software is also the one answering the support call.
§ 02 — RECORD OF SERVICE
| YEARS OF SERVICE | Twenty, in production systems that other people depend on |
|---|---|
| DISCIPLINES | iOS and mobile · ERP and network tooling · field-ops software · AI-driven development pipelines |
| RANGE OF LABOR | From embedded devices to full web platforms |
| POST HELD | Author, maintainer, and the voice on the other end of the support address |
§ 03 — WHY PERCEPTRON EXISTS
Perceptron began in frustration. The old scanners parade a column of numbers before the worker — an address, a hardware code, and silence — and call it an accounting. Across a network of dozens or hundreds, that number answers nothing: not what the device is, not what it does, not whether it belongs there at all. A machine no one can name is a machine no one can govern!
So the work was done properly. Perceptron sets four protocols to labor at once — mDNS, SSDP, DNS and SNMP — and holds their findings against the manufacturer registries until every device on the wire surrenders its true name, its maker, and its purpose. These are the facts the operator needs when a fault must be found and a record must be kept. Let no device on the wire remain a stranger!