7Mind Brain

aury-companion

2 min read

Summary: “Aury” refers to two distinct things in the 7Mind system. The mobile app has an Aury AI chat companion gated by feature flag and A/B test. The backend has an Aury B2B2C partner integration with API credentials. Whether they are the same Aury is TBD. Sources: direct code inspection (lib/features/ai_companion/, lib/features/core/data/services/analytics/ai_companion_analytics.dart, lib/features/core/data/services/configuration/feature_flags.dart, lib/features/core/data/services/configuration/a_b_tests.dart in 7mind-mobile-apps-monorepo; lib/backend/external/aury/ in elixir-backend) Last updated: 2026-05-15

The two Aurys

1. Mobile in-app AI companion

Lives in lib/features/ai_companion/ in 7mind-mobile-apps-monorepo. A chat surface added to the home screen.

  • Gated by: ConfigCat flag isAuryEnabled and Amplitude Experiment aury-experiment (see mobile-analytics-stack)
  • Locale-restricted: only enabled when isAuryEnabled && isAppInGerman (home screen guard)
  • Analytics: dedicated helpers in lib/features/core/data/services/analytics/ai_companion_analytics.dart (trackAuryChatOpened, trackAuryChatClosed, trackAuryConsentGiven, …)
  • Deep links from Aury webview: route alias /courseDetail exists because the webview emits the singular spelling (see mobile-deep-linking)

2. Backend B2B2C partner integration

Listed in elixir-backend dependencies as “Aury — B2B2C partner integration (base URL + API key + partner ID)“. Used for partner-provisioned access and content delivery to corporate / health-insurer cohorts.

How they relate

TBD. From code inspection alone, it is not possible to confirm whether the mobile AI companion and the backend B2B2C partner share a vendor, an API, or only a name. A new agent should not assume one or the other. Confirm with the team before designing changes that touch “Aury” in general.

What is known:

  • Both surfaces use the spelling “Aury”
  • The mobile-side webview does open inside the 7Mind app and emits deep links back into it (the /courseDetail alias is direct evidence)
  • The backend has Aury env vars suggesting a server-to-server integration that is separate from any mobile-only chat SDK

What agents should know

  • Do not flatten “Aury” into a single concept when writing code or docs. Always specify which Aury (in-app companion vs B2B2C partner) is meant.
  • The mobile Aury feature is German-locale-only and flag-gated. Do not assume it is shipping to all users.
  • If a deep link arrives with the path /courseDetail (singular), the source is the Aury webview. Do not refactor it away.
  • For the backend Aury integration env vars and call patterns, see elixir-backend.

Graph View

Backlinks