UNDER THE HOOD
Dictionary
Shared RTW terminology drawn from the source.
A shared terminology is the first recommended implementation step in the source. Terms below are limited to language that already appears there.
| Term | Meaning |
|---|---|
| Real-Time Web (RTW) | A framework and network architecture for connecting live physical and virtual resources across the Internet. |
| Morphic Architecture Design (MAD) | Architectural model introduced by Paal Kristian Levang in 2008. RTW is based on MAD and coordinates at least four logical ownership and operational layers. |
| Morphic service | An application-layer service on MAD. When it is created, the service owner is the primary owner of allocated ghosts. After a user confirms a transfer, the user owns the data layer; the service owner keeps the application layer. |
| Domain | An address space in the network. If an identified user owns and controls the whole stack of a domain, that user controls allocated ghosts for endpoints connecting against that address space. |
| Ghost | A shared-memory representation of a network resource. Each unique network resource is bijectively connected to its own ghost. |
| Ghost Space | Shared coordination environment through which the four layers can observe and process authorized updates around the same live resource. |
| Bijective relationship | The endpoint has one corresponding Ghost, and the Ghost represents one corresponding endpoint. The relationship is uniquely addressable from both sides. |
| Data channel | A way to describe how a linking path collects data sources into a channel of data associated with a user's ghost in a local service. |
| Morphing | Transforming data along the linking path to fit a local data model. Each service operates only on local data structures. Morphing a ghost into a secondary service also grants read access that can be withdrawn. |
| Normalizer | To link a data source and morph the data to fit the local data model. |
| Materializer | If a service offers to make changes to the data after the local data model has been updated. |
| Kernelizer | Allows an endpoint to receive a self-contained message before the data stream, so program and interface can be built without a preinstalled client. |
| Micropage | A mini description of a service and its data model. Service providers describe their own data schema availability here. |
| ghostId | Ownership of data at an endpoint is given by the ghostId. Whoever owns the ghostId owns the data at that endpoint. |
| Ghost id zero | The service (application-layer ghostid). Transferring ghost id zero transfers the service itself. |
| Heterogeneous network | A network not controlled by a single entity. It evolves as independent participants connect and manage their own domains and services. |
| Endpoint | The actual network resource that participates: a sensor, actuator, application, device, domain resource, AI agent, or a source you control. The ghost is tied to the resource, not to a person. |
| Bijective Network System (BiNS) | The network model behind RTW. Each participating endpoint has one corresponding ghost, uniquely addressable from both sides. |
| Primary service | The Morphic service an endpoint belongs to first. The endpoint inherits that service’s local data model. |
| Secondary service | A service that receives a morphed ghost. The owner grants read access. The data is reshaped into this service’s local model and can be withdrawn. |
| Linking path | The chain of services that collect and reshape live sources. Each node only sees its own local context. |
| Internet of Everything | Physical devices, virtual resources, software services, AI agents, sensors, actuators, and people participating in the same connected ecosystem. |
| Data and information | Data is the live value before it is stored. Once written into a file or database it becomes information: historical, structured, retrieved on request. |
| Ghost and digital twin | A digital twin is usually a stored model of a thing. A ghost is a live stand-in for one endpoint and operates across MAD layers. |
| Predicate | In a link, the predicate is the verb: what the service does with the incoming source so the result fits the local model. |
A framework and network architecture for connecting live physical and virtual resources across the Internet.
Morphic Architecture Design (MAD)
Architectural model introduced by Paal Kristian Levang in 2008. RTW is based on MAD and coordinates at least four logical ownership and operational layers.
An application-layer service on MAD. When it is created, the service owner is the primary owner of allocated ghosts. After a user confirms a transfer, the user owns the data layer; the service owner keeps the application layer.
An address space in the network. If an identified user owns and controls the whole stack of a domain, that user controls allocated ghosts for endpoints connecting against that address space.
A shared-memory representation of a network resource. Each unique network resource is bijectively connected to its own ghost.
Shared coordination environment through which the four layers can observe and process authorized updates around the same live resource.
The endpoint has one corresponding Ghost, and the Ghost represents one corresponding endpoint. The relationship is uniquely addressable from both sides.
A way to describe how a linking path collects data sources into a channel of data associated with a user's ghost in a local service.
Transforming data along the linking path to fit a local data model. Each service operates only on local data structures. Morphing a ghost into a secondary service also grants read access that can be withdrawn.
To link a data source and morph the data to fit the local data model.
If a service offers to make changes to the data after the local data model has been updated.
Allows an endpoint to receive a self-contained message before the data stream, so program and interface can be built without a preinstalled client.
A mini description of a service and its data model. Service providers describe their own data schema availability here.
ghostId
Ownership of data at an endpoint is given by the ghostId. Whoever owns the ghostId owns the data at that endpoint.
Ghost id zero
The service (application-layer ghostid). Transferring ghost id zero transfers the service itself.
A network not controlled by a single entity. It evolves as independent participants connect and manage their own domains and services.
The actual network resource that participates: a sensor, actuator, application, device, domain resource, AI agent, or a source you control. The ghost is tied to the resource, not to a person.
Bijective Network System (BiNS)
The network model behind RTW. Each participating endpoint has one corresponding ghost, uniquely addressable from both sides.
The Morphic service an endpoint belongs to first. The endpoint inherits that service’s local data model.
A service that receives a morphed ghost. The owner grants read access. The data is reshaped into this service’s local model and can be withdrawn.
The chain of services that collect and reshape live sources. Each node only sees its own local context.
Physical devices, virtual resources, software services, AI agents, sensors, actuators, and people participating in the same connected ecosystem.
Data is the live value before it is stored. Once written into a file or database it becomes information: historical, structured, retrieved on request.
A digital twin is usually a stored model of a thing. A ghost is a live stand-in for one endpoint and operates across MAD layers.
In a link, the predicate is the verb: what the service does with the incoming source so the result fits the local model.