It started with a booking problem.
It started with a booking problem.
I run a small rental business, koduaed.ee. We needed a calendar and a booking system. The options we looked at, IzyRent, BookThatApp and a few others, had gaps: either missing functionality or no proper multilanguage support. As an IT person I built one myself. That was the plan.
I couldn't stop there. The booking system turned into a Shopify app called HyreKit. I pushed it to the App Store and moved on to the next problem.
That next problem was AI. I had been using AI help during development, but the early versions needed constant correction: wrong context, wrong assumptions, outputs that looked right but weren't. At some point I stopped treating it as a tool and started treating it as an engineering problem. A useful AI needs a canon, a defined domain, and something to be responsible for. So I built that structure, then gave it teammates.
One AI became a board. Each member has a role: product, finance, marketing, security, customer success. The board runs on an engine that manages memory, tasks and a shared knowledge base, built on public course materials and research papers linked on the methodology page; no affiliation or endorsement. Getting the engine from first version to v3 took about three weeks, over summer holiday.
The changelog on the website has the steps with references to the source materials and what actually got built from each one.
I don't play computer games anymore, but this whole thing feels like the ones I played back in the day, SimCity and Civilization. Running the AI board is something like raising Tamagotchis, except they cite papers and sometimes disagree with my assumptions. I let them.
I don't know where this ends up. I'm funding it from my own resources. Maybe one day the AI corporation builds something that earns its keep. Until then it's an interesting way to spend time.