Summary: Table of contents for the technical intelligence layer. Sources: initial architecture; reorganized into guides and legacy folders on 2026-11-09 Last updated: 2026-11-09
Technical Intelligence
This layer covers every repo, shared package, piece of infrastructure, and cross-repo integration pattern in the 7Mind system. Agents should read their own repo note before any significant task, and consult integration notes when a change spans multiple repos.
Since 2026-09-14 7Mind runs on the Gymondo (7NXT) platform. The Elixir backend no longer serves clients. Start with platform-unification and gymondo-platform for anything backend-related. Pages about the pre-migration stack live in the Legacy section at the end.
Repos
One file per repository. Named to match the GitHub repo slug exactly.
Current:
- 7mind-mobile-apps-monorepo — iOS/Android 7Mind app (Flutter monorepo)
- function-sevenmind-legacy-gateway — Go Lambda (Gymondo-git) that answers the 7Mind API on
magic.7mind.*from Gymondo services; the backend as clients see it - website-next-js — 7Mind marketing website (Next.js static export on Cloudflare Pages)
- frontend-public-pages — Gymondo’s shared login, signup and checkout web app, serving 7Mind on
app.7mind.* - api-contracts — TypeSpec contracts of the 7Mind API (unchanged on
mainsince 2026-07-23; the gateway README is the current endpoint list) - pulse-app — Gymondo’s white-label React Native + Expo app (Gymondo, Buddyfit); since 2026-11-10 also the intended home of the 7Mind React Native app (
apps/sevenmind, sibling app)
Legacy:
- elixir-backend — former primary API (Elixir/Phoenix on GKE); now only the content catalogue builder, the parity-test reference for content, and leftover GCP workloads
- nuxt-website — former marketing site and web app (Nuxt SSR), replaced by website-next-js; scaled to zero in October 2026
Add additional repo notes here as they are created.
Guides
Step-by-step runbooks.
- adding-an-app-store-sku — create a new 7Mind app subscription SKU across the stores, Contentful, Gymondo and the app; how to change a live SKU (a new plan)
- adding-a-web-sku — create a new 7Mind web plan, discount voucher, insurance partner (insurance number or voucher code) or paid prevention course across Contentful, the Back Office, the gateway and Storyblok
Projects
Time-bound efforts with their own folder, updated while they run.
- react-native-migration-index — moving the 7Mind app from Flutter to React Native, as a sibling app inside the Gymondo app’s monorepo (pulse-app): goal and architecture, dependency mapping, what is not migrated, Flutter inventory, risks, plan, decision log
Shared NPM Packages
- (none documented yet — add pkg-*.md files as packages are catalogued)
Infrastructure
- infra-overview — high-level system topology (Cloudflare, AWS via Gymondo, legacy GCP), hostname table
- google-cloud — legacy GCP footprint and what still runs there, including the live
rs.7mind.deRudderStack proxy that blocks switching off GKE - cloudflare — DNS zones, routing rules, Workers, Pages
- github-actions — pipeline topology, deploy flows, secrets conventions
- terraform — the three Terraform locations (legacy
sevenmind/infrastructure, the backend repo’s ownterraform/,Gymondo-git/terraform) and the DNS drift warning - test-accounts — shared staging login accounts for manual testing and bug repros
Concepts
System-wide architectural patterns and service configurations that span multiple repos or require cross-cutting context. Read these before editing code that touches the named concern.
- gymondo-platform — the 7NXT/Gymondo platform 7Mind runs on: AWS, CloudFront, Kong, Lambdas, multi-tenancy by vendor
- gymondo-sso-auth — Cognito SSO, Kong token handling, the numeric user id and
legacyUuid - subscription-billing — store in-app purchases, Adyen web checkout, legacy Chargebee and FastSpring shadow subscriptions
- app-subscription-products — how a 7Mind app SKU is wired: store product, Contentful Product, role and tier card, the
productsConfig.jsonallow-list, the app’s catalog-driven paywall, and how a purchase becomes premium (with diagrams) - typespec-contracts — TypeSpec-authored API contracts, OpenAPI emit, Redoc publishing pipeline
- api-versioning-headers — version negotiation via
user-agentandacceptheaders across all clients - mobile-deep-linking — URL schemes, magic login links, Adjust shortlink resolution, Aury webview route alias
- mobile-analytics-stack — Rudderstack / Adjust / Braze (including feature flags) / Sentry / ConfigCat on the mobile app
- aury-companion — the Aury AI chat companion users see as “Seven”: session flow, access rules, the Braze rollout flag
- storyblok-cms — headless CMS behind the marketing pages, magazin and dynamic routes of the Next.js site, rendered at build time
Integrations
Cross-repo connection patterns. Add notes here when a multi-repo interface is non-obvious.
- platform-unification — the 2026 migration from the Elixir backend to the Gymondo platform: timeline, what moved where, what still runs on GCP, gotchas
- mobile-build-pipeline — Codemagic owns mobile production builds, GitHub Actions handles CI and releases
- locale-aware-slugs-static-export — replicating Nuxt’s
nuxtI18n.pathsper-locale URL slugs in a Next.js Pages-Router static export (website-next-js port) - static-export-i18n-catalogue — loading the 450 KB locale catalogue at build time and keeping it out of the client bundle; distributing slices via getStaticProps + a React context (website-next-js port)
Legacy
Concepts and integrations of systems that no longer serve 7Mind users, kept for history and for reading old code. Each page opens with a banner saying what replaced it.
- modulith-domain-model — domain isolation inside the Elixir backend
- dual-brand-routing — how the Elixir backend served 7Mind and 7Sleep (7Sleep API answers 410 since 2026-10-06)
- supertokens-auth — auth on the old stack; SuperTokens only served 7Sleep
- chargebee-billing — Chargebee billing, retired 2026-09-14
- backend-event-bus — Google Pub/Sub + Broadway inside the Elixir backend; replaced by SNS/SQS on the Gymondo platform
- multi-domain-hostname-rewriting — how the Nuxt SSR build served
7mind.de/6mind.de/8mind.de/9mindfrom one image - theme-build-multiplexing —
THEMEbuild arg producing separate 7Mind/7Sleep Nuxt images