Lesson 1: How to Choose a Claim

Module 6 – Capstone Design Biology Audit

Lesson 1: How to Choose a Claim

Your capstone will be a full Design Biology Audit. You will pick one claim, define it clearly, test it against evidence, and write a repeatable evaluation that another person could follow. The quality of your capstone depends on the quality of your claim selection. This lesson shows you how to choose the right claim.

A good claim is not a topic. It is not a field. It is not a general belief. A good claim is a specific statement that can be tested, compared to alternatives, and potentially falsified.

Bad claim: “Evolution is true.” Bad claim: “Design is real.”
Bad claim: “Origin of life happened naturally.”

Those are too broad. They cannot be audited cleanly.

A strong capstone claim is narrow, observable, and operational. It makes a specific assertion about a biological system, a pathway, or an origin mechanism. It points to measurable evidence.

Good claim examples include:

A specific origin-of-life pathway can produce functionally relevant polymers under defined conditions without investigator-imposed selection.
A particular molecular machine can be explained by a stepwise pathway that preserves function at each stage.
A proposed regulatory network can emerge through incremental changes without requiring multiple coordinated features to appear at once.

You do not need to choose a claim you agree with. You need to choose a claim that can be evaluated. Some of the best capstones are neutral in tone. They simply test a claim to see if the evidence supports it.

When selecting a claim, use three filters.

First, clarity.
Can you write the claim in one sentence?
Can you define the key terms?
Can you specify what counts as success and what counts as failure?

Second, evidence access.
Can you find primary sources, data, or reputable summaries?
Can you identify experiments, observations, and controls?
Can you compare different interpretations of the same evidence?

Third, auditability.
Can the claim be tested with severe tests?
Can you define null models and alternatives?
Can you write risky predictions and falsifiers?

If a claim fails any of these filters, it will produce a weak audit.

Next, choose a claim with the proper scope. Your capstone has limited space and time. If your claim requires covering all of genetics, all of evolution, or all of chemistry, it is too big. Pick a claim that fits one system or one proposed pathway.

A helpful approach is to choose a claim that appears in a real paper, a textbook statement, a popular science article, or a common public argument. That gives you a clear target and clear sources.

Once you find a candidate, rewrite it in operational form. Your goal is to remove vague language and replace it with testable terms.

Vague: “This evolved over time.”
Operational: “This function can be produced by this mechanism under these conditions within these constraints, and intermediate stages remain viable.”

The capstone audit is not about rhetorical skill. It is about disciplined evaluation. Your claim must be stable enough to be tested and narrow enough to be examined carefully.

Before you finalize your claim, run it through a final checkpoint.

What system does the claim address?
What function is being asserted?
What mechanism is being proposed?
What evidence would falsify it?

If you can answer those four questions, you have a claim worth auditing.

In the next lesson, you will learn how to use the audit template. You will turn your claim into a structured evaluation with defined steps, controls, alternative explanations, and conclusions grounded in evidence.

Lesson Summary

Module 6 – Capstone Design Biology Audit

Lesson 1: How to Choose a Claim

Your capstone will be a comprehensive Design Biology Audit where you will:

  • Pick one specific claim
  • Clearly define the claim
  • Test the claim against evidence
  • Write a repeatable evaluation for others to follow

The quality of your capstone depends on the quality of your claim selection.

What makes a good claim?

  • A good claim is not a broad topic, field, or general belief.
  • A good claim is a specific, testable, and potentially falsifiable statement.

Examples of poor claims:

  • “Evolution is true.”
  • “Design is real.”
  • “Origin of life happened naturally.”

— These are too broad and cannot be audited effectively.

Characteristics of a strong capstone claim:

  • Narrow, observable, and operational
  • Focus on a biological system, pathway, or origin mechanism
  • Points to measurable evidence

Examples of good claims:

  • A specific origin-of-life pathway can produce functionally relevant polymers under defined conditions without investigator-imposed selection.
  • A particular molecular machine can be explained by a stepwise pathway that preserves function at each stage.
  • A proposed regulatory network can emerge through incremental changes without requiring multiple coordinated features to appear at once.

You do not need to choose a claim you agree with; choose one that can be evaluated objectively, ideally with neutral tone.

Three filters to apply when selecting a claim:

  1. Clarity: Can you write the claim in one sentence? Are key terms defined? Can you specify success and failure?
  2. Evidence access: Can you find primary sources, data, reputable summaries? Are experiments, observations, and controls identifiable? Can different interpretations be compared?
  3. Auditability: Can the claim be tested with rigorous tests? Are null models and alternatives definable? Can risky predictions or falsifiers be written?

If a claim fails any of these filters, it will lead to a weak audit.

Choosing the proper scope:

  • Your claim should fit the limited space and time of a capstone.
  • Claims that require covering whole fields (e.g., all genetics or all evolution) are too broad.
  • Pick a claim focused on one system or one proposed pathway.
  • Good candidates often come from real papers, textbook statements, popular science articles, or common public arguments.

Rewriting claims in operational terms:

  • Replace vague language with testable terms.
  • Example:
    • Vague: “This evolved over time.”
    • Operational: “This function can be produced by this mechanism under these conditions within these constraints, and intermediate stages remain viable.”

Final checkpoints before finalizing your claim:

  • What system does the claim address?
  • What function is being asserted?
  • What mechanism is being proposed?
  • What evidence would falsify it?

If you can answer these, you have a claim worth auditing.

Next steps:

In the next lesson, you will learn how to use the audit template to turn your claim into a structured evaluation with:

  • Defined steps
  • Controls
  • Alternative explanations
  • Conclusions grounded in evidence

Complete and Continue  
Discussion

0 comments