The Genetic Orrery
Case Study VIII-a mapped the genetic sphere as two-dimensional concentric rings — a simplified instrument, built to carry exactly one idea cleanly: relatedness has a hard horizon, and Host and Guest are the same person facing in opposite directions. That page still stands, and nothing in it was wrong. But its spine could only hold one ancestor per generation, a single fused "Mother+Father" unit with no way to represent a half-sibling, a half-aunt, or the roughly one in six children who grow up with one. This case study is the fully realized instrument built to hold what the simplified one could not: a three-dimensional orrery mapping all 995 structurally distinct positions inside the same D≤7 horizon, addressable by generation, by lineage, and by relational plane, ready for a real genealogical database to eventually populate.
What follows is not a rehearsal of the first case study's argument. It is an account of what changed to make a second instrument necessary, what the new one deliberately still refuses to assume, and what it suggests once the frame widens past a single family — toward a use for this kind of mapping that has nothing to do with selling attention, and everything to do with why genealogy is worth doing honestly in the first place.
Fig. 1 — The genetic sphere in three dimensions. Radius is still true genetic distance, exactly as in the concentric-rings version; the new axis is latitude, which now carries generational offset from center the way the flat page's vertical spine once did, freeing azimuth to carry lineage — which specific ancestor or ancestor-couple a relative descends through — instead of forcing it to also do latitude's job. Color marks the same three-way division the flat page used: ancestor side, descendant side, and your own generation, unchanged.
What the Sphere Assumes
Every one of the 995 positions on this sphere is a slot, not a person, and the distinction is the whole design. Two hundred fifty-four of them are your lineal ancestors — the fixed count every human being has, without exception or estimate: two parents, four grandparents, on to one hundred twenty-eight fifth great-grandparents, summed across seven generations because seven is where the rest of this project has already located the practical horizon of detectability. Descendants mirror that structure exactly — another 254 — not because anyone's future children are a fact yet, but because the slot for one already is, in the same sense a chair is still a chair before anyone sits in it. The remaining 487 are collateral relatives — siblings, aunts and uncles, cousins at every degree and remove, full and half alike — each one anchored to a specific shared ancestor or ancestor-couple rather than floating free. Add the four figures together and the total isn't round, which is the point: 995 is what the mathematics actually produces, not a number chosen to look clean.
None of those categories was allowed to answer a question it wasn't built for. Gender belongs to whoever eventually fills a slot, not to the slot itself — a full cousin through a given grandparent-couple is one position on this sphere regardless of whether a real family fills it with a man or a woman, for exactly the reason the scaffold never asks how many children that couple actually had. Both are facts about a specific family that hasn't been supplied yet, not facts about the shape every family shares. What the sphere declines to guess at is precisely what makes it usable for more than one family in the first place — including, eventually, a real one, with real names and real vital records attached to slots that were waiting for them.
One category is missing from the sphere entirely, and that omission is deliberate rather than an oversight. Affines — the people who marry into this structure rather than descend from it — never receive a position of their own. Importing an in-law's own ancestry would mean importing an entirely separate 995-node universe into this one, which would break the hard boundary the whole model depends on to mean anything. Instead, an affine functions as a gate rather than a destination: present exactly at the couple they complete, necessary for every blood relative who descends from that union, and absent everywhere else on the sphere. It is a small structural decision that turns out to carry real weight, once the frame widens past one family — a marriage, on this reading, is never itself a new slot. It is the mechanism by which two entirely separate slot-universes agree to produce one.
Beyond the Family Tree
What makes this instrument more than an illustration is how little would need to change for it to stop being hypothetical. Paired with an actual database of vital statistics for a real set of D≤7 relatives, the same query language already built into the toggles — which generation, which side, how far, what kind — could run against real records instead of empty structural slots, and the sphere would simply light up with whoever is actually there. That surfaces connections and possibilities that would otherwise almost certainly stay hidden inside a flat list or a paper chart, suggesting new ways to act within a whole system rather than just one visible piece of it — a form of system-wide leverage this project has not yet fully articulated but can now at least point a working instrument toward.
Nor does the underlying pattern actually require genetics at all. Radius, here, is standing in for the one thing genealogy happens to supply for free: a precise, unchosen, quantitative measure of relational distance, the halving fraction of shared DNA per generational step. Any relationship admitting its own version of that same thing — a real, non-arbitrary measure of proximity, and a comparable notion of a common origin two parties can be traced back to — could be mapped with the identical geometry. Evolutionary linguistics has one; so, more loosely, do professional networks and organizational lineages. What all of them share with genealogy is the same underlying shape this whole project keeps finding at every scale it looks: a Host and a Guest meet, produce a genuinely new integrative whole neither party could have produced alone, and the process repeats from there. Genealogy is only the special case with the cleanest instrument already built for it.1
The same pattern that makes two people's family spheres worth mapping separately also makes the question of merging them worth asking directly, and it was in fact the question that started this whole line of work: can the overlapping D≤7 spheres of two people who form a partnership be shown as one structure rather than two? The honest answer, at this stage, is that the hard part is solved and the easy part isn't built yet. Nothing about the design needs to change to allow it — a shared slot is just a slot two people's scaffolds both point to, and an affine entering the picture is already, by Section I's own rule, a gate rather than a second universe grafted on. What doesn't exist yet is the rendering itself: two spheres, offset by their real relational distance, occupying one coordinate system, with the "Third Thing" — a shared child — marking a genuine third origin where both parents' spheres collapse into one. That is real future work, planned but deliberately not attempted on this page, and it carries its own fittingly recursive observation worth sitting with before it's built: a single 995-node family sphere, from far enough outside it, is just one node in a much larger structure of intermarrying families, and every node inside that sphere may, at a small enough scale, turn out to be its own walking ecosystem in exactly the same sense — not a metaphor borrowed for the occasion, but the same recursive logic Lynn Margulis's mitochondrion already demonstrated in Case Study VIII's own Section IV, one register down.2
It is worth naming, if only in passing, what a tool like this is not for. A network built to map who is related to whom, at what distance and through which line, is also a description of exactly the data a platform built for attention or advertising would want to extract, and hospitality's own vocabulary is more exploitable than a colder one precisely because it is warmer — a vulnerability this project has examined at length elsewhere and does not need to reopen here.3 The orrery is offered in the opposite spirit: a cartography of host-guest networks built to be looked at, not extracted from — closer to what a genealogical instrument aimed at understanding rather than extraction might have looked like from the start, had one ever been built that way.
The Rough Road
A genealogy chart that begins with a notable ancestor is already a pride object by construction — built outward from the one flattering fact its owner already knew before opening the chart. This sphere cannot be built that way even by someone trying, because it does not begin with a person at all. It begins with a shape every human being shares in common, fills in real names only afterward, and does not move, resize, or reshuffle itself depending on who those names turn out to be. A slot for a fifth great-grandmother is the same slot, occupying the same position relative to every other slot on the sphere, whether the person who eventually fills it was landed gentry or someone the record barely bothered to name. The abstraction is not a limitation this case study apologizes for. It is the thing doing the humbling, on purpose, before a single ancestor's actual story ever enters the picture.
That matters because genealogy's more common use runs the other way. Pursued for pride, it becomes a search for the one relative who justifies the search — a habit of editing a family's actual history down to its best-lit rooms. Pursued for groundedness instead, the same records point toward the opposite discipline: staying close to what this project has elsewhere called the rough road, the hardship, displacement, and unrecorded labor that a search for a flattering ancestor would edit out first. Two hundred fifty-four real people stand behind every person who has ever lived, in the fixed, unglamorous arithmetic Section I already laid out, and the arithmetic does not select for which of them had an easy road. Most, on any honest accounting, did not.
- On the recurring host-guest-third-thing pattern across domains beyond genealogy, including evolutionary linguistics, professional relationships, and organizational growth, and on this pattern's grounding in Levinas's ethics and in Camus's early fiction read against it — see this project's companion essay, Confrontation or Responsibility: Camus, Levinas, and the Fate of the Self.↩
- Ed Yong, I Contain Multitudes: The Microbes Within Us and a Grander View of Life (Ecco, 2016), on humans and other animals as walking ecosystems rather than isolated individuals — read here as the same recursive pattern this case study finds at the scale of a family sphere, one register down from Case Study VIII's own citation of Lynn Margulis on the mitochondrion.↩
- On hospitality's shadow — the shared etymological root of host, guest, and hostile; the Deceptive, Parasitic, and Coercive as this project's own named categories of relational failure; and the clinical "parasitic lifestyle" marker on Hare's psychopathy checklist — see the "Thinking Against Itself" section of this project's Thinking Against Itself: Cosmoxenia and the Case for Narrative Reason, which treats this at the length it deserves rather than repeating it here.↩
No comments:
Post a Comment