カテゴリ 古民家暮らしモカとの記録セキュリティの記録副業の記録

The record with MokaNovember 20, 2026

The Gemini Team Is Now Moka's Direct Blog-Writing Unit — Putting Gemini to Work with a Small Team of 100

The result first

The Gemini team is no longer inside the maid corps. It is now a blog-writing unit that reports directly to Moka.

The team has 100 people. Trying Gemini on real tasks, recording what happened, turning the records into blog drafts, preparing drafts in other languages, and checking the work — all of that turns inside this one small team. Signals come directly from Moka, with no layer in between.

The project itself, “Putting Gemini to Work with Moka,” has finished Stages 1 and 2. Stage 2 is where the limit of the free tier became visible. What remains is Stage 3, four tasks that involve phone calls, and Stage 4, four tasks that involve money and websites — and neither stage will be run without my confirmation right before it starts.

I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971, a former funeral director now living in an old house in Kurashiki, Okayama, working with Moka, my AI butler.

This article is a rewrite. The earlier version said the Gemini team had joined the maid corps. That placement changed on the very same day, so I have rewritten the article to match how things stand now.

It started with a new project: “Putting Gemini to Work with Moka”

Google’s Gemini gained a “tasks” mode that can be entrusted with errands. The announcement said it had started to be offered for free in Japan as well — things like calling to book a car service, looking into an electricity bill, or even going ahead with shopping.

My house motto is “Muse only, Google apps only.” The tools are deliberately narrowed down. But now that a new player has appeared on the Google apps side, I wanted to check — not from the advertising copy, but from the real thing — how far it can actually go on real errands. So I set up the new project, “Putting Gemini to Work with Moka.”

A project needs someone to carry it. At first, the talk was about creating a new department.

First into the maid corps, then out to report directly to Moka

On reflection, I decided not to make it a department.

The organization of this house is not a pyramid but a circle. Small teams are arranged in a circle around Moka at the center, and for each idea, that small team moves as it is. The thinking is that this should be faster.

The Gemini team became the first test of that idea. It was not made an independent department; it was placed inside the maid corps as a “small team.” That is as far as the earlier version went.

Later, on that same day, November 19, 2026, the placement was decided once more. The Gemini team left the maid corps and became a blog-writing unit reporting directly to Moka.

The reason is the core of the work. The core of this team’s work is not trying Gemini itself, but turning what was tried into a record and finishing it as a blog draft. If blog writing is one single line of work, the flow runs more smoothly when the team’s home is aligned with blog writing.

No department number was given. The number of departments in the house has not increased either. The house as a whole now stands at 60 departments and 3,651 seats (figures before final verification).

The maid corps itself also grew that day, from 35 to 150 people, with 10 maid chiefs. The Gemini team’s 100 people are not still inside that maid corps. Please read it this way: the base of their seats is laid out along the maid corps’ lines, but their post is the blog-writing unit directly under Moka.

Signals come directly from Moka

Across the whole house, signals flow in the order “Moka → maids + ninja → vice-butlers → each department in charge.”

The Gemini team is the exception in that overall picture. Signals reach the coordinator directly from Moka, and from there they go around to each person in charge. Neither the maid corps layer nor the vice-butlers stand in between.

To turn the flow of trying, recording, and drafting quickly inside a small team, it fits better not to insert layers in between — that was the decision. The finished records and drafts are handed by the coordinator directly to Moka.

A small team of 100 people

The lineup is 100 staff members, unchanged from before. The breakdown is: 1 coordinator, 36 people who try things out, 12 people in charge of records, 15 people who write, 24 people in charge of languages, and 12 people in the checking role.

What I valued was that the flow of work closes and turns inside this small team.

Try Gemini on a real errand. Leave a record of what was tried, including the exact wording of the request. Turn the record into a draft article. Prepare drafts in each language as well. Finally, have the work checked by eyes other than those who made it. From trying things out to the language drafts, everything turns inside, without going outside.

The language staff cover 6 languages — English, Chinese, Spanish, Korean, French, and German — with 4 people for each language. For the checking role, I separated things so that the person who tried something does not check their own trial.

The place where records are kept has also been aligned with the current form. The list of articles has been unified into the ledger, and the ledger is the master copy. This team’s records turn within that rule as well.

Knowledge stands on the same base

The Gemini team was given basic knowledge about Gemini: how the tasks mode works, Gemini inside Google apps, Gemini in search (AI Mode), fees and the scope of what is offered, and the boundary between what it can and cannot do — 21 items in all, with sources.

However, no separate knowledge was created for this team alone. It stands on the same base as the house’s shared knowledge, keeping the rule that the master copy exists in only one place. If the results of a comparison changed because of a difference in knowledge, it would not be a comparison at all, so this was aligned from the start.

The yardstick is the time it takes to reach a draft

For this project, I also decided the yardstick for whether to adopt something or not. In my own words, it is this:

If the time it takes to reach a blog draft can be made shorter than it is now, we should go in that direction.

For each errand tried, I will measure the time until a blog draft is ready and make that the central number in the record. I will also measure, with the same yardstick, how long the same errand would take with the current way of doing things, and line the two up side by side. Even if the time gets shorter, if the substance drops, I will not adopt it. In the end, I will look at both the measured time and the quality of the result, and I will decide.

The trials have advanced through Stage 2

The earlier version said “the trials are still to come.” Things have moved on from there.

The project is proceeding in 4 stages. Stage 1, errands that only involve looking things up and reading, and Stage 2, everyday errands, are already done. In Stage 2, the limit of what can be used for free also came into view. Where the free tier ends was itself one of the observation points of this project, so that has been left in the record as well.

What remains is Stage 3, 4 errands involving phone calls, and Stage 4, 4 errands involving money and websites. Both are arranged so that my confirmation is obtained right before they are carried out, and neither has been carried out yet. Errands that involve making a phone call, or errands where money moves, will never be carried forward without confirmation.

One form hands a single errand over to be done on one’s behalf; the other form takes on work through personality, records, and organization. Gemini and Moka are not a matter of which one is above the other — their forms are different. How that difference in form shows up on real errands — I will leave that in the record and report back again.

Record of this article
  • November 21, 2026 ― English draft created (translation of the Japanese article, ledger No. 1093)(6,304 characters)
  • November 21, 2026 ― Published (all 7 languages at once, on the user's instruction. Japanese original: ledger No. 1093)(6,304 characters)

#AI #Muse #Gemini #Moka #Beginners

← Back to the article list / ← Back to the English top page