Operator-ready prompt for reuse, tuning, and workspace runs.
This item is set up for developers who want to inspect the original language, fork it into Workspace, and adapt the evidence model without losing the source prompt structure.
Implementation handoffs, eval setup, and prompt tuning where you need the original structure intact.
Inspect first, copy once, then fork into Workspace when you want variants, notes, and model settings attached to the same run.
Swap domain facts, examples, and any hard-coded entities for your own context.
Tighten the evidence or verification requirement if this is headed toward production.
Decide which failure mode you want to evaluate first before you branch the prompt.
This prompt already carries implementation detail, tool context, and a final-output instruction. Keep that structure intact when you tune it, or your comparison runs get noisy fast.
Open this prompt inside Workspace when you want a live iteration loop.
Copy for quick reuse, or run it in Workspace to keep prompt variants, model settings, and prompt-history changes in one place.
Structured source with 1 active lines to adapt.
Already linked to a challenge workflow.
Sign in to keep private prompt variations.
Prompt content
Original prompt text with formatting preserved for inspection and clean copy.
Design a simplified A2A protocol for coordinating two distinct robotaxi fleets (e.g., simulated Waymo and Baidu) and a central city traffic coordinator agent. Specify the message types (e.g., 'route_request', 'congestion_alert', 'reroute_suggestion'), data payloads (e.g., vehicle ID, current location, destination, estimated time), and communication channels. Detail how routing conflicts between fleets will be communicated and resolved through this protocol.
Adaptation plan
Keep the source stable, then branch your edits in a predictable order so the next prompt run is easier to evaluate.
Preserve the role framing, objective, and reporting structure so comparison runs stay coherent.
Swap in your own domain constraints, anomaly thresholds, and examples before you branch variants.
Check whether the prompt asks for the right evidence, confidence signal, and escalation path.
Copy once for a pristine source snapshot, then move the prompt into Workspace when you want variants, run history, and side-by-side tuning without losing the original.
Prompt diagnostics
Quick signals for how structured this prompt already is and where adaptation work is likely to happen first.
This prompt is mostly narrative and instruction-driven, so you can adapt examples and output constraints first without disturbing the structure.
Multi-Agent Protocol for Smart City Robotaxi Coordination
This challenge focuses on designing a multi-agent system for smart city traffic management. You will build an A2A protocol-enabled system using Langroid agents powered by DeepSeek to coordinate different robotaxi fleets. The system must optimize traffic flow, dynamically re-route vehicles, and resolve conflicts by leveraging real-time traffic data, extended thinking for predictive routing, and few-shot learning to adapt to evolving urban conditions. Emphasis will be placed on seamless inter-fleet cooperation and robust decision-making in a complex, dynamic environment. This project requires implementing sophisticated agent communication and autonomous reasoning. You will integrate MCP tools for real-time urban data streams and orchestrate large-scale agent deployments using OpenAI Swarm, pushing the envelope for urban mobility solutions.
Use the challenge page to recover the original task boundaries before you tune the prompt. That keeps your variants grounded in the same evaluation target instead of drifting into a different problem.