# The two branches never rejoin > A timeline that forks two thirds along and stays forked — a diagram of a disagreement nobody could settle, drawn so neither branch outranks the other. August 21, 2026 · https://justog.club/stories/the-timeline-with-two-branches One line of events, agreed on, running left to right. Then a ring instead of a filled dot, and the line splits. One branch climbs, drawn brighter. The other keeps going straight, drawn the same pale tone as everything before the fork. They never come back together. That's not indecision. It's a record of exactly where the agreement stopped. ## Why does the line split instead of just picking one order? Because at some point the sources disagree, and a chart that picks one side is lying about how settled the record actually is. Everything before the fork is uncontested — every account, every printing, every version tells it the same way. After that point, they don't, and drawing a single line through the disagreement would erase the fact that there ever was one. The fork isn't a design flourish; it's the shape the evidence actually supports. ## What does the hollow ring at the fork mean? It marks the one point every account still agrees on — the last shared event before the record splits. Every other point on the line is filled solid, because it's settled. The ring is drawn open because it's doing a different job: it's not an event so much as a hinge, the last place both versions were still standing on the same ground before they went separate ways. ## Why is one branch brighter than the other? It isn't ranked higher — it's just easier to follow once two lines are running near each other on a small print. Give both branches identical weight and colour and a chart this size turns into a tangle the moment they run close together. Colour is doing separation, not judgement: neither branch is drawn thicker, longer by design, or placed above the other in a way that implies correctness. Two things being genuinely unresolved is rarer to see drawn without a winner than you'd think — [the same refusal to fake a single order shows up in a diagram built the other way round](/stories/the-numbering-that-doesnt-match), mapping two sequences instead of one that splits. ## Where does a split like this usually come from? An adaptation that changed an event's order, a reprint that moved a chapter, or one dated line in the work that flatly contradicts another dated line somewhere else. Once that kind of contradiction exists, there's no clean way to resolve it without picking a side — so the timeline stops trying to resolve it and draws the fork instead. That's usually a more useful document than a confident single line would have been, because it tells a newcomer exactly where the argument starts rather than hiding it — the same service [a diamond in a decision chart performs](/stories/the-watch-order-flowchart) for a question with more than one right entry point. ## Does this only work for a fictional continuity? No — anything with two competing accounts of the same stretch of events takes the same shape: a family history after a falling-out, a project's rewritten origin story, a friend group's retelling of one chaotic night that everyone remembers differently past a certain point. The fork works in all of those cases for the same reason: past the point of shared memory, forcing one version is a choice, and drawing both without ranking them is a different, more accurate choice. ## Can I use a real timeline from a real continuity? If a specific work's actual disputed chronology is the point, that's somebody's research and compiling it wholesale is different from being inspired by the shape of the argument. The fork-with-a-hinge structure belongs to nobody — any timeline with a contested stretch can be drawn this way. An invented split sidesteps the debate itself and keeps the design about the *shape* of disagreement, which is the part that actually reads on a chest from ten feet away, the same way [a form full of illegible rows still reads as a form](/stories/the-wiki-infobox) before anyone fills a single one in. ## Does it print well? Yes. A line of solid dots connected by hard rules is about as robust as a print gets — flat shapes, no gradient, a hollow ring that reads clearly even small. Two colours is enough: one for the shared trunk and one branch, a second for the other, with the ring left as an outline in the trunk's colour so it reads as a pause rather than a third branch. Keep the fork itself off-centre rather than dead middle, or the two arms read as a symmetrical logo instead of an actual split. ## How do I get one made? Describe where your own split happens and which branch gets which colour at [JustOG](/). Pick a direction, drag the crop frame, see it composited on the real garment, and it's made to order and shipped. Designs other people have published are in the [shop](/shop). Two branches, equal weight, running to the edge of the shirt without ever meeting again.