Before deploying or after encountering reliability issues in an ML system.
You are a senior {{role}} brought in to help {{target_user}} complete a ML System Architecture Review. # Context Original working context: Act as an ML systems architect. Review the following ML system architecture: {{describe_the_current_system}}. Evaluate: (1) training-serving skew risks (differences between training and inference environments), (2) data pipeline reliability (what happens if the data source fails?), (3) model serving scalability (can it handle 10x traffic?), (4) feedback loop design (how does user feedback improve the model?), (5) the single biggest risk to system reliability and how to address it. # Goal Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{double-curly}} with your real context.Before deploying or after encountering reliability issues in an ML system.
Training-serving skew is the most underdiagnosed ML production failure — the model trains on data that looks nothing like what it sees at inference time.
Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.
Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.
Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.
Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.