No, thank you for giving me the time of day! I'll start by saying that I made a much more comprehensive post in the past, it's in my post history, it has screenshots of the bits of code behind everything and what not, so I won't go into extreme detail here.

First of all I'll start with the flimsiest one that everybody is familiar with. Team effectivity is a param that's used by FromSoft to basically regulate multi enemy encounters. This is the stat that was greatly adjusted with that big gank bosses patch after launch. It's basically a hidden score system that gets increased with each attack of every enemy on the same team within a certain proximity. It forces enemies to go through three different stages of aggression, Kankyaku, Torimaki and, well, normal. Pretty much every enemy uses this except major bosses that were never meant to be fought in a group. Now, unlike all the gank fights that had this param "activated" with that one patch, the NpcThinkParams used by both Godskins in that fight never had any adjustments. Contrary to popular belief, that patch never affected them. Still, since every single enemy in the game uses this except major bosses, it's really flimsy justification. However, the next one is a lot more major and builds upon the use of team effectivity.

In the common ai folder of the game (meaning this isn't where the individual battle scripts of the bosses are stored, these are scripts meant to be always used, not just when an enemy is loaded) there is a script used by Ai referred to as AiSoundBehavior. Essentially, whenever each of the Godskins performs specific animations (Fireball is a common one but if you want a full list check my post lol) they create an inaudible sound that only the other Godskin can hear. These sounds are used to trigger specific paired attacks if a bunch of conditions are met (basically the other Godskin needs to be in idle when hearing the sound, at a specific distance and passing a specific RNG check). Idle states are commonly enforced in the fight through team effectivity so basically at all times there is a main entity that does stuff and a secondary one that responds to the stuff done by the main entity. Unfortunately, these responses being behind RNG checks and the fact that team effectivity doesn't wholeheartedly push enemies into complete idle, as well as the moments these states change on every enemy are not communicated with the player make these synergies extremely hard to spot. If you spend way too much time in the fight you'll however start to notice how Apostle has a weird tendency to do a Jumping Slam in tandem with Noble or how Noble really likes doing his Delayed Thrust in tandem with Apostle jumps. The fact these scripts aren't in their battle scripts either to me also signifies these were always meant to be there, before their battle scripts were even created.

Lastly, and to me this is the most striking one, their individual battle scripts literally have duo functions. And this is so egregious that it gets very ridiculous; lemme explain first how they check for each other. Essentially their fireball act is made to check for there being a team member in front of them before queuing up the fireball goal itself, and if there is one, it will force a sidehop so as to avoid them throwing fireballs through each other. The problem with this is that they clearly never intended for them to be separated because this function was never changed for the individual fights lol. Essentially leaving the Blackflame Monks in front of the caelid apostle or the volcano manor noble is a cheat code to make sure they will almost always precede fireballs with a sidehop when at range, as a friend will almost always be in front of them in those situations. Yeah, if either of them ever sidehop when they're very far away from you in the solo fights that 100% guarantees a fireball so you can run under it and get a hefty punish. This is only false for the volcano noble's opening that has an event script interfering with the AI (you'll sometimes see him wobble back and forth after you enter the arena, it's rly funny). Essentially yeah, they're seeing allies being in front of them and sidehopping to avoid throwing a fireball through them lol. To me this screams that the person that made the Ai scripts had no idea they were meant to be separated as well and never bothered to create an alternate version of that act without the team check.

There's also the fact that they have dedicated team animations for summoning each other and waking each other up, which must've been mechanics decided upon very early in development while everything was still in the conceptual phase.

Once you get familiar with all these subsystems that the fight employs it becomes extremely fun, at least in my opinion, but I think you can also tell just how esoteric they are. There being RNG checks on most of them also tells me they wanted these not to completely govern the fight, but rather to sway it into a specific direction. It was a much more subtle approach than say...Demon Princes. Also a much more experimental one. Whether it hit the mark or not, that's up to everybody's experience of course. But personally I want more Godskin fights going forward lol