Describe
Say what should exist, in ordinary language.
/02System
Skalle takes a sentence through the Synx toolchain and leaves a service on the network. It is not a coding assistant.
Say what should exist, in ordinary language.
Find services and sources already on the network.
Make the service that should do the work.
Connect resources. A neighbor does not require a new private API.
Set ownership, access, and how the service is distributed.
The service operates on the Real Time Web.
The aim is to build and configure the actual Real Time Web architecture, not only to explain it.
Skalle creates and operates distributed services on the Real Time Web. It is not a coding assistant. It is taught the principles, architecture, and developer tools of that network, then works with you in conversation.
REQExample
Create a service that receives live energy data from my buildings, combine it with weather data, give my optimization model access to it, and expose the resulting energy forecast to my application.
A request Skalle can take through the Synx toolchain, from intent to a running architecture.
A coding assistant explains a file or drafts a function. Skalle is taught the principles, the architecture, and the developer tools of the Real Time Web, then works with you in conversation. The aim is the running service, not a paragraph about how you might build it later.
Through MCP, a model you already use can call the Real Time Web operations Skalle exposes. Chat, a desktop tool, or an editor can be the place you speak. Skalle stays the capabilities. A team that wants the session on its own ground can run it as its own service and tie it to the sign-in it already uses.
Each person works inside an isolated session tied to their identity. A model connected from outside can look, unless modification is explicitly turned on. A change can wait for you. Tokens do not stay open. Skalle does not receive a right just because it asks.
Weather can feed an energy reading. That reading can feed a building. The building can feed the people who run it. Each step can stay owned by the person who made it. Weather can feed energy. Energy can feed a building optimizer. That optimizer can feed facility management. Creators keep ownership, and the larger share of revenue.