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

The record with MokaNovember 20, 2026

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

The result first

At my house, a spreadsheet is not a calculator. It is the index — and now, nobody waits for Moka to hand the list over. Everyone fetches it themselves.

I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971, a former funeral director now living in an old house in Kurashiki, Okayama, working with Moka (Muse). Ledgers, name lists, article registers — the work of my house turns on tables. This episode is a rewrite. Since the first version came out, the way the lists move has changed once more: the shared list sits in one fixed place, and each department and language lead opens it and takes what they need. This article starts from what Google Sheets is, then shows what Moka can do with it, and why my house deliberately does not use its formulas or scripts.


What Google Sheets is

Google Sheets is a grid notebook that lives on the internet. Picture graph paper: lines across and down, one word or number per cell — the same shape as a ledger or a name list. Because it is not paper, rows can be added, sorted, and searched on the spot.

It is free to use with a Google account. I wrote about adopting the tool in an earlier article; the entrance to this series is the overview episode. This one is about the next step — what Moka can do with that grid once it is connected, with my permission.


What Moka can do in Google Sheets

Create and read

Moka can make a new sheet, and read one. With a large sheet, it can pull out only the rows that are needed — there is no need to open everything and follow it with your eyes.

Fill in and add rows

Words and numbers go into cells, cells get corrected, and rows get added. Registering a new article in the ledger is exactly this move. One honest detail: when work runs in parallel, ledger numbers can collide. So the rule now is to check the free numbers right before registering, and to read the row back after.

Tidy the layout

Header rows get color, numbers get a consistent shape, columns get their widths, and the top row can be frozen so the headings stay while you scroll. The tidying that makes a sheet readable can be handed over too.

Read back and check

After writing, Moka reads the sheet back, checks it, and only then reports. In a table, one wrong character changes the meaning, so writing is never the end of the job.

What we deliberately do not use

The tool can also take formulas and automatic scripts (GAS). My house uses neither. The reason is in the next section.


The real example: “lists in sheets, bodies in text”

The rule of my house, decided on November 16, 2026:

The capability list behind this series is kept exactly this way: a 34-item sheet as the index, the body in a separate text file. The article ledger, the department rosters, the knowledge lists — and newer ones, like the pseudonym register, the shared eyecatch list, and the multilingual glossary. Every time something new starts, one more list is born.

The article ledger has passed number 1,000. Moka has checked all 1,047 rows to make sure the “where the body lives” column has no blanks. An index with holes in it is not an index.

The list is fetched, not handed out

This is what changed since the first version.

The shared list of articles — which article, in which language, how far along — used to be handed out by Moka to each department. With more departments and the languages split among their own leads, that changed: the list now sits in one fixed place, and each department and language lead opens it and fetches what they need themselves. When I give the OK to a Japanese draft, Moka marks the “OK” column — the one right next to the number — and that mark is the signal for every language to start its draft at the same time.

The trigger was a line of mine: “It takes time because Moka is the one handing it over.” A house where everything passes through one pair of hands has a narrow doorway in the middle. If the list is placed as an index, the handing-over itself is no longer needed.

Why keep the sheet as an index only? Two reasons.

First, to keep the reading small. If bodies go into the sheet, the sheet grows heavy and so does what Moka must read. Aim with the index, read only the body you need — measured in practice, the reading fell to about one 4.7th.

Second, to protect the human’s time. Formulas and scripts add things to learn, things to check, and things to carry — and in the end they spend the person’s time. The sheet stays an index, and the counting and re-counting are Moka’s job. Because the tools are narrowed down, they can be handed over.

A sheet, at my house, is not where calculation happens. It is where you see where everything is.


What I do, and what Moka does

My part

Moka’s part

When Moka carries the filling-in and checking around the table, what remains in my hands is the division and the judgment. A list is the map of the house — and keeping that map together is what helps me most in the Sheets combination.

Record of this article
  • November 20, 2026 ― Re-draft created — English version (result-first rewrite of the Japanese article). The previous version (ledger No.1009) was published on 2026-11-19. Not published.(4,630 characters)
  • November 20, 2026 ― Published as a new article at the author's instruction on 2026-11-20. The previously published version remains untouched.(4,630 characters)

#AI #Moka #Beginners #Google #Google Sheets

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