This zone documents the state-server platform — a Go backend for managing interactive 3D scenes with real-time collaboration and e-commerce capabilities — and the services that run with it (avvy-worker, avvy-app, avvy-landing, contask, content-processor, texture-converter, webapp).
Wording above is sourced from state-server/docs/APP_DESCRIPTION.md and state-server/STATE_SERVER_COMPREHENSIVE_DESCRIPTION.md.
The frontend client is called Avvy (avvy-app). The worker is avvy-worker.
These are the entities defined in the state-server codebase (internal/domain/entity/) and listed in STATE_SERVER_COMPREHENSIVE_DESCRIPTION.md:
User — authentication, profile, inventory ownership.
Object — umbrella term for any 3D entity (the ObjectBase interface in code).
Group — container holding child objects and a gallery of prototypes.
Block — leaf 3D object with a model, transform, properties.
Prototype — versioned template defining default object properties and handlers.
Brane — a root scene, implemented as a Group with IsBrane: true. Not a separate type.
Interface — interaction / connection slot (9-direction grid) on a spatial cell.
Handler — server-side JavaScript (Otto VM) attached to a prototype.
Spatial primitives backing 3D queries:
Blockcell, Spacecell, SpatialKey, and Space — the last is a Go type alias map[SpatialKey]SpacecellBase used for spatial indexing, not a top-level container.
Source: state-server/internal/domain/entity/types.go (entity interfaces), objects.go (Group / Block / IsBrane), STATE_SERVER_COMPREHENSIVE_DESCRIPTION.md §4.
state-server — Go backend; owns Users, Branes, Objects, Prototypes, Handlers; CBOR over HTTPS + WebSocket.
avvy-worker — async pipeline for 3D model processing (preview, projection, canonical GLB).
avvy-app — React web client; bundles avvy-engine for rendering.
avvy-engine — Three.js + AssemblyScript/WASM rendering library.
Deployed services — every service currently running in the production Kubernetes cluster, sourced from the ArgoCD repo.
See Architecture → Overview for the data-flow diagram.
Architecture — system map and per-service deep dives.
API — REST, WebSocket, CBOR, signed callbacks, JS SDK.
Operations — deployment, persistence layer, Redis queue, observability, load testing.
Financial Model — R0 Soft Financial (implemented on a feature branch, awaiting merge) vs the simple credit ledger that runs on dev today.
Releases — public release notes index.
Vision — platform vision from APP_DESCRIPTION.md.
Concepts — domain entities as they exist in the current code and docs.
state-server/docs/APP_DESCRIPTION.md, state-server/STATE_SERVER_COMPREHENSIVE_DESCRIPTION.md, state-server/internal/domain/entity/types.go, state-server/internal/domain/entity/objects.go.