Forking: Difference between revisions
m (Category) |
m (bold) Tags: Mobile edit Mobile web edit |
||
Line 1: | Line 1: | ||
Forking is one of the key mechanics of life on the System: it is the act of creating a copy of oneself. This copy may go on to live their own life or they may merge back down into their [[Clade|down-tree instance]] to provide them with all of their [[Memory on the System|memories]]. Their decision to merge down or not may be determined by their [[dissolution strategy]]. | '''Forking''' is one of the key mechanics of life on the System: it is the act of creating a copy of oneself. This copy may go on to live their own life or they may merge back down into their [[Clade|down-tree instance]] to provide them with all of their [[Memory on the System|memories]]. Their decision to merge down or not may be determined by their [[dissolution strategy]]. | ||
== Merging == | == Merging == |
Revision as of 06:59, 2 February 2024
Forking is one of the key mechanics of life on the System: it is the act of creating a copy of oneself. This copy may go on to live their own life or they may merge back down into their down-tree instance to provide them with all of their memories. Their decision to merge down or not may be determined by their dissolution strategy.
Merging
Should the fork choose to merge down, their down-tree instance will be provided with all of their memories. These may be accepted wholesale, or the cladist may pick and choose which memories to merge.
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 individuated instances, there is a strong divergence in interpretation, which colors how the memory was stored.
Gallery
-
One skunk merging down to another. Looks difficult. Again, there is not usually a visual representation for merging. Art by Iris Jay.
This article is a stub. You can help us by expanding it.