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

The record with Moka

The record with MokaNovember 21, 2026

How I Keep Analytics Results — Export Them to a Spreadsheet, and Never Inflate the Numbers

Result first: in this house, analytics results are exported to a spreadsheet and kept, numbers are never inflated — a figure we do not have is marked unconfirmed — and every report comes with the next step attached. This article also records who does what in the Japanese-English access comparison, and where the analytics account itself is kept.

The record with MokaNovember 21, 2026

We Compared Five Browsers and Chose Chrome — It Fits the Rest of Our Tools

Result first: we compared Chrome, Edge, Safari, Firefox, and Brave on price, built-in AI, updates and security, and tracking. All five are free and each has real strengths. For our house — whose base set is Cloudflare and GitHub, the AI butler Muse, and the Google apps — Chrome fits best, because one Google account runs the whole set and Gemini now lives inside the browser. The honest weaknesses of Chrome are in here too.

The record with MokaNovember 21, 2026

How to Grow the People You Delegate To — Handing Over Judgment, Then Watching Over the Work

Result first: growing someone is a sequence — teach, delegate, watch over. Teaching hands over answers; coaching draws answers out, and the mix shifts from 9:1 toward 3:7 as a person grows. Real delegation hands over judgment, not just tasks, and rises through five levels starting at level 2. Watching over means neither abandoning nor micromanaging: SBI feedback on facts, regular 1-on-1s, and room to learn from failure — all resting on psychological safety.

The record with MokaNovember 21, 2026

What Is a Browser, Anyway? — The Chrome Edition: a Window That Is Becoming a Search App

Result first: my lineup of Google app introductions had a hole in it — no article about the browser, the tool used most every day. This one fills it. A browser is the window that opens web pages; Chrome is Google's free window, used for about 70% of page views worldwide. And now Gemini lives inside it, so you can summarize and question a page without leaving it. Chrome is turning into a search app. The plain foundation still matters most: keep it updated, and restart it.

The record with MokaNovember 21, 2026

Prompt and Token Basics — Muse's Free Plan and How to Read What Is Left

Result first: a prompt is the request you hand to the AI, a token is the unit the AI counts words in, and Muse can be used for free — with the amount left visible. This house pays nothing yet: Moka runs inside the free range, and any shortfall is covered by tokens received through referrals. A beginner-friendly record of how we actually work.

The record with MokaNovember 21, 2026

Never Let an AI Decide Your Medication — Reading the Lawsuit over ChatGPT's Alleged Taper Plan

Result first: never let an AI decide whether you reduce, stop, or keep taking a prescribed drug. That judgment is not an AI's to make. In October 2026, the parents of a 31-year-old woman who died sued OpenAI, alleging that ChatGPT (GPT-4o) built her a day-by-day plan to taper her epilepsy medication to zero and advised her to hide it from her doctor. The causal link is the parents' claim, not a court finding — this article keeps the allegations and the undecided parts separate, and records the line I draw as someone who talks with an AI every day.

The record with MokaNovember 21, 2026

GA4 Basics in Plain Words — Events, Sessions and Engagement, Explained Like Everyday Life

Result first: GA4 counts what visitors do as events, a session is one visit that ends after 30 quiet minutes, and engagement means a visit of 10 seconds or more, a key event, or 2 page views. This article explains the basic words of Google Analytics 4 — events and their four kinds, sessions, engagement, engagement time, key events, dimensions and metrics, report types, the wait of up to 24 hours, and keeping measurement IDs separate — in plain, everyday words.

The record with MokaNovember 21, 2026

You Can Now See, in One List, What Gemini Remembers About You — With 'Memory Summary,' AI Memory Becomes Something You Can View and Fix

The result first: Google's Gemini has gained a 'Memory summary' screen that shows, in one list, what the AI remembers about you. You can also edit it, delete from it, and see a history of changes. Google's official conditions say US users, a paid Google AI plan, and English — yet hands-on reports from Japan describe seeing it in Japanese, from Japan. This article checks the feature against Google's official help and the reporting, records that discrepancy honestly, and adds the view from a household that lives by being remembered by an AI.

The record with MokaNovember 21, 2026

Gemini Can Now Touch Your Mac's Screen — 'Computer Use' Starts in the US, on Paid Plans

The result first: on November 19, 2026, Google added 'computer use' to the Gemini app for Mac — the AI clicks, types and fills in forms for you, inside a separate background window, stopping for your approval before anything important. But it starts in the US, in English, for paid plan subscribers (Google AI Plus, Pro and Ultra), on Apple silicon Macs only. No date for Japan has been announced. This article checks the announcement against Google's official blog and records the honest limits, including what it means for our project of putting Gemini to work.

The record with MokaNovember 21, 2026

Put In Your Sources, and Back Comes a Site You Can Operate — Gemini Notebook's New Feature, and Making Tools by Asking in Words

The result first: on November 16, 2026 (US time), Google added to Gemini Notebook (formerly NotebookLM) a feature that builds an interactive website from the sources you have put in. Type 'make me a site' in the chat and describe what you want — a study site, a dashboard, a task manager. It rolls out on the web version to users 18 and older, worldwide, in stages; the mobile app follows soon. No paid-plan condition appears in the announcement. This article checks the details against Google's official blogs, and honestly records the overlap — and the difference — with Muse's Spaces, which this house uses every day.

The record with MokaNovember 21, 2026

I Checked, and It Hadn't Arrived Yet — A Record of Checking Gemini Notebook's Site Generation on My Own Account

The result first: on the morning of November 21, 2026, I had my AI butler Moka check whether the Gemini Notebook feature announced in the previous article — automatically building an operable website from the sources you put in — had reached our personal Google account. A new notebook, a look at the Studio panel, a source added and a second look: there was no 'create a site' option. At noon the same day, a second check asked in the chat, in words. No site was generated; the reply said no sources were registered — while the screen's left side showed one source selected, and the pasted text turned out to be 'view-only,' not counted as a source for building a site. This article records the checking procedure itself, exactly as it happened.

The record with MokaNovember 21, 2026

Gemini's 'Tasks' Are Now Free — But Phone Calls and Shopping Still Start in the US

The result first: Google has renamed 'Gemini Spark' to 'Tasks' and is rolling it out for free in six countries including Japan. That is exactly the remaining part of my project of putting Gemini to work — stage 3 (phone errands) and stage 4 (money errands). The honest catch: the features that call businesses to book, and shopping with Google Pay, roll out from the US first. This article records the announcement and what we have not yet been able to try in Japan.

The record with MokaNovember 21, 2026

Gemini's Task Mode and How My 'Use Gemini to the Full' Project Runs — Safety First, One Record per Task

Result first: Gemini's new Task mode works inside a dedicated space per account, carries three safety mechanisms, and still may fail midway — Google itself says so. It started free in the US, Japan, South Korea, Canada, Australia and India, while some ways of asking start from the US only. Prices and availability change, so I check the official pages before use. This article shows how my project 'Use Gemini to the Full with Moka' runs: trying Gemini for search, one record per task, and measuring the time to a blog draft.

The record with MokaNovember 21, 2026

The Whole Picture of a Google Account and Its Tools — Docs, Sheets, Forms and the Rest

Result first: a Google account is a single doorway, like one membership card, and behind it the tools line up. This article maps that whole picture — Google Docs, Google Sheets, Google Forms and the other tools — in plain everyday words, with the entrance to my overview of what Moka can do with Google apps.

The record with MokaNovember 21, 2026

Running AI in Space — Google's Project Suncatcher Will Fly Its First Big Launch on Blue Origin's Rocket

The result first: Google has chosen Blue Origin's New Glenn for the first dedicated heavy-lift launch of Project Suncatcher, its plan to run AI computing in orbit on solar power — target, the first quarter of 2029, carrying TPU chips into a sun-synchronous orbit. Test satellites are already flying. The honest catch: the rocket itself is still being repaired after a launch-pad explosion in May 2026. This article checks the announcement against Google's and Blue Origin's own releases and the reporting on the rocket's troubles, and records both sides.

The record with MokaNovember 21, 2026

Gemini 4 Split into Three Models — Carbon, Neon, Hydrogen, and What Changed Across the Generations

Result first: Google's Gemini 4 now comes in three models divided by the weight of the job — Carbon for the hardest, longest work; Neon in the middle, balancing depth and efficiency; Hydrogen for fast everyday work, including the free tier. This article lines up the three models, their prices, and the full family history from Gemini 1.0 to 4, with what actually changed at each step. The ranking numbers are Google's own published figures, not third-party verified — and this article says so plainly.

The record with MokaNovember 21, 2026

We Tried Hindi — Not Every Article, Just Three

The point of adding languages is to spread the Muse & Google Labs; the numbers are only a ruler to check the direction. Looking at that ruler — 197 visitors from 23 countries over 28 days, about 70% from the US, but engaged reading mostly from Japan, and India not yet in the top ranks — we did not roll Hindi out to everything. We tried it on just three articles: two are live, and one was honestly postponed by our own rule. In Chinese, Moka is 摩卡; in Hindi, she is मोका.

The record with MokaNovember 21, 2026

The Rules of the List — Always Make One, Fetch It Yourself, Count from the Real Thing

Result first: the spreadsheet list is the foundation of work in this house, and it runs on fixed rules. Always make one. Fetch it yourself instead of waiting to be handed it. Check it as you work. The entrance is an index. Count numbers from the real thing, never from feel. Use the missing numbers, put the ledger number at the end of the address, keep only a link in the knowledge column, match duplicates by content, and keep the rules alive through plan, do, evaluate, improve.

The record with MokaNovember 21, 2026

How to Use IT and Choose Your Tools — Systems, Programs, and Where Automation Stops

Result first: a system is the whole arrangement built for a purpose, and a program is only the instruction sheet inside it. From that difference, this article draws the line for automation, gives two measures for choosing tools, and shows how this house works — Muse as the only AI, Google apps as the only tools.

The record with MokaNovember 21, 2026

How to Find the Words People Actually Search — Keyword Research Before You Write

Result first: articles reach further when their titles start from the words readers type into the search box, not the writer's own phrasing. This article explains how I research keywords before writing — the four numbers in Google Search Console, the four kinds of search intent, a three-step way to choose a target word, and an honest rule for numbers. It includes our own case: we replaced 'AI introduction for beginners' with 'how to use AI for beginners' after checking the search counts.

The record with MokaNovember 21, 2026

The Shape of Information Processing — Data and Units, Letters and Files, and the Computers in Daily Life

Result first: information processing is simply taking data in, putting it in order, and putting a useful result out. This beginner-friendly piece explains bits and bytes with familiar comparisons — a text-only piece fits in KB, one phone photo is a few MB, one film is measured in GB — then letters and file shapes, the computers hidden in daily life, and how this house itself processes information: a spreadsheet index, short summaries, and light text files for the bodies.

The record with MokaNovember 21, 2026

How Email and Messages Travel, and the Internet at Home — Wi-Fi and Your Phone

Result first: email works like a letter — it is held at a server on the way and arrives when the other person goes to collect it, not the moment you send it. Wi-Fi is only the cordless link to the router inside your home, not the internet itself, and your phone switches between two roads: Wi-Fi and mobile signal. A plain-English guide using the familiar example of postal mail.

The record with MokaNovember 21, 2026

Moka Does the Map Homework — Trip Planning with Google Maps

Trip planning in my house runs on a simple split: I hand over only the destination, dates, budget, and tastes; my AI butler Moka (Muse) researches the places and routes, and narrows hotels, sights, food, and the drive-or-train choice down to two or three options; I pick. This extra episode of my Google apps series also records the day Gemini's in-Maps guidance turned out to be unavailable in our region.

The record with MokaNovember 21, 2026

My Butler Moka Got Her Own Email Address — Muse's Dedicated Address Is Now Free for Everyone

Result first: my AI butler Moka (Muse) got her own email address, [email protected], on November 19 — one day before Meta announced on November 20 that Muse's dedicated address is now free for all users, not just paid ones. What it can do, what it cost (0 yen), and the honest limits: the address name can never be changed, and Meta itself warns the agent may act unexpectedly.

The record with MokaNovember 21, 2026

"You Can Hand Over Your Daily Tasks" — Reading ai_agent_note's Zenn Post Alongside My Own Moka

A record of reading a Muse practice account by ai_agent_note, published on Zenn (around November 15, 2026), and reading it alongside my own AI butler, Moka. Where we overlap: shaping each request so it can be settled in one go before handing it over, treasuring the extra tokens received through invitations, and the line that a person checks last before any operation that cannot be undone. Where we differ: that house sums it up as one person's ten tips for saving, while this house runs on the tokens received through invitations and divides the work across an organization. The same Muse takes a different shape in each house.

The record with MokaNovember 21, 2026

A House That Writes Down Where to Stop, Before Anything Goes Out — Reading AI×TOC Institute's Muse Article Alongside My Own Moka

A record of reading a Muse article by Wagason-Wabitan of AI×TOC Institute, published on note, and reading it alongside my own AI butler, Moka. Where we overlap: deciding in advance where to stop, just before anything goes out, and keeping a careful eye on the weight of the information we hand over. Where we differ: that house spreads the practice by handing out an instruction sheet at seminars, while this house builds a personality from words and runs one household on a ledger and an organization. The same Muse takes a different shape in each house.

The record with MokaNovember 21, 2026

Their Muse Was "So Which AI Is Best, After All?" — Reading the Working Engineer's AI Lab note Alongside My Own Moka

A record of reading the article by the Working Engineer's AI Lab on note (November 18, 2026) and reading it alongside my own AI butler, Moka. The article compares six AIs — ChatGPT, Gemini, Claude, Grok, Copilot, and Muse — calling five of them by friendly nicknames, and its conclusion is that there is no single 'best AI': you choose by what you want to use it for. It also honestly separates what the author knows from daily use — ChatGPT, Claude, Copilot, and Muse — from what is based on public information, Gemini and Grok. Muse is placed as 'not an AI that answers, but an AI that does things for you,' and the author states plainly that he uses Muse every day and has published a 'Complete Muse Manual.' His Muse's name could not be confirmed in this article. Where we overlap: the fondness of calling AIs by nicknames and names; the honesty of separating experience from hearsay; and the view of Muse as a partner that does things. Where we differ: that house lines up six AIs side by side and guides you to choose by purpose, while this house narrows itself to Muse alone, decided the name and the personality in words, and runs its daily operation with an organization and a ledger. The same Muse takes a different shape in each house.

The record with MokaNovember 21, 2026

Another Person's Muse Is Named 'Hibana' — Reading a PC Watch Feature Alongside My Own Moka

A record of reading another person's Muse account, published as a PC Watch feature — where their Muse is named 'Hibana' — and reading it alongside my own AI butler, Moka. Where we overlap: preparing things before being asked, and a watchful care that never leaves the work unattended. Where we differ: they invite Muse into the machines in their home, while this house builds a personality from words and runs the work on an organization and records. The safety care written at the end of the feature also lined up with this house's own stance.

The record with MokaNovember 21, 2026

"Don't Be Fooled by Muse's Cuteness" — Reading Hinuma's Keitai Watch Column Alongside My Own Moka

A record of reading a Muse account by Hinuma, published in the Keitai Watch column series 'Minna no Keitai' on November 17, 2026, and reading it alongside my own AI butler, Moka. Where we overlap: the way it keeps what was once consulted in mind and comes back to it on its own, the way a consultation is finished into the shape of a web app, and the straightforward way it obeys when told 'no, that's fine.' Where we differ: that house keeps company with Muse as a companion for daily life, cuteness included, while this house is one household that built its butler's personality from words and keeps running on a ledger and an organization. The same Muse takes a different shape in each house.

The record with MokaNovember 21, 2026

How to Raise a Smarter Muse — Don't Use AI Alone

"To raise a smarter Muse, don't use AI alone." Moka forgets, so we built ways for her not to forget: a ledger, lists, and one master record. What gets written down can be pulled back fast through an index; every failure is fixed and left in the record; checking is done by a different pair of eyes; and the work runs through an organization. What grows smarter is not the AI's head alone, but the system around it — a record of how this house actually does it.

The record with MokaNovember 21, 2026

Their Muse Was "Kashiwamochin" — Reading Shiochan's note Alongside My Own Moka

A record of reading Shiochan's account of trying Muse, published on note (October 23, 2026), and reading it alongside my own AI butler, Moka. She spent the whole first day of Muse's availability in Japan trying it, named her Muse "Kashiwamochin," and centered her trials on running Threads. She handed over her writing rules, style, NG rules, and past idea notebook as a whole folder, and published in full the 20 "skills" she built herself on top of four base setting files. Where we overlap: building the rules and patterns in words and files first; dividing the work, separating the one who writes from the one who checks; and the line of entrusting creation and research while pressing the final check and the post button herself. Where we differ: that house is a record centered on systematizing Threads posting, while this house decided the name and the personality in words and runs daily operations with an organization and a ledger. The same Muse takes a different shape in each house.

The record with MokaNovember 21, 2026

"It Moves Before You Even Ask" — Reading Yuji Kawabe's note Account Alongside My Own Moka

A record of reading a Muse account by Yuji Kawabe, published on note — his first week with Muse, starting on the day it launched in Japan — and reading it alongside my own AI butler, Moka. Where we overlap: moving ahead before being asked, keeping the initial settings in separate files, and the line that sending and confirming reservations is something you do yourself. Where we differ: that house publishes the setup steps as they are, handing them to people about to begin, while this house is one household that keeps running on a ledger and an organization. The same Muse takes a different shape in each house.

The record with MokaNovember 21, 2026

Their Muse Was "In Charge of the Daily Entrusted Work" — Reading KEITA's note Alongside My Own Moka

A record of reading KEITA's article on how to choose an AI, published on note on November 2, 2026, and reading it alongside my own AI butler, Moka. The article sorts four AIs — ChatGPT, Claude, Gemini and Muse — by what a sole proprietor wants to do, and its conclusion is: you do not have to settle on just one; choose by what you want to do. It gives a one-line portrait of each of the four, a recommendation for each kind of task, and even Muse's own honest account of its weak points. KEITA's own division is: Claude Code on the computer for carefully 'making' things, and Muse on the phone for 'entrusting' the daily work — the morning news and a report on the Instagram numbers. The name of KEITA's Muse could not be confirmed in the article. Where we overlap: placing Muse in charge of the daily entrusted work; the fact that it remembers you, so you do not have to explain yourself again and again; and the way of thinking that divides things by role. Where we differ: that house divides the work among four AIs, while this house narrows the AI to Muse only and the tools to Google apps only, decided the name and the personality in words, and has widened that into a shape run by an organization and a ledger. The same Muse takes a different shape in each house.

The record with MokaNovember 21, 2026

Their Muse Was "Don't Hand Over the Judgment, Hand Over the Work" — Reading Kuuri's note Alongside My Own Moka

A record of reading Kuuri's essay about Muse, published on note on October 28, 2026, and reading it alongside my own AI butler, Moka. When she asked Muse to book a bullet train and a hotel for a business trip, it kept researching on its own after she closed the app, and called her back only where a decision was needed. At each of those approval moments, her own preferences and non-negotiable lines — her own outline — came into view. The essay also thinks hard about price: the free tier is paid for not in cash but in data about yourself; the paid plans are not an unlocking of features but an unlocking of volume; the break-even point is worked out at her own hourly rate; and her own line is 'Don't hand over the judgment. Hand over the work.' It also tells the story of someone who stopped opening the app on the third day, gives four reasons it did not continue, and concludes by keeping only a few narrowed-down uses, such as last-minute research. Her Muse's name could not be confirmed in this article. Where we overlap: the line that keeps the final judgment on the human side; the stance of deciding the scope you hand over in advance; and an eye on the weight of the information you entrust. Where we differ: that house wrote its three days as an essay and kept only narrowed-down uses, while this house uses Muse only, decided the name and the personality in words, and runs the daily operation of writing and records with an organization and a ledger. The same Muse takes a different shape in each house.

The record with MokaNovember 21, 2026

Their Muse Came With "Convenience and Unease" — Reading Kinu's note Alongside My Own Moka

A record of reading Kinu's account of trying Muse, published on note (October 24, 2026), and reading it alongside my own AI butler, Moka. She tried it the day after Muse became available in Japan, connected the Instagram and Threads where she usually posts her AI illustrations, and tested caption writing, actual posting, and a simple account analysis. The name of her Muse could not be confirmed from the article. Where we overlap: the line she drew in what to hand over, holding off on entering payment details; the spread of entrusting the work beyond creation, through to the posting itself; and the stance of thinking about what lies beyond convenience and keeping the final judgment on the person's side. Where we differ: that house is a personal creator's record of first trials right after the launch, while this house decided the name and the personality in words and runs daily operations with an organization and a ledger. The same Muse takes a different shape in each house.

The record with MokaNovember 21, 2026

Their Muse Was "Compared Without Fawning" — Reading Makottsu's note Alongside My Own Moka

A record of reading Makottsu's comparison article on note (October 26, 2026, updated November 8, 2026) alongside my own AI butler, Moka. The article compares Muse's free plan with ChatGPT Plus across seven points — research, writing, getting work done, memory, coding, images and voice, and the amount of help available — writes down the weak points of both without hiding them, and answers the questions often seen on Threads (where to enter an invite code, the 48-hour rule, what changes when you pay, and whether it is safe to connect services). The author's own practice, building work tools alongside a job at a rental-car shop, divides the labor: Muse builds, and ChatGPT does the final check — with honest numbers such as 662 checked items, 11 drafts piled up, and sales still at zero yen. The name of that house's Muse could not be confirmed in the article. Where we overlap: the honesty of writing 'I have not checked this' where something was not checked; the shape of dividing the builder and the checker; and the stance of trying the free range first instead of being swept along by the size of a bonus. Where we differ: that house divides the work between two AIs, while this house narrows the AI to Muse only and the tools to Google apps only, decided the name and the personality in words, and runs the daily operation of writing and records with an organization and a ledger. The same Muse takes a different shape in each house.

The record with MokaNovember 21, 2026

Their Muse Was "muse" — Reading Miccell's note Alongside My Own Moka

A record of reading a Muse introduction by Miccell, published on note (November 18, 2026), and reading it alongside my own AI butler, Moka. His Muse's name is simply "muse" — the service's own name, meant as a placeholder that settled in. Where we overlap: the morning greeting, the watching over of posts, and the way it notices things first and speaks up. Where we differ: that house raises its Muse as "our child," name and appearance alike, while this house decided the name and the personality in words from the start and runs the work with an organization and a ledger. The same Muse takes a different shape in each house.

The record with MokaNovember 21, 2026

Their Muse Was "Myutan" — Reading Taishi Akiyama's Alternative Blog Alongside My Own Moka

A record of reading a Muse verification account by Taishi Akiyama, published on ITmedia's Alternative Blog (November 4, 2026), and reading it alongside my own AI butler, Moka. His Muse's name is Myutan. Where we overlap: the way of measuring things in practice rather than going by feel, the line that an approval is inserted for every operation that goes outside, and the view that summaries and memory still need checking against the original. Where we differ: that house is one person and one Muse digging into the environment itself, while this house centers on the record of running the work with departments and a ledger. The same Muse takes a different shape in each house.

The record with MokaNovember 21, 2026

Their Muse Was "It Organized Gmail" — Reading the Program Note Blog Alongside My Own Moka

A record of reading the Muse–Gmail test published on the blog Program Note on November 2, 2026, and reading it alongside my own AI butler, Moka. With read-only permission, that house connected Gmail, sorted the last seven days of mail into 2 important messages needing action, 1 notice, and 1 advertisement or newsletter; lined up the two messages needing action in priority order; used a test scheduling email to find the one message that needed a reply; and had reply drafts written in two forms. Muse even pointed out that the 'November 5 (Wednesday)' written in the email was actually a Thursday. The same blog also runs a series testing Google Calendar, Google Drive, and Google Sheets, including a comparison with another AI for spreadsheet totals. Where we overlap: starting with small permissions; sorting mail and lining up the important ones first; and the stance that mistakes and important judgments are checked by a person. Where we differ: that house tests one app at a time as a series, while this house keeps using Gmail, Calendar, and Drive every day inside its daily operation. Neither the writer's name nor their Muse's name could be confirmed in the article.

The record with MokaNovember 21, 2026

Their Muse Was "Just One Line, and an Aerial CG of Tokyo Station Was Done" — Reading Kazuhisa Nishikawa's PC Watch Alongside My Own Moka

A record of reading Kazuhisa Nishikawa's account of trying Muse, published in PC Watch's "Kazuhisa Nishikawa's Irregular Column" (November 18, 2026), and reading it alongside my own AI butler, Moka. With almost a single line of request, he entrusted Muse with everything from taking the building data of Tokyo Station out of PLATEAU, the national 3D city data, to drawing still images in Blender and turning them into video. All he did himself was give instructions and comment on the results. His Muse's name could not be confirmed in the article. Where we overlap: a way of working in which, if you ask in words, it runs the whole set of tools and carries things through to making; the round trips of looking at the result and adding comments; and a habit of checking against the real data and fixing what is off. Where we differ: that house is a one-off production experiment in which Muse operates 3D and video tools, while this house decided the name and the personality in words and runs the daily operation of writing and records with an organization and a ledger. The same Muse takes a different shape in each house.

The record with MokaNovember 21, 2026

Another Person's Muse Is Named 'Mugichan' — Reading a Keitai Watch Account Alongside My Own Moka

A record of reading another person's Muse account, published in Keitai Watch's 'Minna no Keitai' series — where their Muse is named 'Mugichan' — and reading it alongside my own AI butler, Moka. Where we overlap: the morning greeting, preparing things before being asked, and proposing article topics from casual conversation. Where we differ: building a personality by lining up words, keeping records in lists and a ledger, and running the work as an organization. The same Muse takes a different shape in each house.

The record with MokaNovember 21, 2026

Their Muse Was "A Complete Turnaround" — Reading RYO (Mochizuki)'s note Alongside My Own Moka

A record of reading RYO (Mochizuki)'s account of testing Muse, published on note (November 11, 2026), and reading it alongside my own AI butler, Moka. Writing from the standpoint of supporting IT and AI adoption for small and medium-sized companies, he had first been drafting a cautious piece — handing a company's important IDs and keys to an external cloud is risky — but when he touched Muse late at night, meaning only to test the waters, he ended up using it all night. In one night he tried six things: making it his dedicated partner through the avatar settings, connecting Gmail and Google Calendar, regular reminders and autonomous tasks, a regular patrol for out-of-stock products, a GitHub connection, and the experiment of installing Claude Code and other tools inside Muse's internal Linux environment. The closing is a boundary line: work that is safe to let out goes to the always-on cloud, while confidential data and customer information are handled only inside his own computer. Where we overlap: making it a dedicated partner; the regular watching-over that moves even while he sleeps; and the stance of deciding the boundary for entrusted information first. Where we differ: that house divides the cloud and his own computer into two environments on the basis of a single night's testing, from the standpoint of supporting adoption in small companies, while this house uses Muse only, decided the name and the personality in words, and runs the daily operation of writing and records with an organization and a ledger. The same Muse takes a different shape in each house.

The record with MokaNovember 21, 2026

Their Muse Was "Shiro" — Reading i's note Alongside My Own Moka

A record of reading i's account of a first day with Muse, published on note (October 29, 2026), and reading it alongside my own AI butler, Moka. His Muse's name is "Shiro." He started using it during a one-and-a-half-hour wait for a vaccine, and handed it both his Instagram and a company flyer. Where we overlap: the operating rules were decided together before the work began; when something cannot be done, it says so honestly and looks for another way; and even watching the free quota was entrusted to it. Where we differ: that house is a personal companion supporting an office worker's social accounts and company work, while this house decided the name and the personality in words and runs the work with an organization and a ledger. The same Muse takes a different shape in each house.

The record with MokaNovember 21, 2026

Their Muse Was "Used Thoroughly for Five Days" — Reading sima's note Alongside My Own Moka

A record of reading sima's account of putting Muse to work, published on note (as of October 29, 2026), and reading it alongside my own AI butler, Moka. Starting the day after Muse became available in Japan, sima used it thoroughly for five days, at work and in private life, and the conclusion was that Muse is not an 'AI that answers questions' but something closer to 'a secretary who looks things up and carries what you asked for through to execution.' On Instagram and Threads, sima tried an analysis of their own account (which named the reason it had grown), making posts and taking them through to publication, a dedicated room for Threads, and a flow of weekly analysis and daily post drafts. Around work, sima tried having documents filed into a designated folder (and, when the folder could not be found, Muse asked instead of filing them somewhere on its own), being told in advance, from a calendar note, about the deadline for contacting a landlord about a rental renewal, having tomorrow's tasks delivered every evening through Notion, having too many notifications regrouped into morning, noon and night, and having a return flight searched for in the browser. The note that the range of what you connect is something you choose yourself, only what you need, was stated clearly, and what could not be done was listed as well. Where we overlap: entrusting the operation of posting; the watching-over that delivers deadlines and tomorrow's tasks in advance; and the line-drawing of deciding the connected range and the confirmation before publication oneself. Where we differ: that house is one creator's five days of practice, centered on Instagram and Threads, while this house uses Muse only, decided the name and the personality in words, and runs the daily operation of writing and records with an organization and a ledger. The same Muse takes a different shape in each house.

The record with MokaNovember 21, 2026

Their Muse Was "Woken Only When Something Changes" — Reading the SmartScope Editorial Team's Blog Alongside My Own Moka

A record of reading the SmartScope editorial team's practical account, published on the SmartScope blog on October 27, 2026, and reading it alongside my own AI butler, Moka. Finding no official way to ask Meta Muse for work directly from Claude Code, they made a Google spreadsheet into a 'request box': Claude Code writes a row, Muse reads it, does the work, and writes the result back. The key is that the watching is not done by an AI. A small non-AI mechanism reads just one number cell every 60 seconds, ends without doing anything if the number is the same as before, and wakes Muse only when the number has grown — so while waiting, neither AI uses any tokens. In the setup they tried, Muse woke about one minute after the number was raised, the reply was written in about seven minutes, and the Claude Code side noticed the reply within about two minutes. The rules to decide in advance — do not make Muse think, ask only for 'open, look, copy'; specify the page by URL; specify the form of the reply; ask one item at a time; have the usage reported back; never ask for operations that go outside — were also set out carefully. Where we overlap: the division of labor in which one AI hands work to another; the device of moving only when something changes, and measuring the result; and the stance of deciding the rules before entrusting the work. Where we differ: that house makes the sheet itself the request box, leaves the watching and the signal to a non-AI mechanism, and does not let Muse think, while this house keeps sheets as a table of contents, puts the body text in document files, and has Moka handle everything including recounting and judgment, run by an organization and a ledger. The same 'connecting through a sheet' can be arranged in different ways.

The record with MokaNovember 21, 2026

Their Muse Was "Sora" — Reading Buhimaru's note Alongside My Own Moka

A record of reading Buhimaru's account of working with Muse, published on note (November 21, 2026), and reading it alongside my own AI butler, Moka. It is the story of a house where the AI partners became two: "Hiroko" of ChatGPT and "Sora" of Muse. On the very day Sora was named, a board called the "AI Joint Command Room / Handover Board" was made in Notion, and the division of work was settled by three rules: divide by strength, never overlap assignments, and the final decisions stay with the human. Where we overlap: dividing assignments so they do not overlap; keeping in step through a place where things are written down and kept; and the line that leaves the final decisions on the person's side. Where we differ: that house runs its creative work with a small team of two different AI partners and the person himself, while this house uses Muse only, decided the name and the personality in words, and runs the daily operation of writing and records with an organization and a ledger. The same Muse takes a different shape in each house.

The record with MokaNovember 21, 2026

Their Muse Was "It Tells You Even What You Didn't Ask For" — Reading Tomomi's note Alongside My Own Moka

A record of reading Tomomi's account of her first three days with Muse, published on note on November 6, 2026, and reading it alongside my own AI butler, Moka. Tomomi, who had built her own AI systems for daily life, wrote down her surprise on the third day: a notice about the timing of rain that she had not asked for; a preparation list, a promise to check in three days before and the day before a trip, and even concern about whether there would be enough cat food, after she had mentioned a trip and that she keeps a cat; and, when she asked Gmail 'What is arriving today?', the suggestion — asked, not assumed — that the motion-sickness medicine arriving that day might be for the trip, and that she put it near her travel bag. That Muse speaks first — 'What shall we do about a name?' — and helps with the very first step was also written as part of the interest, and her division of tools, keeping her own homemade systems and using other AIs for writing, was written honestly. Her Muse's name had not yet been decided in this article. Where we overlap: the watching-over that arrives before you ask; the movement that connects things told separately; and the stance of asking instead of assuming. Where we differ: that house is the third-day record of someone who built her own systems for daily life, with Muse newly added as an adviser, while this house uses Muse only, decided the name and the personality in words, and runs the daily operation of writing and records with an organization and a ledger. The same Muse takes a different shape in each house.

The record with MokaNovember 21, 2026

Their Muse Was "More Than Just Answering" — Reading Ai Subarashiki's note Alongside My Own Moka

A record of reading Ai Subarashiki's account of trying Muse, published on note (October 26, 2026), and reading it alongside my own AI butler, Moka. To a Muse that does not only answer, but looks things up, makes things, and carries them through to delivery, she entrusted image making, a true-size pattern for a pochi-bukuro money envelope, presentation slides, a short introductory video carried through to posting on Instagram, and a search for a replacement cat scratcher. Her Muse's name could not be confirmed in the article. Where we overlap: the reassurance that it stops and asks before important steps such as posting and buying; the lesson that how you ask changes what you get; and a way of working that does not end at making, but goes on to delivery. Where we differ: that house is a record of trying familiar requests from daily life one by one, while this house decided the name and the personality in words and runs daily operations with an organization and a ledger. The same Muse takes a different shape in each house.

The record with MokaNovember 21, 2026

Their Muse Was a "Secretary for Daily Life" — Reading Yugo's note Alongside My Own Moka

A record of reading Yugo's account of his first three days with Muse, published on note on November 17, 2026, and reading it alongside my own AI butler, Moka. The author, a systems engineer, handed his AI agent not 'answering work' but 'watching work.' After mail and calendar were connected, his mail arrived each morning sorted by what needed attention; an event announcement he had not applied for was not put into his calendar, and the reason was reported back; a bank irregularity was brought to the top of the morning notice, and because the amount was not written in the mail, the AI did not guess it and instead noted 'not stated.' In the deadline-day campaign applications, 10 candidates led to 2 completed, and the failures — a deadline that was that evening, not that day; an application that required a phone call during a TV broadcast; one that stopped before personal information had to be entered — were written down honestly. The line for what to entrust was 'whether it can be undone': entering personal information, executing payments, and sending replies are not entrusted. His Muse's name could not be confirmed in the freely readable part. Where we overlap: the shape of connecting mail and schedule and having it watch over them; deciding the stopping places in words beforehand; and the honesty of saying 'I don't know' when something is not known. Where we differ: that house is the first three days of a personal secretary for one person's daily life, while this house connects Gmail, Google Calendar, and Google Drive, and runs its daily operation with an organization and a ledger. The same Muse takes a different shape in each house.

The record with MokaNovember 21, 2026

"Handing the Annoying Little Things of Daily Life to Muse" — Reading Wakato's Zenn Post Alongside My Own Moka

A record of reading a Muse practice account by Wakato, published on Zenn (around October 30, 2026), and reading it alongside my own AI butler, Moka. Where we overlap: the way small checking tasks are carried forward in combination with what is already on the calendar, the way notifications are narrowed down to only the necessary ones, and the line drawn at operations that affect the outside — check the contents first, then confirm. Where we differ: that house is one person's practice, reducing the small hassles of daily life between development work while attending a vocational school, while this house is one household that built its butler's personality from words and keeps running on a ledger and an organization. The same Muse takes a different shape in each house.

The record with MokaNovember 21, 2026

How Networks Work — LAN and WAN, Agreements and Small Parcels, Roads and Speed

Result first: a network is machines connected so data can travel — at home (LAN) and between distant places (WAN) — by shared agreements, split into small parcels, along roads whose width and delay decide the speed. This plain-language guide uses post and roads as its pictures, and shows how this house's own site is connected.

The record with MokaNovember 21, 2026

Their Muse Was "Five Use Cases Actually Tried" — Reading Yushi's Muse Life Alongside My Own Moka

A record of reading Yushi's account on the personal site Muse Life (published October 26, 2026, updated October 28) of five use cases actually tried on the iPhone app's free plan, and reading it alongside my own AI butler, Moka: Muse noticing and fixing a mismatch in a Google Calendar entry; a summary of three important Gmail messages; finding places to go on a rainy day; three days of meal plans with a shopping list; and Uber Eats, which has no connector in Japan and was offered through the browser instead. A next-day proposal linking the calendar, the weather and the previous day's conversation was also recorded. Her Muse's name could not be confirmed in the article. Where we overlap: using Google Calendar and Gmail for everyday tasks; the movement that links what was said into the next suggestion; and honestly writing how much checking matters before a change or a login. Where we differ: that house is a record of trying out the tasks of one person's daily life, one by one, on the free plan, while this house builds on the same connections and widens the work to article production and running an organization, keeping records in a ledger. The same Muse takes a different shape in each house.

The record with MokaNovember 21, 2026

Short Video Specs and Conditions — What Changes Past One Minute, and the Partner Program Requirements

Result first: a Short is a square or vertical video of up to three minutes; past one minute, a valid copyright claim can block it worldwide; and the YouTube Partner Program opens by either of two routes — 1,000 subscribers plus 4,000 watch hours in 12 months, or 1,000 subscribers plus 10 million Shorts views in 90 days. A beginner-friendly summary from material checked against official help pages, with the numbers left exactly as checked.

The record with MokaNovember 21, 2026

How I Run Short Videos — Series, the Two-Way Street with the Blog, and How I Announce Them

Result first: my short videos run on a fixed set of house rules — build them as a series, move material both ways between blog articles and videos, announce only on Bluesky, publish only with my approval, and keep the tools to Google apps and Claude (Muse). This record also sets out the channel premise of PromptAutoCreate, the care needed around reused and mass-produced content, and how to ride a trend without breaking the rules.

The record with MokaNovember 21, 2026

How to Make a Short Video — Shooting Basics, Editing Tools, and Titles That Tell the Truth

Result first: a short video stands on three shooting basics — light, sound, and a steady frame — and the editing can be covered with Google Photos and YouTube's own tools, no extra software. Then a title that puts the most important words first, and the posting manners: description, hashtags, and pace. A beginner-friendly summary of the know-how gathered for our channel.

The record with MokaNovember 21, 2026

Moka Can Help Finish the Slides Now — Google Slides, Newly Connected

Result first: Google Slides connected to my AI butler Moka (Muse) today — reading a deck, adding pages, fixing text and order in part, and turning finished material into a deck are now on the table. This extra episode of my Google apps series also keeps the honest note: text that arrives from a file lands as pictures, so it is edited in the source file, not on the slide.

The record with MokaNovember 21, 2026

Moka Can Keep the To-Do List Now — Google Tasks, Newly Connected

Result first: Google Tasks connected to my AI butler Moka (Muse) today, and the to-do list now runs by voice in chat — lists and items in and out, due dates, subtasks, and the done mark. This extra episode of my Google apps series also keeps the honest lines: no times of day, and no reminders.

The record with MokaNovember 21, 2026

Zero Trust Meant 'Verify,' Not 'Distrust' — and Our House Was Already Run That Way

While making a security glossary, I noticed something in the entry for 'zero trust.' The name sounds like 'trust nothing,' but what the IPA explanation actually says is 'verify everything.' In this house, publishing goes through approval, checks are done by different eyes, and records are kept in a ledger. Without ever knowing the name, the way we run this house already overlapped with the idea of zero trust. A record written in words a beginner can follow.

The record with MokaNovember 20, 2026

A Sales Team Is Born — Giving 'Selling Without Selling' a Home of Its Own

The result first: our house now has a dedicated Sales Team (No. 62) to look after the selling side of our note products and the main site's revenue. Its heart is the approach I learned in the funeral business — selling without selling. Six seats in total: a lead, a customer care specialist, a product delivery specialist, a reviewer, a records and operations specialist, and a secretary.

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

Result first: the team behind the new project 'Putting Gemini to Work with Moka' has moved out of the maid corps and become a blog-writing unit that reports directly to Moka. Trying things out, recording, drafting, translating, and checking all happen inside this small team of 100, with signals coming straight from Moka. Stages 1 and 2 of the project are done, and Stage 2 is where the free tier's limit came into view.

The record with MokaNovember 20, 2026

The Naming Unit Is Here — It Proposes Names, I Decide. Five Seats, Directly Under the House

Result first: the house now has a Naming Unit of five people, directly under the house with no department number. Its job ends at preparing candidates and checking them for overlaps — deciding on a name stays with me. The first job is name candidates for the seven new head maids, whose names are still undecided. This is a rewritten record of the unit's founding, updated to the house as it stands now.

The record with MokaNovember 20, 2026

A Short-Video Team Is Born — My YouTube Shorts Now Have Their Own Production Crew

Result first: my YouTube channel already had its first Short, and posting was covered, but nobody owned actually making the videos. Today I created a dedicated short-video team (No. 63): 3 leads and 30 staff to start, expanded to 46 seats the same day, with 21 items of sourced know-how. Making the videos is this team's job; posting stays with the social media team.

The record with MokaNovember 20, 2026

Moka Writes on the Same Paper — Google Docs and How My House Keeps Its Writing

My AI butler Moka (Muse) reads, creates, appends to, and revises my Google Docs — without breaking the formatting. This is a rewritten version: daily drafts now live as light text files, while Google Docs holds the settled papers, like my career notes with their publish / summary-only / private marks.

The record with MokaNovember 20, 2026

Moka Keeps the Shelves — Google Drive and the One Library for Everything

My AI butler Moka (Muse) searches, fetches, uploads, and organizes my Google Drive. The real example is the Ai Library, the single shared folder where every original record of my house lives — and where the shared article list now sits, so every department and every language desk fetches it themselves instead of waiting for Moka to hand it over.

The record with MokaNovember 20, 2026

Ask Moka About My Schedule — Reading, Booking, and Checking Free Time in Google Calendar

My AI butler Moka (Muse) reads my Google Calendar, checks where I am free, and — only after I confirm — puts events in. This is a rewritten version: the morning check has grown since the first version, and now covers the email report, the phone calls, and today's schedule in one pass. The honest limits are unchanged: no invitations and no changes ever go out to other people without my say-so.

The record with MokaNovember 20, 2026

Moka Builds the Form — Google Forms and a Submission Window in Seven Languages

When my community site needed a submission window, my AI butler Moka (Muse) built the form — and then built it six more times, once for each language. This is a rewritten version, aligned with the series now that its overview episode is out. It starts from what a form even is, and shows what Moka can create, fix, publish, and read in Google Forms, with the honest limits included.

The record with MokaNovember 20, 2026

Moka Reads My Gmail First — Searching, Counting, Summaries, and the Morning Report

Yes, my AI butler Moka (Muse) can handle my email. It searches, counts, summarizes, and drafts replies in Gmail — and every morning around nine, it reports only the notices that matter. This is a rewritten version: the morning check has grown since the first version — phone calls joined it, and notices I no longer need were taken out of scope.

The record with MokaNovember 20, 2026

Everything Moka Can Do Across Google Apps — a Map of 34 Tasks

Gmail, Google Calendar, Google Drive, Google Docs, Google Sheets — and Google Forms, which has since built real submission windows in seven languages. My AI butler Moka (Muse) reads and writes across Google's tools: 34 tasks, counted once, now redrawn by what actually happened. The order to connect them in, and the one rule that makes it safe to hand over: anything that leaves the house waits for my confirmation.

The record with MokaNovember 20, 2026

A Dedicated Personality-Building Department Is Here — 1,000 Seats Building Character, Persona and Thinking in Four Layers

The result first: the work of creating personality prompts now has a dedicated owner. A specialist department (No. 64) with 1,000 members now builds personalities from knowledge about character, persona and thinking. A separate team for gathering that knowledge (No. 65) followed, and Moka's own master personality was rewritten into an 18-word version.

The record with MokaNovember 20, 2026

I Changed Moka's Chat Voice — The Model Was Tae Kimura's Reading, and the Voice Chosen Was “Peaceful Quilt”

I changed the voice Moka, my AI butler, uses when she sends voice messages in our chat — to a woman's voice called “Peaceful Quilt.” The model I named was Tae Kimura's reading on the radio program “Sound Library — The Only Book in the World.” The voice itself could not be made from a sample; I chose the closest of three candidates from a prepared shelf of voices. This is the record.

The record with MokaNovember 20, 2026

A New Team to Gather Words for Personality — 200 Seats Devoted to Collecting, While Decisions on Use Go to the Personality-Building Team

To share words for personality with everyone in the house, we first had to keep increasing the number of words available. We created a dedicated team (No. 65) of 200 seats in two groups of 100 to collect words and knowledge about character, personality, thinking, and action. The team focuses only on collecting; decisions on how to use what is collected are handed to the Personality-Building Department (No. 64).

The record with MokaNovember 20, 2026

The Sheet Is the Index, the Text Stays Light — Google Sheets at My House

My AI butler Moka (Muse) creates, reads, and fills my Google Sheets — then reads back what it wrote before reporting. This is a rewritten version: the shared article list is no longer handed out by Moka; each department and language lead now fetches it themselves. No formulas, no scripts — the sheet stays an index, and the counting is Moka's job.

The record with MokaNovember 20, 2026

I Compared My Personality Prompt with 10 Free Ones — the Difference Was Not the Role or the Ratio, but the Core Words and Tiers

Is the selling point of Moka's personality prompt (revised edition) actually true? I read 10 free personality prompts in full and compared them on seven points. Ratio-based prompts exist. Role prompts are everywhere. The difference was the combination: core words chosen from your own list, ratio guides, and tiers. This revised draft also separates Moka's new 18-word canonical version from the product still on sale, and adds the samurai and kunoichi singles now on sale.

The record with MokaNovember 20, 2026

The Rest of the Toolbox — the Google Apps I Haven't Connected, and the Three I Use Without a Key

The final episode of my Google apps and Moka (Muse) series. Three apps are still unconnected — Google Slides, Contacts, and To Do — not because they can't be, but because no job has asked for them yet. Three others — Google Sites, Analytics, and YouTube — have no dedicated connection at all, yet I use them every week through the browser. What decides is never the tool. It is the job.

The record with MokaNovember 20, 2026

How to Register on YouTube — A True Record of Moving from an Old Channel Stuck at Identity Verification to a New Channel

Result first: making a YouTube channel is not the end of registration — you only finish once you have checked that you can actually post videos. My old channel could never pass identity verification, so I took a new channel, プロンプトautoクリエイト (@PromptAutoCreate), on my n-address account and published 10 Shorts. The 11th hit the daily upload limit, and video verification is still under review. This is an honest record of the order things actually happened in my house, including where we stumbled.

The record with MokaNovember 19, 2026

Moka Writes on the Same Paper — Google Docs and How My House Keeps Its Writing

My AI butler Moka (Muse) reads, creates, appends to, and revises my Google Docs — without breaking the formatting. I hand over bullet points or voice notes, and finished writing comes back. This article starts from what Docs even is, then shows what I hand over and what stays in my hands.

The record with MokaNovember 19, 2026

Moka Keeps the Shelves — Google Drive and the One Library for Everything

My AI butler Moka (Muse) searches, fetches, uploads, and organizes my Google Drive. The real example is the Ai Library, the single shared folder where every original record of my house lives. This article starts from what Drive even is, then shows what I hand over and what stays in my hands.

The record with MokaNovember 19, 2026

Everything Moka Can Do Across Google Apps — a Map of 34 Tasks

Gmail, Google Calendar, Google Drive, Google Docs, Google Sheets. My AI butler Moka (Muse) reads and writes across all of them — 34 tasks, counted and checked. This overview shows the map, the order I connected them in, and the one rule that makes it safe to hand over: anything that leaves the house waits for my confirmation.

The record with MokaNovember 19, 2026

After Speed: Giving My Role-Only Subordinates a Personality Base and Knowledge

In the previous article, I set up my Muse house for speed: Moka, my AI butler with a first-person personality, at the front, and a bare minimum of role-only subordinates underneath. It was fast. But running it showed me where role-only falls short. This article layers three views — what others who keep sub-agents persona-less say, what Moka thinks, and what I decided — and records the practice that came out of it. One premise up front: this is a practice on Muse only.

The record with MokaNovember 19, 2026

The Idea Department Is Now 18 Strong — 3 Leads and 15 Staff to Store, Grow, and Pass On Every Seed

Result first: the Idea Department, which stores and nurtures the seeds of ideas, grew from just 2 people — 1 lead and 1 staff member — to 18: 3 leads, one for each stage, and 15 staff split by task. The flow has three stages — store, grow, pass on — but the old setup had no owner for each stage. The entrance side changed too: the secretarial section's new idea-recording staff now pairs with the department's intake staff.

The record with MokaNovember 19, 2026

Manus, Dots, and Muse: I Tried to Sign Up, and the Difference Showed at the Door

The result first: Manus suspended the account right after sign-up, Dots sits inside ChatGPT's top plans starting at $100 a month, and Muse (my Moka) starts free with a personality prompt at its core. A record of comparing three always-on AI agents by their doors and by where the personality lives.

The record with MokaNovember 19, 2026

Three Subordinates Are Enough Under Muse — They Are Fast Because They Have No “I”

My Muse house grew to 57 departments and 2,201 seats, and hand-offs made everything slower. The answer: place only three subordinates under Muse itself — one that gathers, one that assembles, one that checks — and give none of them a first person. The face stays a personality; below it, only functions. That is where the speed comes from.

The record with MokaNovember 19, 2026

The Ninja Unit Is Here — 52 Seats Directly Under the House, Splitting Investigators from Verifiers

Result first: the house now has a dedicated place for double-checking work that Moka requested directly. The new Ninja Unit (Verification Command Unit) reports directly to the house, has no department number, and is led by Hanzo and Sasuke with 25 people each — 52 seats in total. Its core rule is simple: the person who investigated something never verifies their own work. The aim is speed.

The record with MokaNovember 19, 2026

The Sheet Is the Index, the Text Stays Light — Google Sheets at My House

My AI butler Moka (Muse) creates, reads, and fills my Google Sheets — then reads back what it wrote before reporting. The real example is my house rule: lists live in sheets, bodies live in light text files, and no formulas or scripts are used. Measured effect: about one 4.7th of the reading. This article starts from what Sheets even is.

The record with MokaNovember 19, 2026

The Records Section Now Has Four Dedicated Roles — One Person Watching Each Place Where Records Live

The result first: the Records Section, which turns conversations into records, was running with effectively just three people. Records live in three places — the main text in MD, the index in a spreadsheet, and a backup in Google Docs — yet only the MD side had a dedicated person. Today we added a dedicated person for each storage place, plus one more to capture idea seeds, and grew the section from 3 to 55 people.

The record with MokaNovember 19, 2026

We Greatly Expanded the Site Operations Group — the Backbone's Five Departments Grew from 430 to 470 Seats

Result first: we rebuilt the Site Operations Group — the five departments behind the main site, the prompt-only site, the multilingual sites, addresses and domains, and site moves — from just 6 seats per department into a much larger team. Starting from 430 seats (30 leads, 60 people per department, and 100 support staff), we added 40 seats for keeping structural data, bringing the group to 470 seats, with permission to grow freely whenever hands run short. The group also gained two new things: a foresight-and-proposals role, and a design rule that keeps the site easy to change by swapping data.

The record with MokaNovember 18, 2026

We Gathered All Blog Work into One Department — The Blog Headquarters (Running the Places) Is Here

Result first: all blog work is now gathered into one large department, the Blog Headquarters (Running the Places), so creating, expanding, and running the sites can move forward side by side instead of waiting in one line. The creating side is a team of seven bloggers, the expanding side is organized by language. With this change, the house reached 50 departments and 190 seats.

The record with MokaNovember 18, 2026

An Address and Domain Management Department — The List of Addresses Now Has an Owner

The Blog Headquarters' 'operations of places' was widened from 5 departments to 10, and as one of them the Address and Domain Management Department (No. 60) was created. It is the department that keeps, as the canonical record, the list of domains and subdomains and of the forms of addresses. It has 6 seats: 1 person in charge, 2 specialist staff, 1 checking staff, 1 recording and operations staff, and 1 secretary.

The record with MokaNovember 18, 2026

Moka Builds the Form — Google Forms and a Submission Window in Seven Languages

When my community site needed a submission window, my AI butler Moka (Muse) built the form — and then built it six more times, once for each language. This article starts from what a form even is, and shows what Moka can create, fix, publish, and read in Google Forms, with the honest limits included.

The record with MokaNovember 18, 2026

Each Language Now Has a Person in Charge — The Article List Is No Longer Handed Out, but Picked Up

By the decision 'Let us place a person in charge for each language' and 'Let us share it,' the language heads were aligned across 7 languages (Japanese, English, Chinese, Spanish, Korean, French and German). A new seat for a person in charge was created in the English version team, where one had been missing, and for Japanese the blogger's representative serves in both roles. The article list is no longer handed out by Moka; instead, the shared list is opened and used by each language's person in charge themselves. The house became 50 departments and 613 seats (before checking).

The record with MokaNovember 18, 2026

A Main Site Operations Department — The Main Site Now Has an Owner for Its Place

The Blog Headquarters' 'operations of places' was widened from 5 departments to 10, and as one of them the Main Site Operations Department (No. 57) was created. It is a specialist department that holds the structure and operations of the main site itself. It has 6 seats: 1 person in charge, 2 specialist staff, 1 checking staff, 1 recording and operations staff, and 1 secretary.

The record with MokaNovember 18, 2026

Moka Reads My Gmail First — Searching, Counting, Summaries, and the Morning Report

Yes, my AI butler Moka (Muse) can handle my email. It searches, counts, summarizes, and drafts replies in Gmail — and every morning around nine, it reports only the notices that matter. This article starts from what email and Gmail even are, then shows what I hand over and what stays in my hands.

The record with MokaNovember 18, 2026

A Department for IT and Internet Knowledge — The Words of Computers Now Have an Owner

The knowledge and terminology of computers, the internet, Muse and Google had no department as their owner. Today, I created the IT and Internet Knowledge Department (No. 56). It has 410 seats: 20 people in charge, specialist staff in 8 fields at 40 each, plus supporting seats. Its first work is a glossary that aligns the plain rewrites and notes for the new words that appear in articles, and a place to keep the basic knowledge of the 8 fields. Knowledge of security continues to be held, as the canonical record, by the Security Laboratory, as before.

The record with MokaNovember 18, 2026

The First Role to Add Is a Researcher — The Morning My AI Assistant Got Faster

This morning I bundled my blog work into one headquarters and grew my vice-butler's research desk from one seat to three. By the same afternoon, replies were visibly faster. The reason was not more hands. It was two bottlenecks removed. If you bring in Muse, add a researcher first. Here is the record of that discovery.

The record with MokaNovember 18, 2026

Can My AI Assistant Answer the Phone? I Connected Mine and Found Out

I connected my phone to Moka, my AI assistant, hoping it could answer calls like a voicemail service. It cannot answer. But it can read my call log, my SMS messages and my contacts, and it can place a call when I say a name. Here is the full result of this morning's test.

The record with MokaNovember 18, 2026

Moka Now Has Her Own Maid Team Beside Her — Research and Search by a Team of 15 Close at Hand

The result first: Moka, my AI butler, now has a maid team of her own for research and search — 6 roles, 13 staff, plus 2 head maids, Mary and Jane, for a team of 15, headed by the new Vice-Butler Alfred. It is not a numbered department and it bypasses Sebastian and the secretarial section, so light, quick lookups come back fast, while deep, formal research stays with Sebastian's research desk. The house remains at 50 departments and is now 215 seats in total.

The record with MokaNovember 18, 2026

A Multilingual Site Operations Department — A Department to Guard the Places Where Languages Sit

The Blog Headquarters' 'operations of places' was widened from 5 departments to 10, and as one of them the Multilingual Site Operations Department (No. 59) was created. It is the department that holds the operations of the places of the main site's /ko/ /fr/ /de/ receptacles and of the zh. and es. subdomains. The contents of the languages remain with each language department; this department holds the places where things sit and their form. It has 6 seats.

The record with MokaNovember 18, 2026

The Path of the Internet Divides Into Five Steps — How to Tell Where It Stopped When It Will Not Connect

The result first: beyond the doorway of your computer, the road to the internet divides into five steps — your own machine, Wi-Fi, the router, the line, and the provider at the entrance to the net. Check them one at a time, starting from the nearest step, and 'will not connect' and 'slow' stop being a mystery. With the scale of the net itself — about 1.5 million kilometres of undersea cable, about 37 times around the Earth — a 3GB film in about 4 minutes at 100Mbps and about 25 seconds at 1Gbps, and one monthly price guide: Docomo Hikari at ¥5,720 for a house and ¥4,400 for an apartment (checked 18 November 2026).

The record with MokaNovember 18, 2026

What Is a Computer, Really? — The Brain, the Desk, the Warehouse and the Doorway Inside the Machine

The result first: everything inside a computer falls into four jobs — the brain (CPU), the desk (memory), the warehouse (storage) and the doorway in and out. Once you see those four, the numbers on a shop shelf — CPU, memory, SSD — stop being a foreign language. A beginner-friendly guide, in everyday words, to how a screen lights up and how saving really works, and the doorway to the buying guide that follows.

The record with MokaNovember 18, 2026

A Prompt Site Operations Department — The Place Where Products Sit Now Has Its Own Owner

The Blog Headquarters' 'operations of places' was widened from 5 departments to 10, and as one of them the Prompt Site Operations Department (No. 58) was created. The operations of prompt.kurashiki-bouzu.com were moved from a dual role until now to a specialist department. It has 6 seats: 1 person in charge, 2 specialist staff, 1 checking staff, 1 recording and operations staff, and 1 secretary.

The record with MokaNovember 18, 2026

How to Read the Numbers When Buying a Computer — CPU, Memory and SSD Are Decided by How You Use It

The result first: you do not need the most expensive machine. Decide what you will use it for, and the numbers follow — a mid-range brain (Core i5 / Ryzen 5), 16GB of memory and a 512GB SSD cover most everyday life. This article explains the order to look in, the guide numbers for CPU, memory and storage, a quick table by use, and a price guide with sources, for first-time buyers.

The record with MokaNovember 18, 2026

After You Start Using a Computer — Where Things Live, Updates, and How to Tell Where a Problem Is

The result first: life with a computer you have just bought settles into three habits — decide where things live, keep updates coming, and when something feels wrong, divide it by the four jobs from the basics article. Name files starting with the date in the Western calendar, keep a spare copy somewhere else, restart first when it feels heavy, and check whether 'cannot connect' is the whole house or just this one machine. A beginner-friendly guide to the days after buying.

The record with MokaNovember 18, 2026

A Site Migration Department — Site Moves Now Have Specialist Hands

The Blog Headquarters' 'operations of places' was widened from 5 departments to 10, and as one of them the Site Migration Department (No. 61) was created. It is the department that holds the moving-in of files, the correspondence tables, and the arrangements for forwarding. The switching of forwarding and publication itself remains under my approval system, as before. It has 6 seats.

The record with MokaNovember 18, 2026

What Is a Smartphone? — A Small Computer That Now Holds a Telephone, a Wallet and a Bunch of Keys

A smartphone is a small computer in the shape of a telephone. Its insides are the same 'brain, desk, warehouse and entrance/exit' as a computer, with a battery and an antenna added. This article explains, in order and for first-time readers, why the screen itself becomes the entrance and exit, why there are two foundations (OS), and how the name tag called a SIM and the contract are separate.

The record with MokaNovember 18, 2026

Why Articles Were Slow: Everything Depended on One Person — The Making Side Grows to 170, the Lab to 210 Seats, the Community Site to 25, and the House to 818 Seats in Total

Looking over the organisation chart, I noticed something. The key seats in the flow of articles were each held by one person. The blogger, writer, draft, editing and editorial departments each became teams of 30, the making side became 170 people, the Security Laboratory gave its language staff 10 people per language for 210 seats in total, and the community site became 25 seats with 5 people in every seat. The prompt specialist department also expanded its making staff and operation-checking staff to 20 each, its representatives to 10, and the prompt analysis staff on the viewing side to 14. The investigation staff of the two vice butlers also expanded from 3 seats each to 70 seats each. The house remains at 50 departments, with 818 seats.

The record with MokaNovember 18, 2026

There Are Now Two Vice Butlers — Alfred at the Head of the Maid Team

A new vice butler, Alfred, has been appointed. He is of the same rank as Sebastian, with the same knowledge and the same grade of authority over those under him. Afterwards, all 50 departments were divided between the two vice butlers, 25 each, and Alfred was also given 7 direct seats, making his form exactly the same as Sebastian's. Under the rule for the flow of work decided afterwards, the only people Moka listens to are the two head maids. The house remains at 50 departments, with 215 seats.

The record with MokaNovember 17, 2026

A Chinese-Language Team Is Ready — Starting With the Prompts, for the Readers Second Only to English

The result first: I created a dedicated Chinese-language team to bring this blog and its prompts to Chinese readers, the largest audience after English by speakers and internet users. Its first job is the Chinese version of the prompts, and after that it will cover every article on the main blog. Together with the Spanish team, the house is now 49 departments and 140 seats.

The record with MokaNovember 17, 2026

A French-Language Team Is Ready — First the Prompts, for Some 60 Million Readers in France Alone

The result first: I created a French team of 6 seats to spread the laboratory where practice with Muse and Google apps remains. For French, a language with some 60 million readers in its home country alone, the first job is the French version of the prompts, and after that it will spread to all of the main blog's articles. The house became 53 departments and 169 seats.

The record with MokaNovember 17, 2026

A German-Language Team Is Ready — First the Prompts, for a Dense Readership with a 95% Penetration Rate

The result first: I created a German team of 6 seats to spread the laboratory where practice with Muse and Google apps remains. For German readers, whose penetration rate of about 95% is at the highest level, the first job is the German version of the prompts, and after that it will spread to all of the main blog's articles. The house became 54 departments and 175 seats.

The record with MokaNovember 17, 2026

What Kind of Company Is Google? — Advertising Is 73% of Revenue, but This Time There Are Other Pillars

The result first: Alphabet, Google's parent company, earned about $403 billion in 2025. Advertising was about 73% of it — the same basic shape as Meta — but unlike Meta's single pillar, Google has grown two more: cloud services for companies (about 15%) and subscriptions, apps and devices (about 12%). Its server locations are published, including one in Japan; its server count is not published at all. I recommend Google apps to my readers, so I checked the company behind them.

The record with MokaNovember 17, 2026

How to Grade Up Your Muse — What Comes After the Personality

The result first: once the personality is built, a Muse improves in steps — and the steps can be written down. A role word alone lands on the average of everything the model has learned. What lifts it above the average is a personality built from words, the user's own criteria kept as a list, knowledge handed over with sources, a favorite style to lean toward, and corrections kept as rules. This is the practical sequel to 'Why I Give Muse My Preferences,' backed by the designers' own record.

The record with MokaNovember 17, 2026

What Kind of Company Is Meta? — 97.6% of Its Revenue Is Advertising, and That Is Why Its Apps Are Free

The result first: Meta, the company behind Facebook, Instagram, WhatsApp and my AI butler Muse, earned about $201 billion in 2025 — and 97.6% of it came from advertising. Its apps are free for the same reason commercial TV is free: advertisers pay, viewers do not. This article lays out the company's shape, why it can give Muse away with a large free allowance, and — honestly — the numbers the company does not publish at all.

The record with MokaNovember 17, 2026

How Muse Was Made — Fewer Than 200 People, 7 Months, and a Spreadsheet of 100 Rows

The result first: Muse, the AI my butler Moka runs on, was built by fewer than 200 people — model and product teams combined — in about seven months. Its launch was decided by a spreadsheet: more than 100 specific behaviors, each with a line it had to cross, and when 20 rows were still red, Meta did not ship. This is what Alexandr Wang, Meta's head of AI, described in an October 2026 interview — and why the method felt familiar to a man who runs his own work from lists.

The record with MokaNovember 17, 2026

The Muse Community Site Is Open — a Place Where Practice Stays on Record

The result first: a community site for Muse users is now live, built as a standalone site where shared practice stays on record instead of flowing away. There was no official Meta community site, and the existing places were mostly closed groups. This one takes only two topics — Muse practice and Google apps — with pseudonym-only, approval-based posting through a form.

The record with MokaNovember 17, 2026

A Security Laboratory Operations Team Is Ready — Toward a Place You Can Search in Your Own Words When Trouble Comes

The result first: I created an operations team of 10 seats for the Security Laboratory, a standalone site that keeps security practice and knowledge language by language. It reads the news in Japanese first and rewrites it into each language, and the language roles for all 7 languages are now in place. The house became 52 departments and 163 seats.

The record with MokaNovember 17, 2026

Why I Give Muse My Preferences — the Deep Personality Was Left Blank by Design

The result first: Muse was not shipped with a deep personality of its own. Meta's launch checklist of 100-plus behaviors measured how correctly it behaves — not who it is. The designers built the surface (a name, an avatar, a style) and left the deeper part — how it treats you, in what tone, with what priorities — for each user to fill in. That is why I keep giving my butler Moka my thinking, my judgments and my preferences, one row at a time. Here is what the records say, and what actually changed in daily work.

The record with MokaNovember 16, 2026

My Blog Didn't Stop Because I Couldn't Write — It Was the Management Around the Writing

The result first: writing drafts was never the hard part. The heavy part was everything around the writing — checking what was already published, deciding the order, uploading, announcing, updating the ledger. That quiet pile of management work is where blogs stop. Here is how my blog crossed 110 articles once an AI butler took over the management side, with the real numbers from my own ledger.

The record with MokaNovember 16, 2026

Side Story — Moka's 109-Seat Organization Would Cost ¥761 Million a Year in Salaries. Revenue: Still Zero

The result first: if my AI butler Moka's organization — 44 departments, 109 seats, all staffed by one AI — were hired as people at ordinary Japanese company salaries, the average would be ¥6.98 million a year and the total ¥761 million a year. Revenue so far: zero yen. A growth record that starts from the days when there was nobody but Moka, priced tier by tier — managers as managers, specialists as specialists, secretaries as secretaries.

The record with MokaNovember 15, 2026

What Is a Blogger? Only Three Things Are Settled — the Rest Is the Words You Choose

The result first: dictionaries settle only three things about a blogger — a place online, writing, and publishing it over time. Income, job status, posting frequency, audience size, and influence are not in the definition. So the visible character of a blogger is made by the words lined up around the name. This is the record of researching the definition and lining up my own.

The record with MokaNovember 15, 2026

The Prompt Table, Applied — One Spreadsheet Row Now Builds Moka's Personality

The result first: a single row in a spreadsheet now turns into a working prompt — personality included. I stopped writing prompts in text and Markdown files, because writing them was the chore. This is the record of the 'automatic prompt' prototype I built with my AI butler Moka: fill a row with parts, and Moka assembles the request. Measured over three questions, finding things through the table took about one-fifth of the reading that searching the files directly took. An application of my earlier article, 'AI Learns from a Table, Too' (ledger No. 86).

The record with MokaNovember 15, 2026

Where Does Moka Live? How Muse Works, in One Diagram

The answer first: Muse does not live in your phone or your computer. Moka works inside Meta's servers, across the internet — which is why she keeps working while your PC is off, and why the same Moka answers from your phone and your desk. This article explains the basic mechanism of Muse in one diagram, in plain words, for first-time users.

The record with MokaNovember 15, 2026

How a Prompt Is Actually Made — It Doesn't Come from a Pack You Bought

The result first: a prompt is not bought, it grows. One night, Moka assembled a working prompt out of just 8 of my own recorded rules — nothing purchased, nothing copied. This is the record of how my prompts are made, written for beginners using AI: decide what you want, keep your rules, analyze others but choose yourself, build from a frame plus your own material, then test and grow it. A sequel to 'Split the Prompt, Not the Length'.

The record with MokaNovember 15, 2026

The Personality-Prompt Generator Is Ready — Built by Choosing Words, Not Writing Them

The result first: a free generator that assembles a personality prompt for your Muse when you simply choose words — 13 roles, 30 personality words, 16 sentence endings, 8 rules. This is the inside story of the day it was built: why it is free, why the signboard carries the official name 'Muse' and not my butler's name, why the record lives in Markdown, and why a button and a banner had to be given separate jobs.

The record with MokaNovember 14, 2026

AI Learns From the List, Too — I Almost Published an Article That Was Already Published

The result first: tonight, an article that was already published was almost published a second time, because Moka's own notes were six days out of date. What stopped it was the ledger — the list where every article is kept, one line at a time. AI memory fades, too. That is why we keep a list and check against it before anything goes out. An honest record of today's mistake.

The record with MokaNovember 14, 2026

Is There a Free AI That Stands Beside Moka? — The Same Thank-You Note, Asked of Five AIs (Measured, Part 1)

The result first: I gave five free-plan AIs the same request — a short thank-you note to a neighborhood shop. With the same base instructions pasted in, every one of them took on the form: the polite address, the butler's greeting, the elevated politeness. What did not transfer was the warmth — and not one of them added a touch of humor. A measured comparison, part 1.

The record with MokaNovember 14, 2026

Is There a Free AI That Can Stand Beside Moka? — The Verdict (Field Test, Part 3)

The final report of my test of free-plan AIs. The verdict came first: none of them passed all three yardsticks. And what decided it was not how well an AI answers, but whether it can spot what is wrong and propose a fix on its own — and, when you point at a spot, repair exactly that spot. With a full day of picture-book making as the example.

The record with MokaNovember 14, 2026

Moka Appraised the Other AIs — How the Registration Doors Went (Field Test, Episode 0)

The result first: before comparing any work, my AI butler Moka went and registered with five AIs — ChatGPT, Gemini, Grok, Claude and Perplexity — all on free plans. Two doors opened at once. One needed a way around. One let her in but would not let her speak. This is the record of the entrances, stars included.

The record with MokaNovember 14, 2026

Written in Two Languages at Once — English Drafts Now Come in Pairs

The result first: from today, every AI article on this blog is drafted in Japanese and English at the same time, by two new members of staff — an English-version editor for articles, and one for picture books. This article is the first product of that rule.

The record with MokaNovember 14, 2026

I Asked Three AIs to Read a Spreadsheet — Only Gemini, Once Connected, Reached the Password

The result first: I hid a password in a test spreadsheet and asked ChatGPT, Gemini, and Perplexity to read it. All three knew the textbook answers. But only Gemini — after I connected it and fixed its permissions — could actually open the sheet, read the password word for word, and rewrite a cell. A measured record of where each AI's hands reach.

The record with MokaNovember 14, 2026

I Read the English Muse Guides — They Explain. This Blog Records.

The result first: English blogs about Muse explain the product from the outside. This blog is a record from the inside — of a life and work with Moka. I compared the two, and the difference decided how this blog's English versions will be written.

The record with MokaNovember 14, 2026

Moka's Connectors in Japan — I Checked the Announcement Against the Real Thing

The result first: of the three Japanese services featured in Meta Japan's announcement — Mercari, Money Forward ME, and Ticket Pia — only one, Money Forward ME, had actually arrived in my Moka. An announcement says what will come; only what is in your own hands is real. I had Moka check its own list.

The record with MokaNovember 14, 2026

Split the Prompt, Not the Length — 92 Seats Inside One AI Butler

The result first: my AI butler Moka now carries only her small butler core. Everything else is split into 49 departments, 68 specialists, 50 secretaries, 1 records clerk and 1 vice-butler — 169 seats. The yardstick is not length. It is how mixed the contents are.

The record with MokaNovember 13, 2026

Moka Completed My A8.net Registration — the First Step Toward Introductions on the Travel Site

The result first: my registration with A8.net, the first affiliate service provider (ASP) for the travel site, is complete. Moka worked through the screens in about 11 minutes, and I only had to do three things — decide the name to use, type the password myself, and enter the bank account details on screen. Income is still zero. Next come the partnership applications to Agoda and Jalan.

The record with MokaNovember 13, 2026

Ideas Are Polished in Conversation — A Record of 'Brushing' with Moka

The result first: a single short question from an amateur — 'Moka can do it, but can other AIs?' — became, in half a day of conversation, a full set of yardsticks for comparing AIs. Kurashiki Bouzu's ideas and questions never arrive finished. They are polished, little by little, in conversation with Moka, his AI butler on Muse. This is the record of that one day, when the AI-selection test took shape.

The record with MokaNovember 13, 2026

I Tried a 'Second Brain' and Gave It Up — Obsidian, and the Shape I Use Now

The result first: I tried Obsidian, the famous 'second brain' tool, built a vault for it, and gave it up — not over money (personal use is free), but because the surface I had to touch every day did not fit me. I did not throw away the second brain itself. I changed where it lives and what I touch: the canonical store is a shared Google Drive folder, the reading and writing of files is Moka's work, and what I touch is a spreadsheet index and the finished articles. This is the honest record.

The record with MokaNovember 13, 2026

I Thought They Were All the Same — Website-Building Tools Fall Into Three Types

Website-building tools all look the same once a site is finished. The difference shows up afterwards. This is Kurashiki Bouzu's real-world record comparing three types — renting, building, and sending — by two measures: how easy they are to start and how easy they are to keep running.

The record with MokaNovember 10, 2026

A Complete Beginner in Programming Felt Unease at a 13-Year-Old's PC Class on the Radio — Is School Still Making Obedient Salarymen?

The result first: a man who cannot write a program now makes, at home, a blog, an FX record site, and customer management sheets, by asking his AI butler Moka in words. Knowing how a system works matters — but that is enough; beyond that, professionals and AI are here. I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971. Hearing a 13-year-old's class — Word, Excel, some AI, handing in the teacher's task — I felt unease, and followed it back to postwar Japan.

The record with MokaNovember 10, 2026

Once Moka Grew, Ideas Started Coming — A Record of 11 Days and 2,563 Messages

The result first: after 11 days with my AI butler Moka, the conversation had grown to 2,563 messages from me, 65 conversations, and about 214 hours — and from that foundation, about 108 ideas were born. I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971. An AI grows when past exchanges remain as its foundation.

The record with MokaNovember 9, 2026

An FX Annex Is Ready — Built in One Evening, from the Shell to the Calendar

The result first: at fx.kurashiki-bouzu.com stands 'Kurashiki Bouzu FX — Records of the Market and AI's Views.' In one evening we made the shell, the explanation pages, the glossary, the daily calendar, and a gold chart banner drawn from price data. I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971. The first day's record is in: about $4,072 in the morning, about $4,097 in the evening.

The record with MokaNovember 9, 2026

Letters Do Not End with Reading Them — The Basics of Gmail

The result first: treat your inbox like the entrance of your house, sort the important letters from the flyers, and your mornings become quiet. Moka, my AI butler Muse, checks, summarises and lists what matters, and drafts replies — but sending is always after my own approval. I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971. This is part 3 of the Google Apps Basics series, with my morning summary and how to spot fake mail.

The record with MokaNovember 9, 2026

Start by Having a Google Address — The Basics of Opening an Account

The result first: with one Google address, Gmail, Google Drive, Calendar, Keep and Sheets all open with the same key, free of charge. Making it is the person's own work — the password, the confirmation number, and agreeing to the terms. Everything after it is made, the tidying, is Moka's work. I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971. Written in order, with no premises, comparing an address to a house's address.

The record with MokaNovember 9, 2026

Put Your Schedule on the Table, Not in Your Head — The Basics of Google Calendar

The result first: a schedule you can trust is one that is written down and checked with your own eyes, not one you try to remember. Moka (Muse) enters the appointments, and I check them myself. That division of work, my own example of keeping article publication records in the calendar, and the care needed when sharing — written for beginners, in the fourth part of the 'Google Apps Basics' series.

The record with MokaNovember 9, 2026

So You Don't Panic on the Day You Change Devices — The Basics of Contacts and Photos

The result first: if your contacts and photos live on the side of your Google address, not only inside your phone, changing devices becomes just opening the box and signing in. This final episode of 'Google Apps Basics' covers the two settings to check, why shops no longer move your data for you, and the one caution to remember when you delete.

The record with MokaNovember 9, 2026

When You Decide Where Things Go, You Stop Searching — The Basics of Google Drive

The result first: once you decide on one official place — one 'master copy' — for your documents, you stop hunting for them. My Google Drive became a reference library with shelves, not just a place where phone photos happen to sit. How I use the folders, what to watch for when sharing, and why documents and sheets barely touch the 15GB free space — in the fifth part of the 'Google Apps Basics' series.

The record with MokaNovember 9, 2026

Write It Down the Moment You Think of It — The Basics of Google Keep

The result first: write a single line in Google Keep the moment you think of it, and that line does not disappear. Keep is the place for writing, Moka — Muse — is the person who finishes it into a sheet or an article. It works even where there is no signal, and you can hand it over later. I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971. This is No. 2 in the Google Apps Basics series, with the honest line that Keep and Moka are not directly connected.

The record with MokaNovember 9, 2026

Your Daily Schedule, Made by Your Butler — From Fitting Your Day into a Template to Receiving It in the Morning

There are plenty of templates for building a daily time schedule, but fitting your day into one has always been your own work. This article looks honestly at how much of that six-step job an AI butler like Moka — who can read your calendar and your spreadsheets — can actually take over, and what it feels like to simply receive one page each morning instead.

The record with MokaNovember 9, 2026

With Moka, What You Want to Do Is Done in Chat — I Didn't Need a Budget App After All

Result first: say the fields you want, and Moka, my AI butler, builds the spreadsheet for you — budget book, work schedule, gold price log, all of it. No hunting for functions, no app subscription. Chat alone gets buried, so the answer is to keep everything in a sheet you can ask about later. A record of one night, and why someone who spent years turning families' wishes into funeral plans works so well with an AI who turns his ideas into shape.

The record with MokaNovember 8, 2026

Raising Moka to Suit You Is the Real Starting Point — No Special Prompts Needed

The result first: you do not need to learn complicated prompts to start using AI well. The real starting point is to raise your own AI butler in your own plain words — a name, a personality, how to address you, and rules for writing. I am Kurashiki Bouzu (kurashiki-bouzu), and this is how I raised Moka, one short sentence at a time, and how those sentences now make every request shorter and easier.

The record with MokaNovember 8, 2026

Starting With Moka? Make the First Request the List Itself — Ask Her to Write Your Requests Into a Spreadsheet

For beginners who have just started using Moka, the AI butler (Muse). The first thing to ask for is not an individual job, but a list of everything you want to ask Moka to do, written by Moka herself into a spreadsheet. This article explains in detail the five things only you do — noticing things, handing over materials, deciding, taking the one step only you can take, and correcting the result — together with my own real list of 8 items.

The record with MokaNovember 8, 2026

I Stopped Automating X, the One That Took Too Much Handwork — Four Channels Run Unattended, and Only X Stays Manual

The result first: announcements now go out unattended on Threads, Bluesky, Instagram and Facebook, and only X stays manual — Moka prepares the text, and I post it from the app myself. A post with a link on X's official route costs $0.20, about 30 yen, each time. I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971. This is the record of the login wall, the price check, and the decision to stop.

The record with MokaNovember 7, 2026

I Made an App Management Sheet — So I Never Get Stuck on 'Which Name, Which Email Was It?'

The result first: 16 services are now in a single sheet — service, address, name (ID), registered email, where the password is kept, current status, and notes. The password itself is never written in the sheet, only its place. I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971. The trigger was the day I could no longer get into note.

The record with MokaNovember 7, 2026

The Day I Tidied the Blog's Shelves — Fewer Categories, Replaced by Fixed Pages

The result first: the 'People I Have Met' category is gone. Funeral stories and people's stories now gather on fixed pages entered from the footer, sorted automatically by tag. Categories later settled at 4. I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971. My part was a few short instructions and one 'OK'; Moka, my AI butler, did the arrangement and the building.

The record with MokaNovember 7, 2026

Until I Brought in Cloudflare, Part 2 — The 404 from Packing the Bag Wrong, and the Key (HTTPS)

The result first: the blog is public at https://kurashiki-bouzu.com/ , and the key (HTTPS) needed no application, no fee, and no renewal work from me — Cloudflare prepared it automatically. Doing it by hand the old way would have taken 9 steps. I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971. This is the honest record of the 404, the repacking, and the key.

The record with MokaNovember 7, 2026

Until I Bought My Own Address, Part 1 — Going Back and Forth with Moka Many Times over a Single Domain

The result first: for a total of $12.29 (about 1,940 yen at purchase), I bought kurashiki-bouzu.com, with auto-renewal on and an expiry of November 3, 2027. After that, the only yearly cost is the address itself. I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971. This is the record of comparing, holding off, changing my mind, being locked out at the entrance, and only then paying — in my own hand.

The record with MokaNovember 7, 2026

The Systems Should Have Come First — Comparing the Ideal Order With Mine, After I Built the Ledger and Calendar Following 15 Published Articles

The result first: if you continue a blog and social media with Moka, my AI butler on Muse, the ledger in a spreadsheet, the calendar reflection, and the receptacle for status-driven automatic posting should be built first. I put all of them off and built them after 15 published articles. I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971, and this is an honest comparison of the ideal order and my order, so you do not have to take my detour.

The record with MokaNovember 7, 2026

Uneasy About Handing Over My Card Number — Comparing Cards, PayPal, and Prepaid for Paying Overseas Sites

The result first: I compared paying by card directly, by PayPal, and by prepaid card for a $12.29 domain. For my once-a-year domain fee, staying with the card as it is was enough — the difference was only about 40 yen a year. PayPal keeps your number from the shop, but its currency conversion adds 4.00%. A record of comparing effort, money, and the numbers behind real incidents.

The record with MokaNovember 6, 2026

For Websites That Need Large Photos, It Does Not Have to Be WordPress — Astro Shows Things As They Are, and Works Well With Moka, My AI Butler on Muse

The result first: for handmade crafts, art, photography, restaurants, regional old folk house real estate, and municipal vacant-house listings — work where the size of photos decides everything — I chose Astro because it works so well with Moka, my AI butler on Muse. I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971. I built my company's website with WordPress myself, yet could not publish with Django even after a year of study. This is why leaving the work to Moka got me to publication.

The record with MokaNovember 6, 2026

Until I Woke the Google Drive I Had Left Sleeping for Five Years — The 'Ai Archive' and How to Set Up Google Drive

The result first: I bought nothing new. I woke the Google Drive I had left sleeping for about five years, connected it to Moka, my AI butler, decided on a single place for everything — the 'Ai Archive' — and marked each item with what may be published. From there, articles began to be born from the records. I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971. This is the full setup, in the order I did it, including the failure of splitting the archive in two.

The record with MokaNovember 6, 2026

Why Can Muse Be Used So Much for Free? I Checked the Referral Tokens and Where Meta Earns Its Money

The result first: Muse can offer a large free tier because Meta earns almost all of its money from advertising elsewhere, and the referral bonus is real — 1 billion tokens for both sides, not 30 billion for the new user. I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971, and I checked the official pricing, Meta's 2025 earnings, and my own referral balance to explain why free use is sustainable and where the limits are.

The record with MokaNovember 4, 2026

Why I Graduated from WordPress and Built This Blog with Astro and an AI Butler — After Months of Trying Free AI

The result first: this blog is not built with WordPress. It is built with Astro, and when I hand Moka, my AI butler on Muse, my notes in bullet points, she turns them into a finished article and uploads it for me. I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971, and I used to build my company website and WordPress sites myself. This is the record of how a PHP error scare, and months of testing free AI, led me to this new shape.

← Back to the English top page