Internet RAM
The RAM contract does not require one universal database or one universal owner. A vendor can expose a Region with its own schema, API, lifetime, security and backing.
Vendor-owned semantics
The vendor decides what the tuples mean and what higher-level API is useful: objects, collections, queries, indexes or domain operations.
Independent policy
Region scope, lifetime, residency, backing, reconstruction, split/merge behavior, reconciliation and security belong to the Region owner.
Composition
An application can use several Regions without forcing their vendors to share a schema, credentials or consensus system. The application defines the relationship.
The Regions do not have to become one system.
A process can map several independently created shared-memory segments and use them together without merging the segments. Internet RAM applies the same idea across independently governed Regions. A weather vendor, a manufacturer and your own private Region can remain unrelated systems with different owners, schemas, credentials and policies. Your application is the thing that knows how their truths relate.
The backing store is an implementation choice.
A Region can be transient memory, persistent storage, a domain database or something in between. The application relationship is to the Region contract, not to MariaDB, C++ memory or another backing technology.
Application RAM is deliberately decoupled from the whole FrogNet node.
The application-side RAM work depends on the FrogNet core for transport and semantic compression. It does not require every application datastore to participate in FrogNet discovery, elections or broker operation. How a client finds the vendor's store is the application's business.
Evidence
big5
Five heterogeneous machines in two cities mounted one Region served from a third city. The same program ran without placement logic.
FrogChat
Internet chat used the shared-RAM contract with a small client and no conventional application backend.
Sourri handoff
The application developer rebuilt and validated the handoff independently, an important test that the model could be picked up by somebody other than its author.