IDE Earth should not be described as “the OASIS IDE”. It should be described as an independent interface for the Earth Operating System, with OASIS as one of its first major integration families. OASIS, from NextGenSoftwareUK, can provide a powerful early bridge into Web4/Web5 infrastructure. Its own documentation describes the WEB4 OASIS API as a data aggregation, identity, reputation, token and NFT layer, while the WEB5 STAR API/ODK is described as the gamification, metaverse and application layer. :contentReference[oaicite:0]{index=0} But IDE Earth needs to remain loosely coupled. Its long-term value is not that it depends on OASIS, but that it can connect many civic, ecological, creative and technical systems through a shared interface. The architectural principle should be: > IDE Earth is independent at the core, federated at the edge, and generous in its integrations. This means OASIS becomes an adapter, not a dependency. Human.tech becomes an adapter. Solid pods become an adapter. GitHub, Obsidian, Federated Wiki, maps, calendars, publishing systems, community wallets, learning passports, media tools, voting tools and governance protocols can all become adapters. MCP is the natural way to express this pattern. The Model Context Protocol defines a host-client-server architecture in which servers expose tools, resources and prompts to AI applications. This allows IDE Earth to discover and use external capabilities without hard-coding every integration into the core application. :contentReference[oaicite:1]{index=1} So the core of IDE Earth should remain small: It should manage projects, identities, permissions, workspaces, prompts, agents, provenance, publishing, safety, consent and user experience. Everything else should plug in. This gives IDE Earth independent viability. Even if OASIS changes direction, becomes unavailable, or is not appropriate for a particular community, the IDE still works. It can run with local files, Git repositories, Solid pods, FedWiki pages, human.tech services, open data APIs, or completely offline civic design packs. The goal is not to build one mega-platform. The goal is to build a civic IDE that can host many worlds. For the Hitchhiker Campaign, this becomes an important political and cultural claim. Zaphod is not asking people to trust a single platform. Zaphod is inviting people into an open cockpit where different tools, communities and infrastructures can be connected, compared, forked, replaced and governed. This also protects the project ethically. If IDE Earth is too tightly bound to one infrastructure provider, it risks becoming another platform dependency. If it remains loosely coupled, it can become a shared public instrument. A useful phrase might be: > OASIS is one powerful engine. IDE Earth is the cockpit, workshop and map room where many engines can be connected. Or: > IDE Earth does not belong to OASIS. > IDE Earth can speak OASIS. The same should be true of every integration: > IDE Earth does not belong to Solid. > IDE Earth can speak Solid. > IDE Earth does not belong to human.tech. > IDE Earth can speak human.tech. > IDE Earth does not belong to GitHub, Obsidian, FedWiki, Holochain, Ethereum, ActivityPub, AT Protocol or any single stack. > IDE Earth is where these stacks become available to ordinary people as creative civic tools. The alpha can therefore be described as an OASIS-enabled alpha, not an OASIS-dependent alpha. That distinction matters.