One engineer, a habit of fixing the same thing twice

I’m Shiva. I work inside the systems that big companies run on: invoice capture and approval platforms, statistical process control across manufacturing plants, OPC servers pulling data off factory floors.

That work has a pattern. A platform handles the common case well, and then something at the edge goes wrong in exactly the same way at the next client. A customer asks which AI tools you use and nobody has the list. A vendor gets paid twice because the invoice number had a dash in it. A plant pays a heavyweight licence to read a few hundred tags.

I kept writing scripts to catch these things. Kriosity is what happens when those scripts grow up: each one becomes a small, finished product with a clear price, so the next team doesn’t need a consultant to get the fix.

The name comes from curiosity and crystal. The mark is a gem cut into facets, one for each product, and it grows a facet whenever a new one ships.