This wiki captures final-state design and reference. Active work — backlog, in-flight tickets, design discussions, decision logs — lives in the systems below. Pages on this wiki link out; they do not mirror.
Host. avvy.atlassian.net.
Projects.
AL — AvvyLandNext. Active product backlog.AVARCH — AvvyLand_ARCH. Historical architectural records (largely closed).DOM — DomiDo 2.0. Manufacturing / construction epics.Access. Use the credentialed access documented in your local memory. The MCP Jira tool routes to a different instance — for avvy.atlassian.net use direct REST API v3 over curl with the user-scoped API token.
Host. gitlab.avvyland.com.
Groups.
avvy (id 18) — the Avvyland platform. ~80 projects; see Repo Catalog for the curated index.domido (id 3) — DomiDo v1.domido-v2 (id 1294) — DomiDo v2.Access. SSH on port 22 via the platform's GitLab. The MCP GitLab tool is configured against a different instance — for gitlab.avvyland.com use direct REST API calls with a personal access token (PRIVATE-TOKEN header).
https://avvyland.com — this site (Wiki.js).gitlab.avvyland.com/avvy/avvy-landing; production hostname per deployment config.gitlab.avvyland.com/avvy/avvyland-website.https://locust.k8s.avvyland.com (Locust harness; internal). See Load Testing.https://grafana.avvyland.com/api/otlp/v1/traces when GRAFANA_OTLP_TOKEN is configured. See Observability.avvy group description; it is not maintained and is not mirrored here.pivot 1.0/, pivot 1.5/, checkpoint/ in the strategic-docs repo) or in chat. They are intentionally not brought into this wiki — see the "final state only" principle on Home.Repo Catalog for the GitLab index.
Onboarding Reading Order for where to start.