Tural Gulmammadov

Use when the user wants to "interpret results", "explain the solution", "what does this mean", "translate to business language", "present findings", "sensitivity analysis", "what-if analysis", "how robust is this", "visualize the result", "make a recommendation", or needs to translate a mathematical solution back into real-world meaning, actionable insights, and stakeholder-ready communication. The final skill in the /uber-model → /uber-solve → /uber-interpret trilogy.

Use when the user wants to "model a problem", "translate to math", "formalize a problem", "mathematical modeling", "how to model this", "set up the math", "define the problem", "what kind of problem is this", or discusses translating real-world problems into formal mathematical structures. Covers any computational domain — discrete, continuous, statistical, or hybrid.

Use when the user presents a real-world problem and wants end-to-end help: "solve this problem", "help me figure this out", "model and solve", "full analysis", "what's the answer and what does it mean", or any problem that benefits from the complete Model → Solve → Interpret pipeline. Orchestrates /uber-model, /uber-solve, and /uber-interpret as a single unified workflow.

Use when the user wants to "solve a model", "run the algorithm", "compute the solution", "find the optimal", "prove this theorem", "implement the solver", "solve this problem", "what algorithm should I use", "optimize this", "find the answer", or needs to execute a mathematical solution with computational rigor. This is the solving engine for models produced by /uber-model.