ONE OF TWO VALUES

Creating.

Making things that didn't exist before.

I grew up with the ideas, not the engineering chops. For most of my life that meant the ideas stayed where they started, in notebooks, in conversations, in the back of my head. AI changed that math. The cost of getting a thing from "what if" to "shipped" collapsed, and the bottleneck moved from skill to taste, judgment, and willingness to actually finish. So I started finishing. This page is the long version of what that looks like in practice. Three surfaces, one habit. The first is AI Systems, the layer underneath everything I build. The second is Publishing, where I write the books I wish had existed for my younger self. The third is Building, where ideas become products with users and revenue and lives of their own. Different formats, same instinct: see something missing, sketch the shape of it, then keep working until it exists in the world.

SUB-BUCKET 01

AI Systems

The infrastructure under everything else. AI isn't a feature I sprinkle on at the end. It's the team I build with from day one. AI Systems is how I help organizations and individuals stop treating AI like a procurement question and start treating it like a capability question. Strategy when the moves aren't obvious. Automation when the work is repetitive and load-bearing. Co-creation when an idea exists but the path to ship doesn't. Three offers, one belief: tools are cheap, judgment is the constraint.

SUB-BUCKET 02

Publishing

Books are the slowest format I work in, and the one I'm most patient with. Publishing under Zaceos covers the long-form writing that doesn't compress well into a tile or a tweet. The first project here is Evergreen Elementary, a children's book series built around the developmental skills schools rarely teach explicitly. There's a second long-form manuscript I'm working toward a 2027 release on. Both share a frame: take the ideas adults assume kids will absorb by osmosis, and write them down properly.

SUB-BUCKET 03

Building

Building is where ideas turn into products. Five of them live here right now, each at a different stage and pointed at a different audience. Some are for industries I've worked in. Some are for communities I'm part of. One is for the kitten arriving this spring. The common thread is that none of them would exist if I had to write every line of code myself. They exist because I treat AI as the execution layer and my job as the editor, integrator, and person who decides what gets shipped. If you want to see what "non-coder with AI" actually looks like at scale, this section is the answer.

WHAT'S NEXT

Two values, one practice.

Creating is half of what I do. The other half is the inverse: not making things, but making people. If you want the rest of the picture, read about Empowering. If you have something specific in mind already, the fastest path is a conversation.