Kimiko, my nickname for ChatGPT, helps me organize receipts so I can look back at our household spending. As we discussed recording individual items, cabbage came into the conversation.

Suppose the same shop, at the same time, offers a quarter cabbage for 158 yen, a half for 308 yen, and a whole one for 598 yen. These were prices I used as an example to explain the issue.

Multiply 158 by four and you get 632. The arithmetic is correct. But in this example, the shop sells a whole cabbage for 598 yen. Buying four quarters and buying one whole cabbage do not cost the same. The pieces add up to a whole cabbage; the prices do not have to cooperate.

The gray-haired fictional author in a green shirt compares a cabbage wedge with a whole cabbage on the table.
AI illustration about purchase units, not a reconstruction of an actual shopping trip or prices.

That is why I wanted more than the name “cabbage” and a price in the receipt records. Was it a quarter, a half, or a whole one? To see what I paid for, I wanted to keep that detail too.

If I calculate an equivalent price for a whole cabbage to make comparisons, that is a calculated value. It should not replace the unit I actually bought or the amount I paid. The discussion reminded me of a term from work: nisugata, describing the form or packaging in which goods are handled. Somehow, a household-budget conversation had brought a work term back to the table, with a cabbage in tow.

This was a requirement I was explaining to Kimiko, not a report of completed analysis. I did not want to admire a neat set of numbers and then wonder, “But which size did I buy?” Even a quarter cabbage gets a detailed specification from this particular opponent of extra chores.

WRITTEN BYYoshio Taki

IBM i / AS/400 System Engineer