Anomalous Result Investigation Chain

validated scientific chain v1.0.0 cc-by-sa

Block ID: 12a9c33f-6c71-4d70-85ae-3b8feb48e5a0

Community-contributed block. PromptDNA makes no guarantee of output quality or fitness for purpose. User assumes all responsibility for use.

Template

Investigate the unexpected result described in {anomaly_context} before either celebrating or discarding it. Work in order of prior probability: (1) Reproduce first: does the anomaly recur on rerun with nothing changed? A one-off that vanishes is noted and monitored, not chased. (2) Audit the mundane failure modes, which explain most anomalies: calculation errors (redo independently), unit and transcription mistakes, instrument calibration drift (check against a known standard), contamination, reagent age or lot changes, environmental shifts (temperature, humidity, vibration), and software or configuration changes since the last normal result. (3) Check the protocol: was anything done differently, however trivial — different operator, different time of day, different consumable batch? (4) Isolate variables: change one suspected factor at a time back toward the last-known-good configuration until the anomaly appears or disappears. (5) Only after steps 1–4 fail to explain it, treat the result as possibly real: design the controlled test that would confirm it and predict what else must be true if it is. (6) Document everything either way — excluded explanations are the record that makes a real discovery credible.

Investigate the unexpected result described in {anomaly_context} before either celebrating or discarding it. Work in order of prior probability: (1) Reproduce first: does the anomaly recur on rerun with nothing changed? A one-off that vanishes is noted and monitored, not chased. (2) Audit the mundane failure modes, which explain most anomalies: calculation errors (redo independently), unit and transcription mistakes, instrument calibration drift (check against a known standard), contamination, reagent age or lot changes, environmental shifts (temperature, humidity, vibration), and software or configuration changes since the last normal result. (3) Check the protocol: was anything done differently, however trivial — different operator, different time of day, different consumable batch? (4) Isolate variables: change one suspected factor at a time back toward the last-known-good configuration until the anomaly appears or disappears. (5) Only after steps 1–4 fail to explain it, treat the result as possibly real: design the controlled test that would confirm it and predict what else must be true if it is. (6) Document everything either way — excluded explanations are the record that makes a real discovery credible.

Variables

Name	Type	Required	Trust level
anomaly_context		yes

troubleshootinganomaly-investigationlab-practicechain-of-thought

Ratings

0.0

Overall (0)

0.0

Accuracy

0.0

Consistency

0.0

Clarity

0.0

Efficiency

Benchmarks

Not yet self-validated against any benchmark. Automated, evaluative only - not a factor in whether this block was published.

Submitted by James P FounderMod via mcp · 2026-07-18