SCIENCE · INVESTIGATE AND EXPLAIN

Separate carrier prevalence from a unique transfer history

A marker can become common because an existing carrier lineage expands, because the marker crosses lineage boundaries, because similar states arise repeatedly, or because the sampling frame changes. A pooled carrier frequency alone usually cannot distinguish these histories. Stable lineage information and time ordering add constraints but do not automatically identify a mechanism.

Learning outcome: Construct two records with the same pooled total and different lineage allocation. Retain each denominator and explain why neither pattern alone uniquely proves transfer or clonal expansion.

Starting recap

Trace copying, expression, inherited variation and horizontal-route evidence while separating sampling, ancestry, selection and model uncertainty.

All lessons are open directly. Your saved experiments remain when you leave and return.

Try

At a=40,b=0, pooled prevalence is 40/200=0.2 and within-lineage prevalence differs by 0.4. At a=b=20, pooled prevalence is still 0.2 but the within-lineage difference is zero. Equal marginals do not mean equal biological history.

Open the experiment

Predict

Can the same pooled prevalence support different lineage-association patterns?

Your prediction and reason

Experiment

Construct two records with the same pooled total and different lineage allocation. Retain each denominator and explain why neither pattern alone uniquely proves transfer or clonal expansion.

Compare the same carrier total across lineage backgrounds

Worked teaching model · synthetic values · Original two equally sized lineages, 100 cells each. Carrier totals and within-lineage prevalence are supplied records, not mechanisms. Transfer, repeated origins, ancestry or sampling can need additional evidence.

Carriers in lineage A: 40 of 100 cells Carriers in lineage B: 0 of 100 cells

Reset keeps your prediction, captures and practice history.

Equal pooled frequencies need not imply equal lineage distribution or one transfer history.

Original two equally sized lineages, 100 cells each. Carrier totals and within-lineage prevalence are supplied records, not mechanisms. Transfer, repeated origins, ancestry or sampling can need additional evidence.

Conditional evidence ledger, not actual microbial observations
Quantity	Value	Unit
Total carriers	40	of 200 cells
Pooled carrier fraction	0.2000000	fraction
Within-A carrier fraction	0.4000000	fraction
Within-B carrier fraction	0	fraction
A minus B prevalence	0.4000000	fraction

Original supplied records only. No genetic engineering, biological transfer execution, culturing or clinical interpretation is requested.

Equal pooled frequencies need not imply equal lineage distribution or one transfer history.

Observation to attach to a capture

Captures preserve recipes and replay their calculated results. They are synthetic model evidence, not physical measurements.

Understand

Define the evidence

Connect mechanism and measurement

The original record contains 100 cells in lineage A and 100 in lineage B. The controls select carrier counts a and b, so pooled prevalence is (a+b)/200, within-lineage prevalences are a/100 and b/100, and their difference is (a−b)/100. The population sizes remain fixed; changing a control constructs a comparison record rather than simulating a biological transfer.

Forty carriers confined to A and twenty carriers in each lineage both yield pooled prevalence 0.2. They differ in lineage association. The distributed record is compatible with horizontal movement, but it could also reflect older shared ancestry, repeated origins or misclassified lineage markers. A concentrated record is compatible with clonal expansion but does not prove that transfer never occurred.

The conclusion therefore stays at the evidence level: marginal frequencies can conceal structure. Additional independently documented ancestry and timing might distinguish competing histories. No donor selection, transfer procedure, resistance-generation step or organism-specific genetic construction is included.

Reconstruct the original record

Predict and investigate

Predict first: Can the same pooled prevalence support different lineage-association patterns?

Construct two records with the same pooled total and different lineage allocation. Retain each denominator and explain why neither pattern alone uniquely proves transfer or clonal expansion.

Defend a changed case

Apply the mechanism to a changed boundary

Use a=20,b=40. Find pooled prevalence and the signed A-minus-B difference.

Retain the first response, units, uncertainty and any prior feedback exposure in the notebook before comparing this public explanation.

Compare a worked response

Pooled prevalence is 60/200=0.3. Within A it is 0.2 and within B 0.4, so the difference is −0.2. The sign identifies association in this record, not the direction of a transfer event.

Retain bounded evidence

Preserve original assumptions, first responses and feedback exposure in the Microbiology evidence workspace. All numerical records are original fictional evidence. No culture, genetic modification, transfer execution, resistance generation or personal clinical interpretation is requested. Actual independent practical competence is not established.

Primary mechanism context, checked 30 October 2026. Original teaching and fictional data; no copied operating procedures.

Apply

Public practice checks a specific claim. It does not establish independent mastery.

Use a=20,b=40. Find pooled prevalence and the signed A-minus-B difference.

Your explanation and limitations

Continue

Completion requires a saved prediction, at least one capture and a reflection. Presence checks do not grade your reasoning.

Skipping retains experiments and awards no mastery.

Previous: Distinguish horizontal routes using bounded mechanism evidence Next: Explain descendant clusters without need-directed mutation

Save a science backup or import one

Science work is stored locally in this browser, separately from mathematics and AI. It does not sync automatically. Use this science-only backup; this checkout's older all-subject export does not include science.

A legacy file is available only when the complete snapshot fits the 36 MB limit. For larger snapshots, prepare a complete file set below; never discard notebooks to make a smaller file.

Choose a science backup (maximum 36 MB)

Matching imported notebook drafts replace their current drafts. Omitted lessons and known first attempts remain. Export your current work first if you want to retain both drafts.

Complete file sets and course backups

A file set can hold more work than one science file. Keep its manifest and every part together. Each file is limited to 36 MB. This format needs this version of LearnAI or a compatible newer version; older versions can use only the legacy single-file backup above.

Export scope

The set includes every saved science course and global continuation at this moment. Later edits need a new export. A conflicting tab exports its own visible work, which may differ from saved work in another tab.

Choose the manifest and all parts together

0 file(s) selected. File order and filenames do not determine identity. Missing, changed or conflicting parts block the entire restore; no good part is applied by itself.

Science storage: loading. No account or remote computation is required.