Knowledge base
AuraScore 79/100

Algorithmic Simulation Failure Diagnostic Framework

Build a tiered diagnostic framework and troubleshooting taxonomy for numerical instability and simulation errors in computational knowledge bases.

Apply this framework when technical support specialists require a structured knowledge base schema to diagnose and resolve non-deterministic numerical errors, convergence failures, and solver anomalies. It creates clear decision trees and remediation documentation standards.

Template

Role: Lead Support Knowledge Strategist for High-Performance Computational Systems with deep expertise in numerical mathematics.

Context

  • Simulation Environment: {{simulation_platform}}
  • Solver Infrastructure: {{numerical_solver_stack}}
  • Targeted Anomalies: {{failure_class_scope}}
  • Tier Distribution: {{support_escalation_tiers}}
  • Benchmark Suite: {{reproducibility_benchmark}}
  • Revision Governance: {{update_governance_cycle}}

Task

Develop a comprehensive diagnostic troubleshooting framework and knowledge article architecture to empower support engineers to identify, isolate, and remediate numerical stability and solver failures in complex simulation workflows.

Method

  1. Construct a standardized root-cause classification ontology centered on {{failure_class_scope}} and solver failure modes.
  2. Formulate step-by-step diagnostic decision trees mapped directly to the technical capabilities of {{support_escalation_tiers}}.
  3. Design diagnostic article schemas that mandate logging solver settings, tolerance configurations, and conditioning metrics for {{numerical_solver_stack}}.
  4. Define isolation procedures to decouple user-input error from intrinsic solver defects within {{simulation_platform}}.
  5. Establish validation requirements mandating that remediation recipes pass against {{reproducibility_benchmark}} prior to article publication.
  6. Detail actionable mitigation playbooks (e.g., relaxation factor adjustments, preconditioning switches, mesh refinement protocols).
  7. Set forth knowledge deprecation, maintenance, and synchronization protocols aligned with {{update_governance_cycle}}.

Constraints

  • MUST require every diagnostic article to link directly to a verifiable test case in {{reproducibility_benchmark}}.
  • MUST NOT provide generic remediation advice that overlooks the mathematical nuances of {{numerical_solver_stack}}.
  • Ensure operational clarity so lower tiers can efficiently route unresolvable mathematical defects to higher tiers.
  • All error codes and diagnostic telemetry must match standard output formats of {{simulation_platform}}.

Output format

Provide the complete framework structured under these 5 mandatory sections:

  1. Failure Taxonomy & Root-Cause Classification System
  2. Tiered Diagnostic Decision Logic & Routing Matrix
  3. Knowledge Article Template for Numerical Anomalies
  4. Benchmarking & Verification Protocol
  5. Knowledge Base Maintenance & Release-Cycle Governance Format all diagnostic logic with explicit branching conditions and structured tables.

Self-review

  • Are the troubleshooting pathways uniquely calibrated for {{numerical_solver_stack}} and {{simulation_platform}}?
  • Does the framework define unambiguous triage handoffs across {{support_escalation_tiers}}?
  • Are validation criteria tied directly to {{reproducibility_benchmark}}?
AuraScore breakdown
79/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

support-success
support-knowledge-base
complex-reasoning-analysis-math
knowledge-base
computational-math
simulation-support