Challenge 2

bySoban

Challenge 2: AI Service Orchestrator for Informal Economy Challenge Overview Informal economy, including plumbers, electricians, tutors, beauticians, and home service providers, operates largely through: ● WhatsApp messages ● phone calls ● informal referrals This results in: ● inefficient service matching ● missed opportunities ● lack of automation ● poor user experience At the same time, users struggle to find: ● reliable services quickly ● availability in real time ● trusted providers nearby Problem Statement Build an Agentic AI System that automates the end-to-end lifecycle of a service request — from user intent to booking and follow-up. Your system must: 1. Understand user service requests (in natural language) 2. Identify relevant providers using location/context 3. Select or recommend the best provider 4. Simulate booking and confirmation 5. Handle follow-up interactions 6. Show complete reasoning and workflow execution Mandatory Requirement: Google Antigravity Teams MUST use Google Antigravity as the core platform to: ● orchestrate agent workflows ● manage multi-step reasoning ● integrate tools (Maps, Search, APIs) ● execute actions (booking, notifications, etc.) Use of external LLMs is allowed, but Antigravity must be central to system logic and orchestration. Example User Scenario User input (Roman Urdu / Urdu / English): “Mujhe kal subah G-13 mein AC technician chahiye” Expected Output Service Request: AC Technician Location: G-13 Time: Tomorrow morning Recommended Provider: Ali AC Services (2.1 km away) Reasoning: Closest available provider with high rating Simulated Booking: - Slot booked: 10:00 AM - Confirmation sent Follow-up: Reminder scheduled 1 hour before appointment System Requirements 1. Intent Understanding ● Process natural language input ● Support: § Urdu § Roman Urdu § English ● Extract: § service type § location § time 2. Provider Discovery ● Use: § mock dataset OR § Google Maps / Places APIs ● Identify: § nearby providers § service category match 3. Matching & Ranking ● Rank providers based on: § distance § availability § rating (simulated or real) ● Provide clear reasoning for selection 4. Decision & Recommendation ● Select best provider OR show top options ● Explain decision in simple terms 5. Action Simulation (CRITICAL REQUIREMENT) System must simulate: ● booking confirmation ● provider assignment ● scheduling Simulation can include: ● updating a mock booking system ● creating a confirmation message ● writing to a database/spreadsheet ● generating a booking receipt 6. Follow-Up Automation ● Simulate: § reminders § status updates § completion confirmation 7. Agentic Workflow (MANDATORY) System must demonstrate: ● multiple agents OR structured reasoning pipeline ● planning → decision → action → follow-up ● traceable logs of: § decisions § tool usage § action execution Deliverables 1. Working Prototype with Mobile App (MUST) and Web App (Optional) 2. Demo Video (3–5 minutes) Must clearly show: ● user input ● system understanding ● provider matching ● booking simulation ● follow-up workflow 3. Agent Trace / Logs ● reasoning steps ● agent interactions ● action execution logs 4. Documentation (README) Include: ● system architecture ● how Antigravity is used ● APIs/tools used ● assumptions and limitations Evaluation Criteria 1. Use of Google Antigravity — 25% ● Core orchestration handled via Antigravity ● Effective use of tools (Maps, APIs) ● Demonstrates planning + execution 2. Agentic Reasoning & Workflow — 20% ● Multi-step reasoning ● Logical flow from request → decision → action ● Evidence of autonomy 3. Matching Quality & Decision Logic — 20% ● Relevant provider selection ● Clear ranking criteria ● Strong reasoning behind decisions 4. Action Simulation & Execution — 15% ● Booking process realistically simulated ● Clear system state change (confirmation, scheduling) ● End-to-end workflow demonstrated 5. Technical Implementation — 10% ● Clean architecture ● API/tool integration ● Robust handling of edge cases 6. Innovation & UX — 10% ● Creative approach ● Intuitive interface ● Clear and engaging demo Important Guidelines ● This is NOT a simple listing or booking app ● Focus on agentic automation, not UI complexity ● At least one booking must be simulated end-to-end ● Must demonstrate reasoning + decision-making ● Use mock data if real APIs are unavailable ● Avoid use of real personal/sensitive data

LandingProviders
Landing

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirement Document

Challenge 2: AI Service Orchestrator for Informal Economy

Introduction

The "Challenge 2: AI Service Orchestrator for Informal Economy" project aims to automate the end-to-end lifecycle of service requests within the informal economy. This includes sectors such as electricians, plumbers, AC technicians, beauticians, tutors, and mobile repair services. The system will leverage Google Antigravity for orchestrating workflows and managing multi-step reasoning to improve service matching, booking, and follow-up processes.

System Overview

The system is designed to address inefficiencies in the informal economy by automating service requests from user intent to booking and follow-up. It will process natural language inputs in Urdu, Roman Urdu, and English, identify relevant service providers, simulate bookings, and automate follow-up interactions. The core platform for orchestration will be Google Antigravity, ensuring robust integration and execution.

Page 1 of 5

Functional Requirements

  • As a User, I should be able to request services like Electrician, Plumber, AC Technician, Beautician, Tutor, and Mobile Repair.
  • As a User, I should be able to input requests in Urdu, Roman Urdu, or English.
  • As a System, I should normalize user inputs for consistent processing.
  • As a System, I should extract intent and validate entities from user inputs.
  • As a System, I should match users with the best service providers based on location, availability, and ratings.
  • As a System, I should simulate booking confirmations and provider assignments.
  • As a System, I should automate follow-up reminders and status updates.

User Personas

  • User: Individuals seeking services like electricians, plumbers, etc.
  • Service Provider: Professionals offering services in the informal economy.
  • System Admin: Oversees system operations and manages provider data.
Page 2 of 5

Visuals Colors and Theme

  • primary: #1E3A8A (Deep Blue)
  • primary_light: #3B82F6 (Sky Blue)
  • secondary: #F97316 (Vibrant Orange)
  • accent: #10B981 (Emerald Green)
  • highlight: #F59E0B (Amber)
  • bg: #F3F4F6 (Light Gray)
  • surface: rgba(255, 255, 255, 0.9) (White)
  • text: #111827 (Dark Gray)
  • text_muted: #6B7280 (Muted Gray)
  • border: rgba(209, 213, 219, 0.5) (Light Gray)

Signature Design Concept

Interactive Service Map: The homepage will feature an interactive map where users can see available service providers in their vicinity. Using @react-three/fiber and @react-three/drei, the map will allow users to zoom in on specific areas, click on provider icons to view details, and drag the map to explore different locations. Providers will be represented as dynamic icons that animate when hovered over, providing a lively and engaging experience. The map will also feature a real-time filter to adjust visible providers based on service type and availability.

Page 3 of 5

Interaction Model & Motion Direction

  • Interaction Model: Parallax
    • The landing page will use a parallax effect to create a sense of depth as users scroll through different sections. Background layers will move at varying speeds, enhancing the visual storytelling.
  • Internal Pages: Static
    • Internal pages like dashboards and settings will focus on clarity and minimal motion to ensure quick access to information.

Non-Functional Requirements

  • The system must handle high volumes of service requests efficiently.
  • It should provide real-time updates and notifications to users and providers.
  • The system must ensure data privacy and security, especially for user and provider information.

Tech Stack

  • Frontend: React for Web, React Native for Mobile App
  • Backend: Python, FastAPI
  • Database: MySQL or MariaDB
  • AI Models: GPT 5.4 for user-friendly responses
  • AI Tools: Litellm for LLM Routing
  • Orchestration: Docker, Kubernetes
Page 4 of 5

Assumptions and Constraints

  • The system assumes the availability of Google Antigravity for workflow orchestration.
  • Mock data will be used for provider information if real API data is unavailable.
  • The system will not store personal or sensitive data beyond what is necessary for service matching and booking.

Glossary

  • Google Antigravity: A platform for orchestrating agent workflows and managing multi-step reasoning.
  • LLM: Large Language Model, used for processing natural language inputs.
  • Parallax: A scrolling technique that creates a sense of depth by moving background and foreground elements at different speeds.
Page 5 of 5
Landing design preview
Landing: View Platform
Register: Create Profile
Profile: Set Service Category
Profile: Set Availability
Dashboard: View Incoming Requests
Dashboard: Accept Booking
Booking: View Job Details
Booking: Update Job Status
Tracking: Mark Job Complete
Dashboard: View Earnings
Profile: Manage Availability
Landing design preview
Landing: View Platform
Register: Create Profile
Profile: Set Service Category
Profile: Set Availability
Dashboard: View Incoming Requests
Dashboard: Accept Booking
Booking: View Job Details
Booking: Update Job Status
Tracking: Mark Job Complete
Dashboard: View Earnings
Profile: Manage Availability