Track 04 · World Tennis — Player and club coordination
Track name on your submission: Player and club coordination
Build an Omega assistant that finds a player the right opponent, court and time, resolves the clash, and asks before it books.
Who you are building for
WorldTennis.app is a verified tennis platform. ID-verified players, coaches, courts and referees are matched by skill level, availability and location. Players find opponents and doubles partners, book courts and track results in one app instead of ten. The idea behind it: your tennis, your data.
The problem
Today a match takes a dozen messages across group chats, a separate booking app, and guesswork about whether the other player is at your level. Players coming from different countries use different rating systems. Courts sit empty in hours nobody can see.
Your build
An Omega assistant for one focused workflow. The suggested one: match available players to a suitable court and time. It:
- reads player profiles: level, availability, location, preferences
- reads court availability
- proposes a match with its reasons
- resolves a scheduling conflict
- asks both players to confirm before a simulated booking
What Omega does here
| Role | Match coordinator that proposes, negotiates a clash, and confirms. |
| Memory and reasoning | Remembers player preferences and past matches; uses MeTTa rules for level fit, travel distance and availability overlap. |
| Tools | Sample player profiles, sample court availability, a simulated booking step. |
Demo script (3 minutes)
- A player asks for a match this week.
- The agent proposes an opponent, court and time, with reasons: level, distance, shared availability.
- Introduce a conflict, such as the court being taken or one player becoming unavailable. Show the agent re-plan.
- Both players confirm. The agent makes a clearly labelled simulated booking.
Showcase checklist
- A proposed match with visible reasons
- A scheduling conflict resolved
- Confirmation requested before booking
- Simulated bookings and payments clearly labelled
Boundaries
Use sample player profiles and court availability only. No real player data. Bookings and payments are simulated and must be labelled as such.
Stretch ideas
Doubles matching for four players; translating between rating systems; filling a club's empty court hours.
Best for
Builders who want a clear, visual consumer demo.
The rules apply to every track
Entry rules, deadlines, judging weights and boundaries are in the buildathon brief.

Dev LMS