Avvyland is a 3D presentation and distribution network — a platform where commerce, content, and entertainment live inside explorable 3D worlds rather than 2D pages. The core thesis: existing marketplaces (Amazon, Shopify) lack the game-like discovery experience of a physical mall. Avvyland rebuilds commerce as navigable 3D space.
Brane — a 3D world / scene; functionally a "3D webpage." Types: personal, showcase, rental, public.
Object — a 3D entity inside a brane, instantiated from a Prototype.
Prototype — a template defining default object properties and behaviors.
Block — an individual scene element placed in a brane's grid.
Handler — server-side JavaScript (Otto engine) that encodes economic rules, possession terms, and revenue splits for an object or brane. Conceptually a smart contract.
Portal / Teleport — a one-way or two-way bridge between branes with optional economic routing.
Space — a top-level container that organizes branes.
Karma — internal currency. Two flavours: purchased (non-withdrawable) and earned (withdrawable). Negative balances are allowed but search-depressed.
NPC — AI-driven non-player characters (later stages) that profile users through dialogue for personalized funnels.
state-server — Go backend that owns entities, transactions, real-time sync.
avvy-worker — async pipeline for 3D model processing (preview, metadata, projection).
avvy-app — React 19 web client; builds and browses branes.
avvy-engine — Three.js + WASM rendering library used by the web client.
Asset pipeline — view-handlers, graphic-engine, texture compression, UCS family.
Storage — avvy/storage backend for object/asset persistence.
Auth + Identity — JWT + L1-attached users via auth_backend; SHA3 utilities.
Infrastructure — ArgoCD, Rancher autoscaler, monitoring, load-testing, TURN proxy.
See Architecture → Overview for the service map and data-flow diagram.
Product — vision, concepts, user journeys, domains.
Architecture — system map and per-service deep dives.
API — REST, WebSocket, CBOR, signed callbacks, JS SDK.
Operations — deployment, MongoDB, Redis, observability, load testing.
Financial Architecture — wallet, billing, entitlements (design only; figures redacted).
Development — repo conventions, coding standards, testing, release process.
Releases — public release notes index.