I started building Lunea because most systems are good at recording activity and much worse at understanding what that activity means. Dashboards can tell you what happened. I wanted to see how far I could push software toward understanding the work itself.

That has meant dealing with the parts that are easy to skip in a demo: state that has to persist, permissions that have to fail closed, authentication, databases, APIs, simulations, evaluation, bad deployments, edge cases, and deciding what the system should never be allowed to do.

I’m keeping the product itself private for now. What I can show is the build: I took it from an idea to a real system, broke it more than once, rebuilt it, and kept raising the standard for what it has to survive.