⬡ OASIS Holonic Architecture
⬡ W3AI Holonic Intelligence
Every application in OASIS lives somewhere in the holarchy — from Moon to GrandSuperStar. Scan a GitHub repo, a live on-chain protocol, or a local codebase.
Repository URL
Public repos only. We use the GitHub API — no auth needed.
Protocol, token, or contract address
We query DefiLlama and CoinGecko — fully public, no API key needed.
Try an example:
Absolute path on this machine
Scanned server-side via the OASIS API at localhost:50564.
Try an example:
⬡ HOLONIC SCAN IN PROGRESS
Projected Entry Tier
—
Calculating...
★ Karma prerequisite
This is your projected entry tier based on data gravity alone. To hold this position in the OASIS holarchy, your builders' Avatar must also meet the Karma threshold — earned through contributions, quests, and ecosystem participation.
What this means in OASIS
OASIS gamifies your project's growth. As your codebase expands and your community grows, your holonic body evolves.
⬡ OASIS Holonization
Holonization stores every file as an IHolon — a universal data object with cross-chain portability, version history, and provider-agnostic identity.
01 — IDENTITY
One universal ID
Every holon carries a GUID, audit trail, and provider-agnostic storage key. Move between Ethereum, IPFS, and MongoDB — zero data loss.
02 — HIERARCHY
Holons nest infinitely
Your project becomes a Planet containing Moons containing Zomes. Every level maps to real code structure — folders, modules, files.
03 — PORTABILITY
Every provider, one API
IOASISStorageProvider means your holons run on any backend. No lock-in. Auto-failover and replication built-in.
04 — KARMA
Reputation travels with you
Builders accumulate karma across every OASIS app. Contribute once, earn everywhere in the ecosystem.