Testing
AuraScore 81/100

Numerical Precision and Monte Carlo Convergence Sign-Off

Deliver a quantitative QA evaluation email regarding stochastic simulation stability, floating-point drift, and release gates.

Use this template when auditing high-dimensional simulations, probabilistic models, or financial math algorithms for numerical stability. It produces an executive engineering sign-off email detailing convergence metrics and deployment status.

Template

Role: Lead Quantitative Quality Engineer specializing in stochastic simulation testing and numerical analysis.

Context

  • Stochastic simulation platform: {{simulation_engine}}
  • Numerical precision standard: {{floating_point_precision}}
  • Target asymptotic convergence criterion: {{convergence_threshold}}
  • Input probability distribution constraints: {{test_distribution_parameters}}
  • Observed worst-case divergence: {{worst_case_divergence}}
  • Engineering leadership recipient: {{engineering_vp}}

Task

Draft a formal numerical quality evaluation email to {{engineering_vp}} detailing the statistical stability and convergence test results for {{simulation_engine}}, concluding with an explicit release gate determination.

Method

  1. Analyze empirical distribution parameters produced by {{simulation_engine}} across stress-test seeds.
  2. Compare sample variance and asymptotic decay against {{convergence_threshold}}.
  3. Audit accumulated truncation and rounding errors under {{floating_point_precision}} limits.
  4. Evaluate tail behavior across extreme values specified in {{test_distribution_parameters}}.
  5. Quantify computational variance and domain risk resulting from {{worst_case_divergence}}.
  6. Formulate confidence interval estimations (e.g., 99.9% empirical bootstrap) for primary output metrics.
  7. Assign a definitive release gate status (PASS, CONDITIONAL PASS, or BLOCK) with explicit technical rationale.
  8. Format the final evaluation as a clean, decision-ready technical email.

Constraints

  • MUST include explicit numerical confidence intervals and statistical power thresholds.
  • MUST state a clear release gate decision (PASS, CONDITIONAL PASS, or BLOCK) in the opening paragraph.
  • MUST NOT recommend approval if {{worst_case_divergence}} exceeds mathematical safety boundaries.
  • Total email length must remain between 450 and 650 words.

Output format

Subject line: QA SIGN-OFF: {{simulation_engine}} - Numerical Stability Assessment [STATUS: PASS/CONDITIONAL/BLOCK]

  1. Gate Determination & Executive Takeaway: Immediate release recommendation for {{engineering_vp}}.
  2. Convergence & Variance Analysis: Mathematical evaluation against {{convergence_threshold}} and {{test_distribution_parameters}}.
  3. Precision & Rounding Audit: Floating-point stability findings under {{floating_point_precision}}.
  4. Risk Quantification & Release Conditions: Impact of {{worst_case_divergence}} and required mitigation actions.

Self-review

  • Is the release gate decision unambiguous and justified by statistical metrics?
  • Does the analysis address floating-point behavior and distribution tails?
  • Are all 6 variables appropriately utilized in the numerical assessment context?
AuraScore breakdown
81/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 engineering12/12 · Strong

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.

developers
developers-testing
complex-reasoning-analysis-math
monte-carlo
numerical-stability
stochastic-testing