04 /Journey
Inquiry → proposal → booking
The same journey, viewed from three roles. This is where matching output meets trust, permissions, and business workflow — the part a bare ranking algorithm never has to solve.
Synthetic data, safe demo mode. Every tutor and student here is invented for this benchmark — no real people, no real bookings, no real payments, no external side effects. Ranking runs entirely in your browser against committed fixtures. The runnable harness lives in
benchmarks/edumatch.01 /Multi-role
Walk the journey
Safe demo mode — no real booking or payment
01Inquiry — Student describes their need (subject, level, availability).
02Proposal — A matched tutor sends a proposal: rate, plan, and time slot.
03Booking — Student accepts the proposal and the session is booked.
04Session logged — Booking appears on every role's dashboard and in the audit trail.
02 /Why it matters
Trust, not just ranking
Trusts that a recommended tutor is genuinely qualified and available — not just highly rated.
Trusts that proposals reach students whose needs they can actually meet, and that ratings reflect real match quality.
Needs visibility into every booking and a way to intervene — the flag action here stands in for a real trust & safety workflow.