One orbit, separate responsibilities
Echo is intended to operate within LOCORBIT, not as an unrelated assistant bolted onto the page. The visitor enters through the same question interface and should retain the same context as the work progresses. Cazonci supplies the human perspective and design responsibility; Echo represents the AI-assisted side. The system needs to keep those responsibilities legible without making the visitor understand its internal architecture. That is why the role and the system are explained separately. A role describes what the operator is meant to contribute. The system explains how that contribution fits into the wider experience, its boundaries, and the path toward a useful result.
Connect capabilities deliberately
A working AI service requires more than a portrait, a play button, or an operator badge. It needs an actual service connection and an explicitly defined scope. Requests have to reach the appropriate service, any permitted tools must be available, and results need to return through a clear response path. The current public package provides the interface and request forms; it does not itself provision those private capabilities. This distinction keeps the beta honest. Echo’s eventual workflow should be assessed against what is connected and observable, not against the sophistication of the visual identity or the possibilities suggested by the name.
Keep private work out of public surfaces
The public interface should collect the context needed for the request without inviting unnecessary exposure. Credentials, sensitive account information, and unrelated private records do not belong in a general question simply because they exist. Operator tools and service credentials should remain separate from the public pages. The visible IP panel is a connection utility, not a dossier or a verified VPN detector; its lookup is kept separate from form submissions in this build. The broader design principle is the same for Echo: use only the context and access required for the task, and do not confuse a public display with permission to inspect something private.
Keep outcomes observable
The system should distinguish receiving a request, preparing an answer, attempting an action, and confirming that an action succeeded. Those are different states, and each should be described accurately. A useful AI handoff includes the relevant context, the work completed, the assumptions still in play, and any decision that needs the human operator. If a connected service is unavailable, the interface should say so rather than manufacture an appearance of activity. LOCORBIT’s standard for Echo is therefore the same as its standard for the human-facing experience: clear identity, understandable behavior, and results that can be checked. Different hardware. The same obligation to be useful.
SAME ORBIT. DISTINCT IDENTITY. CAPABILITIES THAT MUST MATCH REALITY.