671
edits
Forking: Difference between revisions
Expand merging and add individuation
m (bold) Tags: Mobile edit Mobile web edit |
(Expand merging and add individuation) |
||
| Line 5: | Line 5: | ||
During the process of merging, one may encounter conflicts. These occur when the same event was witnessed from two different divergent viewpoints or when, in sufficiently [[Individuation|individuated]] instances, there is a strong divergence in interpretation, which colors how the memory was stored. | During the process of merging, one may encounter conflicts. These occur when the same event was witnessed from two different divergent viewpoints or when, in sufficiently [[Individuation|individuated]] instances, there is a strong divergence in interpretation, which colors how the memory was stored. | ||
=== Reconciliation === | |||
When maintaining a long-lived fork, a cladist can keep them on the same page by having them merge down regularly only to refork back into them. Done frequently enough, this creates a sort of gestalt of individuals. True Name keeps such a pool of instances, numbering 108 on Lagrange in systime 226 (2350), reconciling daily. | |||
=== Bubbling up === | |||
Prior to the Century Attack, it was only possible to merge down, not up. To address this, the down-tree instance would fork and let the up-tree merge down, and then that instance would assume the identity of the old up-tree. | |||
== Individuation == | |||
The longer two instances stay separate the more different from each other they become. This process is called individuation. | |||
=== Dissolution strategies === | |||
Depending on how one engages with individuation, there are three loose categories of cladists: | |||
* Taskers | |||
* Trackers | |||
* Dispersionistas | |||
== Gallery == | == Gallery == | ||