what is a side system vs sub system vs layer? ive heard multiple definitions of subsystem and im confused (I'm sorry if this sends multiple times my wifi is bad)
No problem! All of these terms are very similar and rely heavily on inner structure. I hope this helps:
'Subsystem' can mean multiple things. The first meaning refers to groups of alters that are somehow linked together and separate from other alters somehow. This could be a group of alters very similar to one another, ones with better communication between one another, or separate in other ways. Subsystems may reside in specific areas of the innerworld or have a separate inner world themselves.
The second definition refers to 'alter-in-alter' subsystems. Think of it like a russian nesting doll - an alter has their own alters. These subsystems may have their own innerworlds and struggle with communicating with those in the main system when fronting.
The third definition is an overarching term for any groupings of alters, including layers and sidesystems. Basically, it's a catch-all term. This definition is the most common within clinical literature, so when reading them, it might be confusing.
Here's an attempt at a visual representation:
The larger subsystem has good communication with the rest of the system and resides in its own area of the innerworld. These parts could have all split to deal with the same specific trauma and are considered a subsystem because they sort of stick together.
The smaller subsystem is a possible example of an alter-in-alter subsystem. The part that's inside the main system may be the "host alter" for that subsystem. Their innerworld is disconnected from the main one and may have communication difficulties.
'Sidesystem' can refer to a programming-specific phenomenon where programmers specifically create programmed parts somewhere completely separate from the main system. I'm using this definition because it's what I was referring to in my previous post, and I don't feel like debating if non-programmed systems can have structures that are similar. In literature, this is seen referred to as 'Left' and 'Right' sides of systems, but they don't necessarily have to be right next to each other. Despite the name, they don't have to be left/right, that's just how some people describe them.
Sidesystems typically have their own innerworld and are used by programmers to keep programmed parts hidden and separate from the main system or those that deal with day to day life. Sidesystems themselves can be layers. There may be one or two higher ups that can travel between sidesystems.
A notable difference between sidesystems and other groupings of alters is the amnesia level. Amnesia barriers between sidesystem alters and non sidesystem alters are huge. While there can be amnesia between other groups, the whole point of sidesystems is to create a completely separate "system," and thus, very heavy amnesia is present.
An attempt at a visual representation:
Sidesystems have no connection with the main system. This can be changed through integration of course, but as a base, they are completely seperate. Ideally, none but a couple alters will know about each other.
'Layers' refers to groups of alters that are separate from the main system, often "stacked" on top of one another. Despite the name, they don't have to be stacked. That's just how some people describe them. Layers are very common within polyfragmented systems, especially programmed systems. Layers often have their own themed innerworld, for example, a city or forest. Alters are typically separated by purpose or other split patterns and may have communication difficulties with other layers. In programming, layers are often seen within sidesystems or are sidesystems themselves. There may be some connection between layers.
An attempt at a visual representation:
In this, there are three layers stacked on each other. The main system has a connection to the layer below them and may be able to communicate more easily. The layer above, however, has no connection, and it may require a higher up part to communicate with them.
As you can see, all of these terms are very similar and can overlap with one another, and all can exist within the same system. At the end of the day, use what you are most comfortable with. Do you just want to call everything a subsystem? That's fine. If you like the specification? That's also fine.
For example, one person says "I kind of visualise it as descending 'containers' of alters. Like it goes, 'sidesystem -> has multiple layers -> has multiple subsystems.' but I know that that isn't everyone's experience."
Another says, "I can't be assed to specify what kind of group it is. I call everything a subsystem. It works for me."
All in all, I hope this helped. Let me know if you have any other questions, and I'll do my best to answer them.
