Forking - Revision history

Fireheart&: Apply 'systime' template.

2024-02-03T18:29:31Z

Apply 'systime' template.

← Older revision		Revision as of 18:29, 3 February 2024
Line 7:		Line 7:

	=== Reconciliation ===		=== 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.		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]] {{Systime\|2350}}, reconciling daily.

	=== Bubbling up ===		=== Bubbling up ===

Makyo: /* Merging */ add cross-tree

2024-02-02T08:04:03Z

Merging: add cross-tree

← Older revision		Revision as of 08:04, 2 February 2024
Line 11:		Line 11:
	=== Bubbling up ===		=== 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.		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.

			=== Merge direction ===
			Prior to the Century Attack, an instance can only merge down — that is, only the instance which forked them will receive memories when they quit. However, as part of the work done to repair the System, the ability to merge up- or cross-tree was added. This is only available on Lagrange as of the first few years after the attack.

	== Individuation ==		== Individuation ==

Makyo: /* Reconciliation */ links

2024-02-02T07:59:21Z

Reconciliation: links

← Older revision		Revision as of 07:59, 2 February 2024
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 ==
	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.		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 ~~[[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 individuated instances, there is a strong divergence in interpretation, which colors how the memory was stored.

	=== Reconciliation ===		=== 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.		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 ===		=== 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.		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 ==		== Individuation ==

Makyo: Expand merging and add individuation

2024-02-02T07:55:00Z

Expand merging and add individuation

← Older revision		Revision as of 07:55, 2 February 2024
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 ==

Makyo: bold

2024-02-02T06:59:57Z

bold

← Older revision		Revision as of 06:59, 2 February 2024
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 ==

Makyo: Category

2024-01-29T22:49:57Z

Makyo: Category

2024-01-29T22:48:23Z

Makyo: Gallery

2024-01-29T21:26:22Z

Gallery

← Older revision		Revision as of 21:26, 29 January 2024
Line 1:		Line 1:
	[[File:Dear forking.png\|alt=A fennec fox looking rather snarky, splitting into two.\|thumb\|Usually there is no such visual indication, but [[Dear]] is just Like That. Art by [https://irisjay.net Iris Jay].]]
	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 ==
	~~[[File:Merge.png\|thumb\|Dealing with a large merge. Art by [https://irisjay.net Iris Jay].]]~~
	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.		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 [[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.
	{{Stub}}
			== Gallery ==
			<gallery>
			File:Dear forking.png\|[[Dear]] forking. Usually, there is no visual representation of forking, but Dear is just Like That sometimes. Art by [https://irisjay.net Iris Jay].
			File:Merge.png\|One skunk merging down to another. Looks difficult. Again, there is not usually a visual representation for merging. Art by [https://irisjay.net Iris Jay].
			</gallery>{{Stub}}

Makyo: Clean up

2024-01-29T21:09:53Z

Clean up

← Older revision		Revision as of 21:09, 29 January 2024
Line 1:		Line 1:
	[[File:Dear forking.png\|alt=A fennec fox looking rather snarky, splitting into two.\|thumb\|Usually there is no such visual indication, but [[Dear]] is just Like That. Art by [https://irisjay.net Iris Jay.]]]		[[File:Dear forking.png\|alt=A fennec fox looking rather snarky, splitting into two.\|thumb\|Usually there is no such visual indication, but [[Dear]] is just Like That. Art by [https://irisjay.net Iris Jay].]]
	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 ==
	[[File:Merge.png\|thumb\|Dealing with a large merge. Art by [https://irisjay.net Iris Jay]]]		[[File:Merge.png\|thumb\|Dealing with a large merge. Art by [https://irisjay.net Iris Jay].]]
	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.		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 [[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.
	{{Stub}}		{{Stub}}

Makyo: Creation

2024-01-29T21:07:45Z

Creation

New page

[[File:Dear forking.png|alt=A fennec fox looking rather snarky, splitting into two.|thumb|Usually there is no such visual indication, but [[Dear]] is just Like That. Art by [https://irisjay.net Iris Jay.]]]
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 ==
[[File:Merge.png|thumb|Dealing with a large merge. Art by [https://irisjay.net Iris Jay]]]
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 [[Individuation|individuated]] instances, there is a strong divergence in interpretation, which colors how the memory was stored.
{{Stub}}

← Older revision		Revision as of 22:49, 29 January 2024
Line 14:		Line 14:
	{{Stub}}		{{Stub}}
	[[Category:Mechanics]]		[[Category:Mechanics]]
			[[Category:Cladistics]]

← Older revision		Revision as of 22:48, 29 January 2024
Line 10:		Line 10:
	File:Dear forking.png\|[[Dear]] forking. Usually, there is no visual representation of forking, but Dear is just Like That sometimes. Art by [https://irisjay.net Iris Jay].		File:Dear forking.png\|[[Dear]] forking. Usually, there is no visual representation of forking, but Dear is just Like That sometimes. Art by [https://irisjay.net Iris Jay].
	File:Merge.png\|One skunk merging down to another. Looks difficult. Again, there is not usually a visual representation for merging. Art by [https://irisjay.net Iris Jay].		File:Merge.png\|One skunk merging down to another. Looks difficult. Again, there is not usually a visual representation for merging. Art by [https://irisjay.net Iris Jay].
	</gallery>{{Stub}}		</gallery>

			{{Stub}}
			[[Category:Mechanics]]