1. Home — what this wiki is and how to navigate it.
2. Avvyland zone home — the platform's purpose and shape.
3. Vision — platform vision verbatim from APP_DESCRIPTION.md.
4. Concepts — domain entities as defined in current code.
5. Glossary — verified vocabulary.
6. Architecture Overview — service map, data flow, where each repo sits.
7. Deployed Services — what actually runs in production, per the ArgoCD repo.
Backend engineer. Read state-server architecture, then REST API and WebSocket protocol. Skim signed callbacks to understand the worker integration.
Worker / pipeline engineer. Read avvy-worker architecture and signed callbacks. Then Projection model SOP for the manual-review gate.
Frontend engineer. Read avvy-app architecture, avvy-engine architecture, then the JS SDK.
SRE / DevOps. Read Deployed Services (the truth of what's running) and the Operations index: Deployment, Persistence Layer, Redis queue, Observability, Load testing.
Product / partner. Read Vision and Concepts. Product/user-journey/legal-surface framings are out of scope on this wiki until canonical sources land in the live state-server repo.
1. Clone the relevant repos from gitlab.avvyland.com/avvy — see Repo Catalog for the curated index of active projects.
2. Follow each repo's README for local setup. For state-server, external/mongo/docker-compose bootstraps a single-member replica set sufficient for local dev (production uses FoundationDB — see Persistence Layer).
3. Build, test, vet (Go) and lint (JS/TS) as documented in each repo's CLAUDE.md / README.md.
This wiki captures final-state design. The active backlog lives in Jira — see External Links for project keys (AL, AVARCH, DOM) and access notes.