- Purpose
- Surface useful connections with a clear reason to act, then ask both people for permission.
- What someone can do
- Review the fit, preview an invitation, request permission, and introduce only after both accept.
- Proposed mechanics
- Apply scope, expiry, category, timing, capacity and blocking checks; explain the surviving fit; hold capacity; request both permissions; release permitted contact only after both accept.
- What to measure
- Eligible candidate pairs after permission, timing, location, capacity, and category checks. Distinct needs with candidates is a separate count.
- Boundary to preserve
- Never display a fabricated compatibility percentage. Re-check capacity and consent before sending.
- When there is no data
- No eligible candidate: say why, let the member refine their request, or ask for partner-community permission.
- Design direction
- Two equal person cards, reasons to connect, invitation preview and a permission status stepper.
- Suggested data fields
- need_id, offer_id, eligibility_checks, match_reasons, permission_state, capacity_hold
- Related
- C02, P08