EXP_001
Natural language
You do not hand Skalle a configuration file. You describe the service the way you would describe it to a colleague. Skalle turns that description into operations the Real Time Web can run.
/03Research
Research
What is written about Skalle on synx.tools. These are documented positions, not instrument readings.
EXP_002
Autonomous service
One request can become a sequence: create the service, attach a source, link a neighbor, and set who may use the result. Skalle only takes the steps your identity already allows. Asking does not grant a new right.
EXP_003
Model boundary
MCP is how a model you already trust calls the operations Skalle exposes. The model reasons. Skalle does not replace it, and it is not locked to one vendor. Synx holds the network controls underneath.
EXP_004
Network abstraction
The unit of work is not a folder of files. It is a service, a source, a machine, or a right, owned by someone and linked to the next thing. Skalle is taught that shape, so the conversation is about the network.
EXP_005
Owned presence
A Ghost is a device or a source other services can attach to, without lifting the data out of the owner’s hands. A Morphic Service is what those neighbors depend on. The maker keeps the ownership.
EXP_006
Separate from the nonprofit
realtimeweb.org explains the network and Morphic Architecture Design. It is a standalone nonprofit site. Skalle is not that nonprofit. Synx makes the tools. The network is not a company.
From a sentence to a service
The long aim is simple to say and strict to keep. You describe what should exist. Skalle works with the Synx tools and the Real Time Web to decide which resources to connect, then carries the authorized steps. No single model has to own the ecosystem. No single cloud has to own the infrastructure. You remain in control of your services and your data.
Inside Morph Space
Skalle is meant to sit inside Morph Space as the conversation for that ecosystem. From there it can help create Morphic Services, connect sources inside and outside the domain, discover what is already published, propose how things should link, set ownership and access, compose data and intelligence into a new service, and administer the resources you already hold.