Strong foundations. Deliberate boundaries.
I used AI-assisted development to build the product. The important work was deciding what the system should know, guarantee, and never assume.
Experience
React · TypeScriptPeople, overlap, circles & plans
Product logic
TanStack server functionsMatching, member actions & verified webhooks
Data & access
Postgres · access policiesProfiles, memberships, messages & payments
Make overlap a data relationship, not an AI verdict.
Interests, intent and life context are explicit signals. Shared-item explanations come from stored answers, so a person can see the actual starting point.
Structured choices miss some nuance. A ranking is a useful introduction—not a prediction of friendship.
- Implemented evidence
- Profile taxonomy → overlap services → connection cards
- Acceptance check / next test
- Can a guest explain what connects them to someone without seeing a score?
My AI thesisAutomate the work around connection—not the human judgment of who deserves one.
Product principle, not a research findingTools accelerate execution. They don’t own the decisions.
Lovable supported the build. Managed infrastructure provides auth and storage; Stripe, Razorpay and messaging integrations appear in the codebase. Their presence is implementation evidence, not a claim that every provider is live or that the entire system has passed a security audit.