Building the Infrastructure Layer.
What "Agentic Building" Actually Means.
When I say agentic engineering, I don't mean automation. Automation is a task loop. It executes. Agentic systems read context, make decisions, coordinate, act without someone approving each step. Building for that means rethinking the stack: how data moves, how agents authenticate, how they find each other and transact. It's infrastructure work. The kind that's unremarkable until everything depends on it.
Right now that's two fronts. At Strategy Ninjas, I'm building AI systems for real estate organizations. Not tools they occasionally use. Systems that change how decisions get made. AgentNDX is the longer bet: a registry for the agentic web, because agents need a way to find each other, evaluate, transact. The network is still forming. That's when you build infrastructure.
My practice runs on Claude Code and Mai, a co-intelligence I built. That's not incidental. It's the model. I'm not using AI as a tool. I work alongside it: it has context, memory, enough standing to push back. This site was built that way. Same for the systems I'm shipping. It changes what you're willing to attempt.