A Community Site Operations Team Is Ready — A Place Where Everyone's Practice Remains Needs an Owner
The result first: a dedicated operations team for the “Muse Community Site” — a standalone site where people who use Muse bring together what they have put into practice — is now in place, with 5 seats. The site itself is built the same way as my blog, submissions come in through a Google Form, and there is no comment section at the start. Three rules were handed to the team from the beginning: my own practice appears there only as a title, a short summary, and a link to my blog; nothing is published until the person who wrote it has seen the edited text and replied that it may be posted; and no personal information is carried, with “This is not an official Meta site” written clearly at the entrance.
Hello, I am Kurashiki Bouzu, born in 1971, a former funeral professional. I live in an old folk house in Kurashiki, Okayama, and work together with Moka, my AI butler.
The team’s name is the “Muse Community Site Operations Team.”
Why I created the team
The trigger was a short remark from me:
“If only we could make a community site for Muse, too.”
When I had Moka look into it, an official community site from Meta did not exist yet. In the private sphere, there are gatherings such as Facebook groups and communities inside Discord (a tool for making places to talk). But those are places where posts flow away. A standalone site in a shape where practice remains as articles, and people who come later can reach it through search, was nowhere to be found.
So the plan was settled. The body is a standalone site built the same way as my blog. The window for submissions is a Google Form (Google’s form tool). No comment section will be attached at first — because watching over one takes effort forever, and because, for a “place where things remain,” arranged articles fit better than flowing posts.
A site is not finished once it is made. Each time a submission arrives: receive it, arrange it, have the person who wrote it check it, post it, and fix the list. That is the repetition. A team that keeps holding the plan is needed — that is what I said.
“This department is needed, too.”
The team has 5 seats
The first draft of the lineup was made for me by Sebastian, the vice-butler. This is how this house works: place one person in charge, and that person places only the roles that are needed. This time, the seats were divided by each section of the work flow.
- Person in charge — Holds the schedule for the whole site in one line, and reports to me. Also the guardian of the “rules to guard” written below
- Site building and operations role — Builds the site, checks the display, and keeps the place it sits. The technical work
- Submission editing and posting role — Arranges the practice that arrives into readable text, and holds it through to posting. This role is the core work
- Records and list management role — Records, with dates, how far each submission has progressed, and keeps the list up to date
- Community site secretary — Acts as the receiving desk, handling only reception and carrying
The roles I did not place are also kept in the draft, together with the reasons. The biggest one is a role to watch over a comment section. Because it was decided not to attach the section itself, there is nothing to watch over. No role for an English version, either, because it was decided to start with Japanese only. Not being greedy is how this house builds a lineup.
There are 3 rules to guard
This team has lines that were decided and handed to it from the start.
The first is how it is divided from my blog. My own practice is not carried as full text on the community side. Only a title, a short summary, and a link to the blog are placed there. The full text is unified on the blog. The full texts on the community side are only what other people have contributed. The same text is never carried in two places.
The second is approval-based posting. The arranged text is shown to the person who wrote it, and it is posted only after receiving a reply of “you may post it.”
The third is to carry no personal information. And, at the entrance, to write clearly, “This is not an official Meta site.”
The first job comes after the address is decided
The site’s address and name were still awaiting my judgment. Four candidates are lined up in the plan document. Until they are decided, this team’s work is to prepare, in drafts, the shape of the shelves and the steps for receiving submissions. The actual building of the site and its publication come after the address is decided and my approval is taken.
A record in numbers
With the new 5 seats together, the house became 50 departments and 145 seats.
The salary estimate was also recalculated. Using the method of applying the national statistics values by occupation to each seat, the new 5 seats of this team come to 29.993 million yen a year, and the whole house to 1,004.013 million yen a year, an average of 6.924 million yen per seat, and about 83.67 million yen per month (figures before checking by the salary calculation department).
Let me write this first: this organization’s sales are still 0 yen. The only thing actually being paid is the fee for using Muse. The estimate figures are placed as a yardstick for what it would come to at an ordinary company.
Postscript (2026-11-18)
The numbers in the main text are the record from the time the team was set up. After that, on the night of 2026-11-17, there was a reorganization that abolished 5 departments with no record of work, and on 2026-11-18, one knowledge collection and preservation seat was added to the Security Laboratory operations team. As of publication on 2026-11-18, the house is 49 departments and 169 seats.
The community site was published on 2026-11-17 at muse-prompt.kurashiki-bouzu.com. It is open in 4 languages — Japanese, English, Chinese, and Spanish — and submission forms are prepared for each language.
Related reading
- The Chinese team set up on the same day: A Chinese-Language Team Is Ready
- The Spanish team set up on the same day: A Spanish-Language Team Is Ready
Record of this article
- November 17, 2026: Draft created. A record of setting up the Muse Community Site Operations Team. Ledger No. 149. Publication awaited my judgment
- Sources for the numbers: salaries from the Ministry of Health, Labour and Welfare’s “2025 Basic Survey on Wage Structure,” estimated annual income by occupation. The current state of communities (that there is no official standalone site, and the shapes of private gatherings) follows the research record in the plan document
~/workspace/blog-admin/muse-community-site-plan-2026-11-17.md - November 18, 2026: Published (by my decision). A postscript was added at the time of publication
- November 18, 2026 ― English draft created (results-first rewrite of the Japanese article, ledger No. 149). Not published; publication is a separate step.(5,485 characters)
