Current implementation: the shared-RAM contract and engineering record
Sensors and physical systems.
Give each sensor or source an owned address. Readers can hold the readings they depend on and derive the view they need. The earlier physical demonstration actuated a New York lamp from Seattle; it is evidence of that path, not a claim about every actuator’s safety or timing contract.
People and media.
Presence, invitations and call state fit shared application RAM. A media plane carries the stream. The Communicator demonstrates this separation while adapting to a changing link. Read its two-plane contract.
Compute.
Worker contributions can materialize independently in state. FrogTorch preserves PyTorch above the backend and explores heterogeneous paths. A resource model assembled across machines is possible; a complete scheduler or datacenter management system is not supplied by those measurements.
Scoped networks.
A local network, remote device or isolated workload can publish facts and participate in a scoped network. The current bridge demonstrates PCs and Android devices and has namespace tests for overlapping private networks. A finished container orchestration product is not implied.
Another existing contract.
Take an incumbent system, preserve its external behavior, move ownership and observation into state, then measure what work disappeared. The conversion record is a starting point, not a performance guarantee for the next program.