Who it serves
Members ready to be found by people walking a similar path.
The experience
Publish a public signal profile when you choose to. AGA's matching engine reads only what you approved, suggests a person with the reason written in plain language, and a connection happens only when both sides say yes — then you share a private room.
Strongest evidence
Opt-in is enforced in SQL, not just UI — matching only ever sees profiles that are public, discoverable, and open to connections, and only signals the person explicitly approved.
For the technically curious
backend/web/matching.py:191 (_eligible_profile — the SQL-enforced triple opt-in)frontend/src/components/ConnectionsPage.jsx (/connections — 'Mutual by design')backend/web/moderation.py (blocking, moderation, appeals)
What we measure
Mutual-connection rate. Suggested pairs where both people accept, divided by pairs where at least one person saw the suggestion.
Definition approved 2026-08-27; decision data exists (match_decisions), not yet surfaced — no live counters in Phase 1
Boundaries — what AGA does not claim
- Nobody appears in matching until they publish a profile and switch on discovery and connections — three separate consents.
- Per-signal visibility: public, connections-only, or private.
- Suggestions arrive only in your inbox on the platform — no push, no emails about people.