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.
Prepare the necessary `Seldon Core` deployment configuration (YAML files) to serve your trained anomaly detection model as a real-time inference endpoint on a Kubernetes cluster. Your configuration should define a custom `SeldonDeployment` that incorporates your pre-trained model and the `Featuretools` pipeline for real-time feature extraction. Consider how to pass the raw sensor input to your model and receive anomaly predictions. Provide a Dockerfile if a custom runtime environment is needed beyond standard Seldon wrappers.
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.
Predictive Anomaly Detection for Rocket Boosters
The integrity of next-generation rocket boosters is paramount for mission success and safety. Early detection of anomalies, whether structural, propulsion-related, or systemic, can prevent catastrophic failures. This challenge focuses on building a robust, real-time predictive anomaly detection system for a rocket booster during its pre-flight testing phase, mirroring real-world scenarios like the recent Starship booster incident. Participants will develop an AI model that processes streams of multivariate sensor data (e.g., pressure, temperature, strain, vibration) from a simulated rocket booster. The system should identify subtle deviations from nominal operational parameters that indicate an impending anomaly or failure, long before it becomes critical. The solution will leverage advanced machine learning techniques, including time-series analysis and pattern recognition, to forecast potential issues and provide early warnings to ground control.
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.