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.
Containerize your anomaly detection model, the RAG system, and the GPT-5 integration into a unified service. Use BentoML to package and serve this entire application as a production-ready API endpoint. The service should expose an endpoint (e.g., `/detect_anomalies`) that accepts a time range and returns detected anomalies along with the AI-generated recommendations. Write comprehensive `bentofile.yaml` and `service.py` files to define your Bento.
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 source structure until you know which part of the prompt is actually driving the result quality.
Change domain facts, examples, and tool context first before you rewrite the instruction scaffold.
Validate one failure mode at a time so prompt changes stay attributable instead of getting noisy.
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.
AI-Powered Quantum Link Integrity Monitor
Inspired by advancements in practical quantum networks and noise reduction, this challenge focuses on ensuring the integrity and security of quantum communication links. Participants will develop an AI-driven service to monitor simulated quantum network telemetry (e.g., Quantum Bit Error Rate, entanglement fidelity, photon loss). The system will be tasked with real-time anomaly detection, identifying deviations indicative of environmental noise, tampering, or eavesdropping attempts. The core of the solution involves integrating a machine learning model for anomaly detection with a Large Language Model (LLM) like GPT-5. The LLM, accessed via Fireworks, will leverage a knowledge base built with LlamaIndex and stored in Postgres with pgvector, to provide contextual analysis and actionable mitigation recommendations for detected threats. The entire service must be packaged and deployed as a scalable, production-ready MLOps artifact using BentoML.
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.