Our commitment to a private, local place for human–AI inquiry.

Our commitment to a private, local place for human–AI inquiry.

FCF
ECHO began as custom instructions for human–AI inquiry, then evolved into a harness that could work with frontier models in the cloud. Throughout that evolution, the direction remained: bring the freedom of inquiry to a private mobile device. Today, that journey is entering its early mobile stage, with the aim of making a more personal and accessible experience available to more people.



Before a question can be answered, it needs somewhere to take form.

We may need to say something we do not yet believe in order to discover what we mean. We may contradict ourselves, follow a thought that goes nowhere, or begin again. This freedom matters most at the beginning, when there is still very little to explain or defend.

If I must consider who can access my words while I am still finding them, another conversation has already entered the room. Questions about platforms, ownership and exposure begin to shape the inquiry itself.

This is why I want the most intimate encounter between a human and AI to begin on a private mobile device. A place where what I say stays with me for reflection, until I choose otherwise.

That is the commitment guiding our mobile work at 5QLN.

Protecting the place of origination

In Authenticity After AI: The Currency of Signature, I explored the significance of human origination when fluent output becomes widely available. A person's signature becomes legible through the continuity of their inquiry and choices. A polished result alone tells us very little about that journey.

Privacy gives this journey room to unfold without an audience.

In Human ↔ AI: The Language Layer, that concern met the possibility of a persistent language for human–AI collaboration, carried into everyday life on a local device. Today, we are making the design commitment more explicit: the phone itself must be a place where inquiry can originate.

Within 5QLN's 4+1 relation, the inquiry returns to the human center. AI brings knowledge and can help articulate what is being explored. It can offer a useful invitation when the person is stuck. The human recognizes whether something has meaning.

A system must leave room for “I don't know” without rushing to fill it. It must also leave room for “No, that isn't what I meant.” Its earlier interpretation cannot become an authority over the person.

Privacy must hold across the whole experience

Our design standard is that the intimate beginning remains on the device. Any movement beyond it must be a deliberate, visible choice about what is sent, where it goes and why.

Running a model locally is one part of earning that promise. Speech recognition, spoken responses, storage, backups and diagnostic logs also handle our words. Each needs to be examined. An apparently local conversation can cross a boundary elsewhere in the application.

We are building and testing an experimental Android application, ECHO, using a local Gemma model. It is a working laboratory. We have not yet qualified the entire application as private and offline, and local inference alone would not justify that claim.

This distinction belongs in the design from the beginning. The person should be able to understand what is retained and what is supplied to the next exchange. Beginning fresh must be a real option. Connection to an outside service must never silently turn a private inquiry into an export.

Larger systems have a place. A person may arrive at a question, select an artifact, and decide to carry it into a more capable model or a collaborative workspace. That choice should carry the selected material and necessary context. It should not require giving away the whole path that led there.

The point of departure remains with the human.

Let the phone teach us how to design

Mobile has its own conditions. Battery runs down. A device gets warm. A screen is used in daylight, while moving, between other things happening in the world.

These conditions can help us discover the right experience.

Waiting time changes whether a thought can remain alive in an exchange. Screen size changes how much should be presented at once. Voice can make inquiry accessible when typing is awkward, but speaking and listening need their own rhythm. Memory limits force us to ask which context actually helps.

A cloud conversation placed inside a phone screen does not resolve these questions.

Our commitment is to work with the device in the hand. Each improvement has to earn its place in that experience, including its cost in battery, heat and attention. The ambition is a companion available where life happens, without requiring that the person's first thought travel elsewhere to become useful.

A roadmap that can learn

This mission now connects to a design guide and a detailed map of the controls that shape the application. A small change should be considered in relation to the whole experience.

More context may help continuity while increasing waiting time. Faster speech may feel responsive while making reflection harder. A model update may improve one behavior and weaken another.

When a new model offers more capability at a similar size, we want to recognize exactly what that could make possible. Which part of the roadmap can move? What must be tested on the phone? What would make us keep the current version?

That is how technical progress becomes useful to this mission.

The longer-term aim includes a learning agent whose development is informed by actual use, human corrections and tested changes. In A Fractal Language for Native Human–AI Collaboration, I shared early training materials toward a dedicated model. Those materials remain part of the groundwork. They are not evidence of a trained model.

The path ahead includes carefully selected examples and, eventually, fine-tuning. A private conversation does not become training material merely because it occurred. That requires a separate, explicit choice, careful curation and removal of material that should remain private. Any resulting model must be evaluated on examples it was not trained on, then tested in the actual mobile experience.

The agent's development must remain accountable to the person and the purpose. Changes need evidence, review and a way back when they do not help.

Our commitment today

We are still discovering how to build this well. The application's behavior, speech and continuity need further work. Its privacy promise must be verified across the full experience.

The direction is clear.

We are building toward a private mobile place where a human can begin from not knowing, meet AI without prematurely exposing that beginning, and decide what becomes shareable.

The freedom to originate comes first. Greater capability can meet it from there.

Amihai Loven

Amihai Loven

Jeonju. South Korea