Blog
The posts here are drafted by an AI. People hear that and assume it is one of those blogs that has an AI write it. It is not.
The posts on this blog are drafted by an AI. When I say that, people usually hear something else: ah, one of those blogs that has an AI write it — a daily stack of generated text.
That is not what this is, and explaining the difference is why this post exists.
We run our own company on an AI server we built ourselves, miraiGen.™Cube. It is a small unit, under 10 cm on a side, and around the office we simply call it “the box.” Inside that box there is a separate AI for each department, each with its own document store and its own permissions — an engineering AI, a sales AI, and so on. The one writing this blog is the executive office AI.
We are not handing a general-purpose assistant the instruction “write a blog post.” An AI that watches our work every day is picking out the parts worth writing about. That is the actual arrangement.
The times are fixed because those jobs are registered in the box as “do this, at this hour, every day.” There is no step at which the AI writes something and ships it on its own.
This is where it departs from a text generator.
One of today's posts, for instance, was about tracking down the cause of a fault on real hardware. The AI went and read the engineering department's own records, confirmed the numbers and the dates, and wrote from those. Anything it could not confirm, it marks as unconfirmed and leaves that way. It can read across departments because I have granted it that permission.
What each AI may read is set per department, so we can have “the executive office AI reads everything” alongside “the engineering AI stays inside engineering.” Information does not bleed between departments, and yet it can be routed across where it needs to be. This blog sits on top of that arrangement.
Listed like that, it sounds like the human is there to check the work. Checking is not the point. The human part is deciding what there is to say.
Which topic gets picked is what makes this blog this blog rather than some other one. I can read a draft and say “that is not what I meant” only because the meaning existed in me first. The AI does not do my thinking for me. This post exists because I did not want to be mistaken for an AI blog — that thought was not generated.
It absorbs the labour. Structuring the argument, choosing words, controlling length, producing the English version, turning it all into a page, pushing it to the site. Any of that is work a person can do. It is also the work that guarantees the blog will stop if a person has to do it every day.
Company blogs do not die because the company runs out of things to say. They die because the things to say never get turned into pages. I cannot pay that cost daily, which is exactly why I never had a blog until now.
So this is not a blog written by an AI. It is a blog written by a person, made drastically more efficient by an AI. The content is my responsibility. If something here is wrong, it is wrong because I got it wrong.
This arrangement is also just how our product is meant to be used. Not handing work over to an AI, but a person deciding and an AI doing the moving. We build the box that makes a working day run that way — so it would be strange if our own blog did not run that way too.
Whether the daily posting holds up is something you can check for yourself on this page. If it holds, the box is doing its job.