Workshop
Those who are in love with practice without knowledge are like the sailor who gets into a ship without rudder or compass and who never can be certain whether he is going.
Leonardo da Vinci, Notebooks, section 19, trans. Jean Paul Richter (1888)
I build AI systems to run my own work. Each page here shows what I built and how it works.
Project list
- The village site (2026). I built my portfolio with AI as a walkable Roman harbor town. Every page also reads as plain text.
- Fleet Console and Campaign Map (2026). I built one dashboard to run all my projects and direct my AI officers, plus a planning method to go with it.
- Knowledge base (2026). I built a library for my AI officers so they work from sources I picked and cited. Each idea sits in its own file, so an officer loads only what a task needs and logs what it can't find.
- The officers (2026). I set up AI officers that each own one field of my work and bring me the next step. None acts on its own until a clean run of work earns my sign-off.
- Public skills library (2026). I publish the Claude skills I wrote for my own work. Each is rewritten first so nothing private ships, and credited where the idea came from someone else.
How I build
I build my AI to work as an extension of me. It knows my products, my voice and my standards, and I decide how it reads all of that before it says a word. That's why my skills, my files and my software are built the way they are. At work, it's why our sales team's product library comes with a prompt pack beside it.