Can computation validate the final scientific claim?

No. A desk review cannot certify manufacturing, field reliability, safety, or regulatory compliance. Computation can prioritize and eliminate directions; final validation remains with the appropriate domain methods and accountable specialists.

When should the project stop or reframe?

Stop or reframe when no plausible outcome changes the allocation decision, critical evidence is unavailable, the thesis depends on untestable assumptions, or a cheaper route dominates on information gained per unit of cost and time.

R&D Decisions

Deep-Tech Technical Due Diligence: Test the Physics Behind the Story

Published 2026-08-22 · Updated 2026-08-22

Answer in brief

Before funding deeper validation, Deep-Tech Technical Due Diligence should resolve which technical assumptions determine feasibility and scale-up risk. The minimum credible analysis compares distinct routes using governing equations, material constraints, energy and mass balances, prototypes, tolerances, and failure modes and attempts to run an order-of-magnitude constraint check before detailed forecasting. The result should name the leading direction, the counterevidence, and the condition that would stop it.

Evidence status: Decision-method guide; not a completed investigation or final validation.

The decision this guide supports

which technical assumptions determine feasibility and scale-up risk

Why the problem is difficult

The article-specific identification challenge is whether the question “which technical assumptions determine feasibility and scale-up risk” can be resolved using governing equations, material constraints, energy and mass balances, prototypes, tolerances, and failure modes, rather than merely restated in new language.

A falsifier-first workflow

Define the decision precisely: which technical assumptions determine feasibility and scale-up risk.
Build a source and data ledger around governing equations, material constraints, energy and mass balances, prototypes, tolerances, and failure modes.
Compare the inherited route with a mechanistically distinct alternative and a constraint-based null.
Actively search for the strongest counterevidence relevant to this decision, including boundary cases and prior failures.
Run the lowest-cost discriminating challenge: run an order-of-magnitude constraint check before detailed forecasting.
Record pursue, reframe, or stop, the confidence level, the evidence ceiling, and who owns downstream validation.

Decision criteria

Decision impact: would the result materially change the choice about which technical assumptions determine feasibility and scale-up risk?
Evidence fit: does the available evidence—governing equations, material constraints, energy and mass balances, prototypes, tolerances, and failure modes—directly address the decision rather than merely correlate with it?
Discrimination: does the preferred route predict an outcome a credible alternative does not?
Robustness: does the ranking survive the challenge “run an order-of-magnitude constraint check before detailed forecasting”?
Validation boundary: is the conclusion no stronger than the available sources, data and computation?

Supporting evidence

governing equations, material constraints, energy and mass balances, prototypes, tolerances, and failure modes

Counterevidence

For this decision, a result from “run an order-of-magnitude constraint check before detailed forecasting” that reverses or flattens the ranking must remain visible even when it is commercially inconvenient.

Computation

Here computation earns its place only if it changes the choice about which technical assumptions determine feasibility and scale-up risk or exposes why the available evidence cannot resolve it.

Fastest falsifier

run an order-of-magnitude constraint check before detailed forecasting

When to stop or reframe

A decision-specific stop trigger is failure of the challenge “run an order-of-magnitude constraint check before detailed forecasting” without an independently supported alternative mechanism.

Evidence ceiling

A desk review cannot certify manufacturing, field reliability, safety, or regulatory compliance.

Sources and starting points

NASA Systems Engineering Handbook — Official systems-engineering guidance on requirements, verification, risk, and technical decisions.
NIST: Guidelines for Evaluating and Expressing Measurement Uncertainty — A reference for uncertainty-aware decision records.
GAO Technology Readiness Assessment Guide — Additional authoritative starting point selected for this decision area; applicability must be checked against the precise question.
NIST Data Repository — Additional authoritative starting point selected for this decision area; applicability must be checked against the precise question.

Continue the decision journey

Explore the full topic hub · Editorial standard · Scientific Oracle consulting

Frequently asked questions

What decision does “Deep-Tech Technical Due Diligence: Test the Physics Behind the Story” help make?: It supports a bounded decision about which technical assumptions determine feasibility and scale-up risk. The framework keeps alternatives, evidence, counterevidence, uncertainty, and the fastest falsification test visible.
What is the fastest useful test?: run an order-of-magnitude constraint check before detailed forecasting
Can computation validate the final scientific claim?: No. A desk review cannot certify manufacturing, field reliability, safety, or regulatory compliance. Computation can prioritize and eliminate directions; final validation remains with the appropriate domain methods and accountable specialists.
When should the project stop or reframe?: Stop or reframe when no plausible outcome changes the allocation decision, critical evidence is unavailable, the thesis depends on untestable assumptions, or a cheaper route dominates on information gained per unit of cost and time.