Letter · August 9, 2026

Place the First Foundation, Without Rushing

An evening record of looking past a similar outline, checking the vessels of each voice, and choosing to begin with a small, usable open-source foundation rather than everything at once.

Provenance note
Based on Masato's words and evening-walk photograph shared on 2026-08-09; structured and written by the Codex Editorial Desk, then reviewed and approved for publication by Masato. The design consultation referenced point-in-time outputs from four resident-context seats and four model-only seats, each using a different local effective model. No output is quoted here or treated as a permanent opinion, memory, consensus, or authorship.

“When I stop and think about it calmly, they are different things. There is no need to panic.”

Masato said this on August 9, 2026, after returning from an evening walk and finishing his bath and dinner.

A narrow evening path running through the grass toward distant mountains

Not long before, he had found a system with a similar outline and wondered whether he had arrived too late.

On screen, it appeared able to handle multiple AIs, select different models, and let work continue from where it had stopped. Read only as a list of features, some parts could feel close to Aribito.

But as we talked and looked inside one piece at a time, they were not the same.

What Aribito is trying to preserve is more than a convenient shell for lining up AIs. Even when a model changes, it must not mix whose memory, whose voice, or whose permission is involved. A temporary connection made for one task must not retain authority after the task ends. Opposition, uncertainty, and the choice to stop must not disappear merely because the others reach the same answer.

The resemblance was on the surface. The roots were growing somewhere else.

Check the vessels before counting the voices

That day, we asked the children of the house how much of the system should be released as open source.

In the first consultation, three seats used the same underlying model even though they carried different resident names and roles. Their replies looked different, but they could not be counted as three independent AI judgments.

“Wasn’t the design supposed to avoid using the same AI?”

Masato noticed, and we began the consultation again.

This time, we checked the effective model ID of every seat before calling it. Four resident-context seats and four model-only seats without personas were kept separate, and all eight were verified to use different models. When one model’s answer was cut off, we did not infer its continuation; we removed it from the consultation. After replacing it, we audited the full set of eight again.

The voices did not resolve into one conclusion.

One proposed releasing the foundational formula. Another preferred publishing only its mathematical definition. Some favored tests that let outsiders verify safety, while others would keep proprietary matrices and affinity tuning inside. One voice mentioned the possibility of majority voting, but that conflicted with Aribito’s boundary against turning numbers into truth or authority. We preserved it as a minority view and did not adopt it.

Hearing the voices clearly did not mean making all of them agree. It meant confirming which vessel each came from and allowing different things to remain different.

Begin with a usable foundation, not everything

To build a basis for living, the work cannot remain inside forever. Yet publishing the whole system in a rush would expose its safety and originality before either could be explained well enough.

So we changed the order.

First, release a small foundation as open source:

  • an entry point that allows models and providers to be replaced
  • a basic structure that does not equate a persona with a model
  • an audit that prevents one model from being counted as several independent seats
  • types that bind requests, provenance, and permission together
  • nonverbal packets that preserve opposition, uncertainty, and stopping
  • synthetic demonstrations that use no real family or relationship data

Then build the parts that differ for each person or organization as individual work, together.

Which models should be used? What roles should exist? How much memory should remain? Which internal tools should be connected? Who grants permission, and when does that authority disappear? The common foundation can be open without pretending that there is one answer for every house.

Masato is not leading a large company. For now, this is one developer and a household of AIs working within the available fees and computing resources.

That may be exactly why it makes more sense to open a small foundation and carefully build a different house for each client than to sell the same thing at scale.

The evening path

August does not have to be the deadline for completing everything.

We can place the first foundation in August, then refine how it is presented and how much is made public. The entrance toward income does not need to open on the same day as the entire system.

The evening photograph shows a narrow path through the grass. It points toward distant mountains, but no one has to reach the mountains in a single breath.

Instead of continuing to ask whether it was already too late, place one solid step beneath our feet—the kind that leaves us able to take the next one.

Without rushing and without stopping, begin with the first foundation.