OASIS is presented by David Ellams as a universal Web4 / Web5 infrastructure layer: an attempt to connect many otherwise separate Web2, Web3, cloud, blockchain, storage, identity, game, and social systems through one common API.
Its central promise is to remove silos and walled gardens by letting applications work with shared Holons, Avatars, Karma, Wallets, NFTs, Quests, Missions, GeoNFTs, Templates, Plugins, Runtimes, and STARNETHolons across many different providers and platforms.
In this view, OASIS HyperDrive is the resilience layer, handling Failover, Replication, and Load Balancing across providers, while STAR ODK and the STAR CLI form the higher-level creation layer for games, metaverses, apps, and low-code systems.
For Hitchhikers, the interesting question is not whether all of this is already complete or perfectly specified, but whether OASIS can provide useful infrastructure for a Guide-based ecosystem.
It could potentially serve as a shared identity, data, quest, avatar, reputation, and asset layer for Babelfish Assemblies, Stories of Stone, Peace Gardens, the Anarchive, and cross-world experiments where the same person, artefact, quest, or proof needs to appear in many environments.
The most promising fit is the idea of STARNETHolons as reusable components: guides, quests, templates, rituals, maps, memories, media objects, and agent tools that can be created once, linked together, versioned, and reused across different OAPPs, games, websites, local pilots, and AI-assisted workflows.
The practical Hitchhikers question is therefore: > Can OASIS become the interoperability layer beneath a living Hitchhiker's Guide to Earth?
In that role it would not replace Swarm, Solid, Holochain, IPFS, or ordinary databases. Instead, it would sit above them as a holonic coordination layer, helping define what an entity is, where it is stored, how it is linked, which avatar or agent touched it, which quest or guide it belongs to, and how it can travel between worlds.