Decision-layer simulator on synthetic data. Not a wet-lab protocol, not a guide-RNA designer, not a deployable recommendation without your own genotype/phenotype data and domain review. See Model limitations and What could make this recommendation wrong? in the decision report below.
MVP v0.7.34 — Promptbio v0.1 Mapper + v0.2 Diff + Issue 07 Substrate + v0.3 Evolution Loop

Selection Strategy Simulator

Compare selection strategies as an early decision engine: Monte Carlo replicates, neutral/random baselines, genomic selection mockups, OCS-like constraints, cross planning, Pareto trade-offs, risk probabilities, and minimal CRISPR-aware edit introgression.

Small populations are intentionally allowed. Try N=8 or N=12 to see rapid drift and fixation. Runs are manual: if parameters are unchanged, recalculation is skipped. The Run simulation button shows worker-pool progress. Solid lines are the current run; dotted lines show the previous run.

  1. 1. Datasynthetic, built-in real, or uploaded CSVs
  2. 2. Confirmpopulation & data summary
  3. 3. Constraintsinbreeding, diversity, risk floors
  4. 4. Runcompare strategies
  5. 5. Feasibilitywhich strategies make the cut
  6. 6. Decision Reportplain-language verdict
  7. 7. ExportJSON / summary text
  8. 8. Next stepcross plan, edit set, or new run

No run yet

Press Run simulation in the left panel to compare selection strategies on the configured population. Results will appear here.

  1. The summary cards at the top compare best-gain / best-risk-adjusted / best-feasible recommendations.
  2. The Decision Engine Output panel synthesises the verdict in plain language.
  3. The Sensitivity sweep panel asks whether the recommendation holds if h² / selection / horizon / climate shifts.
  4. The strategy table, Pareto chart, allele-frequency histogram, and per-generation charts give the visual evidence behind the verdict.
  5. The candidate-edit table classifies each edit as EDIT / CROSS / WAIT with reason on hover (Issue 07).
  6. Export the full run as JSON (button on the left) for follow-up analysis or audit.

If this is your first time, leave the defaults and just press Run — a balanced configuration is preloaded.

Decision engine output

Sensitivity sweep — does the recommendation hold if h² / selection / horizon shifts?

Run notes

Genetic gain

trait mean vs baseline

Diversity

mean heterozygosity

Inbreeding risk

approx. diversity loss

Effective population size — Ne = 1 / (2 ΔF), log scale; dashed lines mark FAO vulnerable (Ne=100) and long-term-viability (Ne=50) thresholds

Allele-frequency drift

mean abs. shift from start

Rare useful loci lost

warning metric

Fixed loci

rapid fixation becomes obvious in tiny populations

Pareto decision chart

genetic gain vs combined risk probability — axes are pickable when multi-trait is active

Upper-left is usually better: more gain with less combined risk. White outline marks non-dominated Pareto candidates.

Live allele-frequency spectrum

updates per generation while the run is live
Waiting for first generation snapshot…

10 bins over [0, 1]: bin k counts markers whose current allele frequency falls into [k/10, (k+1)/10). Tracked from the BreedOS default ("balanced") strategy when present; otherwise the first configured strategy. The snapshot freezes on the final generation when the run completes.

CRISPR edit candidates

This is intentionally not guide design. It is a minimal decision-layer demonstration: which beneficial low-frequency loci might be worth seeding into a breeding strategy simulation.

RankLocusEffectAllele freq.Gain scoreRiskEdit / Cross / WaitDecisionNGT

Strategy recommendations

Strategy Rank Score Final gain ±σ Diversity ±σ Inbreeding ±σ Risk P(inb/div/loss) Fixed loci Parents Pareto Feasible Δ vs previous Recommendation

Export & next step

The run above is now in the browser only. Export it before closing the tab or running a new configuration — there is no server-side persistence.

Next step

  1. If the recommendation is stable across the climate sweep, plan the next breeding cycle around the best-feasible strategy named above.
  2. If the recommendation is fragile, choose the strategy explicitly for the weather year you expect (the climate-robustness section names the alternative).
  3. If the candidate-edit table flagged EDIT rows, route those loci to your CRISPR pipeline (Benchling / Synthego / CRISPResso) for guide-RNA design — BreedOS does not design guides.
  4. If you uploaded predictions and the imported_gebv strategy won, the GEBVs from your prediction pipeline are doing real work in this run; document the prediction-pipeline version in the exported JSON for audit.
  5. For a new run with different parameters: change the inputs on the left and press Run simulation again. The previous run is overlaid as dotted lines on the charts for direct comparison.