Greek: “whole” + “part”
A holon is both a self-contained entity and a component of a larger system. It is whole on its own. It is also a part.
In OASIS, every data entity is a holon: users, applications, quests, NFTs, game objects. Each holon carries a unique GUID, parent-child references, extensible metadata, and provider-agnostic storage keys.
This means any holon can be stored on any provider — and moved between them without data loss. One data structure. Every backend.
Every holon has a GUID, version history, audit trail, and change detection. It knows who created it, who modified it, and when.
Holons nest inside holons. A parent references children; children reference their parent. Infinite depth. One tree.
Each holon maps its ID to every provider it touches via ProviderUniqueStorageKey. Move between Ethereum, MongoDB, Holochain — zero data loss.
A single holon is powerful. But the real architecture emerges when holons nest. OASIS organises all data into a celestial hierarchy — a holarchy — where every level is both a self-contained whole and a part of something larger.
The STAR ODK maps this hierarchy to a cosmic metaphor: Stars contain Planets, Planets contain Moons, and Moons contain Zomes — the atomic holons at the bottom. At every level, the same rules apply: identity, persistence, interoperability.
Celestial mapping
Omniverse → Multiverse → Universe → Galaxy → Solar System → Star → Planet → Moon → Zome → Holon
Top-level platforms — full OAPPs with their own ecosystems. A Star is an application that contains Planets and Moons as sub-modules. Think of it as the root of an entire product.
Major modules or feature domains within a Star. Each Planet is a holon — independently deployable, with its own children — but bound to its parent Star’s identity.
Small, self-contained apps or micro-services. Every OAPP starts life as a Moon. Moons orbit their Planet parent and carry their own Zomes inside.
The atomic layer. Zomes group related holons — profiles, quests, NFTs, game items — into logical bundles. Each holon is the leaf node: one piece of data, stored on any provider.
IOASISStorageProvider defines CRUD for holons and avatars. Every provider implements it. Your app calls one API regardless of backend.
If the active provider goes down, OASIS switches to the next in the failover list. No downtime. No code changes.
Write to multiple providers simultaneously. Data lives on Ethereum and MongoDB at the same time. Redundancy by default.
Generate, publish, install, and launch holonic OAPPs from the command line. Scaffolds the full OASIS stack.
Maps your data models to holons automatically. Your classes inherit holon properties — GUID, versioning, provider keys — without manual wiring.
OASIS Applications. Holonic apps that run on any provider. Build once, deploy to any blockchain or database the OASIS API supports.
Store holons on Ethereum today, migrate to Solana tomorrow. Zero code changes.
Primary provider down? The next one activates automatically from the configured failover list.
Holons replicate across multiple providers simultaneously. Data is never trapped in one place.
Requests distribute across active providers based on performance metrics.
Your Avatar is a holon. It carries credentials, provider wallets, and JWT tokens across every OAPP.
Numerical reputation tracked via akashic records. Earned in one app, visible in every other.
NFTs, tokens, and items stored in your Avatar holon. Accessible from any provider.
Log in once. Your profile, reputation, and assets follow you across the entire OASIS ecosystem.
A governed IP Pool with clear valuation and licensing terms. A Builders Fund that helps teams form real companies on top—routing revenue back to creators until a fair cap is reached.
Every holon starts as an idea. Tell us what you’d build on OASIS — a game, a DAO tool, a cross-chain bridge, anything. We collect every idea and help the best ones get started.