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.
Extend your `ZenML` pipeline or add an external service to integrate an AI agent. Simulate an API call to `Grok-2` to perform anomaly detection on the processed quantum experiment metrics, identifying results that deviate significantly from expected performance. Additionally, design a `Smolagents`-like autonomous agent that monitors the queue of submitted experiments, optimizes scheduling, and triggers `Grok-2` analysis upon completion.
Adaptation plan
Keep the source stable, then branch your edits in a predictable order so the next prompt run is easier to evaluate.
Hold the task contract and output shape stable so generated implementations remain comparable.
Update libraries, interfaces, and environment assumptions to match the stack you actually run.
Test failure handling, edge cases, and any code paths that depend on hidden context or secrets.
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.
Design a Secure Decentralized Quantum Experiment Orchestration Platform
This challenge focuses on building a secure, decentralized platform for orchestrating quantum experiments. The platform must enable multiple organizations or research groups to collaboratively define, execute, and analyze quantum circuits on shared or distributed quantum hardware (simulated). Key aspects include robust access control, verifiable logging, secure data sharing, and integrity of experiment results. Participants will implement a prototype that demonstrates secure multi-party access to simulated quantum resources and leverages modern MLOps principles for data processing and AI-driven insights. The solution should address the critical need for trust and data governance in a multi-stakeholder quantum ecosystem. This involves using cryptographic techniques for data integrity and access control, along with AI to streamline experiment workflows and secure aggregation of results.
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.