Simulate haplodiploid honeybee genetics and uncover why ancestry counts follow the Fibonacci sequence
| Gen | Fibonacci Term | Drones (♂) | Queens (♀) | Total Bees | Diploid Baseline (2ᴺ) |
|---|
The saved bee genealogy tool teaches an idealized branching rule. One drone node gives one queen node. One queen node gives a queen and a drone. If m and f count the two node types, the next generation has m prime equal to f, and f prime equal to m plus f. Starting with one drone and no queens gives generation three one drone and two queens, total three. Generation four has two drones and three queens, total five. Bars show nodes with one common scale of sixty pixels per node. This is the source toy pedigree rule, not a census of real descendants or unique ancestors. The tool ledger reports the total sequence one, one, two, three, five, eight, thirteen. Each new total is the previous two totals added. At generation six its branching model reports thirteen nodes. The diploid comparison column is two to the generation, sixty four at generation six. Both bars use eight pixels per node. The comparison button changes the table header color; it does not change the recurrence or remove the comparison column. Switching ancestors and descendants changes node ordering and explanation, while this source uses the same count recurrence in both views. Use the native generation slider from one through six. The ledger and tree redraw together. At generation four, the exported JSON contains all five rows from zero through four with totals one, one, two, three, five. Their sum is twelve tree nodes, not five. Five counts only the last generation. The JSON also retains the chosen view and maximum generation. Reset returns to ancestors at four. These bars use forty pixels per node and distinguish a generation count from the cumulative drawn tree. Treat the biological labels as the pedagogical assumptions of this saved model.