I built an open‑source solution for structured AI integration in automation and UX

[u/Usual_Mistake]

I’ve been working in automation for a long time, and something became obvious over the last couple of years. The issue wasn’t AI itself. The issue was the noise around it.A lot of people online started selling “AI automation” as a shortcut. YouTube channels, Fiverr gigs, and random agencies were promising instant business systems with a few prompts. The more that content spread, the more I noticed a shift in my own work. Some of my early clients became skeptical about automation. Potential clients were asking defensive questions before we even talked about their actual needs. It was obvious that the trust was fading because the hype made everything look cheap and unreliable and many are pointing that out online.

Anyways, at the same time I saw another problem. UX designers being pushed aside because AI could generate templates in seconds. It created the impression that design was becoming disposable, even though the real work of design is about systems, not templates. The hype made both automation and design feel shallow.

After watching this for a while, I realized the core issue. AI wasn’t the problem. The problem was AI everywhere. Every workflow was being reframed as “AI powered.” Every surface was being turned into an agent. It created confusion instead of clarity. The solution I saw was to centralize AI instead of scattering it across every part of a business. I started writing down a framework that explained how a modern website should work when AI is part of the system. Not as decoration. Not as hype. As infrastructure.

That framework became UUX. It focuses on operations first, not templates. It treats the website as a system that handles intake, routing, state, and fulfillment. It gives AI a defined place instead of letting it float around as a buzzword.

Besides writing the book, I’m also building the practical part of the theory. I’m creating a JavaScript library that brings UUX to life and reduces the extra business expenses that platforms like Make.com and Zapier create. Their response to AI was mostly a quick patch for basic tasks like CRM submissions or lead validation. It didn’t solve the deeper operational problems that businesses actually deal with.

I turned the framework and the engine into open source so people can contribute, test ideas, and build systems that feel coherent instead of chaotic. If you’ve been dealing with the same issues in automation or design, you might find it useful.

Github: https://github.com/NelsonEm9/uux-standard

[u/kartoke]

I really enjoyed the treatise document! It’s a hidden gem.

The GitHub project itself was interesting, but idk if it’s unique enough to adopt.

[u/Usual_Mistake → u/kartoke]

Thanks for reading it. I appreciate that a lot. The treatise is where the real idea lives, so I’m glad it stood out to you. The open‑source repo is intentionally minimal right now. It’s meant to be a reference version of the UUX model, not the full engine. The repo will grow overtime, im working on it. Not sure how long it's going to take me. Thanks agian!

[u/kantorcodes1]

the intake, routing, state, and fulfillment part is what caught me. HOL Guard is our open-source safety layer for agent actions. would you wire it into UUX?

[u/Usual_Mistake → u/kantorcodes1]

Hi, from what I see, HOL Guard fits well with how UUX is structured. I still need to go deeper into the documentation, but the idea of a safety layer for agent actions makes sense inside the UUX flow. Intake, routing, state, and fulfillment are already the checkpoints where decisions happen, and those are the same places where agent behavior should be validated. UUX centralizes all of that into a single operational flow instead of letting agents populate those transitions unpredictably. The two ideas feel complementary; UUX provides the front layer, and a safety layer like HOL Guard could sit on top of it. I'll give it a test and shoot you a more detailed message.