I like this idea.
I also want to point out, to readers in general, that the criticism that a CYOA is on rails and that your character can only do so many things is only somewhat valid, at best.
We’re talking about projects that are usually written by a single person. These are not massive, open-world, endless, MMO-depth RPGs written by a team of highly paid individuals.
If a single person could design and code something like that, don’t you think they would be working for someone like EA or Blizzard, or even have their own company?
Where I’m going with all that is that when we better “establish a nomenclature for the family tree of branching,” I’d like for said branching to be judged fairly and on an appropriate scale.
The A1, A2 thing or the A1.1, A1.2 thing can be a bit confusing. It may be easier to think about story chapters.
If the A in A1 represents chapter 1, then…
The 1 in A1 represents what exactly?
(That “1” can represent different things for different stories.)
So after we branch out and finally come to B (B1; B2; B1.1; B1.55555, etc.)
Now we’re talking about Chapter 2.
C is chapter 3
D is chapter 4
E is chapter 5, etc.
As far as the numbers… let’s look at A1 again, for example… 1 can represent a plot point, or perhaps the first choice tree.
If we go with the latter, consider this example:
I am buying a car at this dealership. I want the color to be…
If we use “A1” here, we’re talking about this first choice tree in chapter 1. At least, to my understanding.
So does that mean that the second choice tree should be A2?
Where would it make sense to use A1.1 instead?
(This is not a rhetorical question.)
However, before this becomes too confusing, we must remember the reason(s) why we are seeking to establish this nomenclature in the first place.