So here’s something VERY EXPERIMENTAL (explanation below the image):
Inspired by the thread Split ID Folder;
and inspired by the use of ‘
Heading IDs’ in the Life Admin Quick Start Pack;
and realizing I hadn’t organised my house components yet because I couldn’t think of how to map a very deep hierarchy into a preferrably shallow JD system;
I thought I would try to follow my own suggestion.
60% chance I’ll deeply, deeply regret this, and move it all to its own more suited system.
But I figure I might as well try for a week or so 
What is this??
I’m lengthening the IDs to create a hierarchy without putting this in subfolders. It requires some trickery, but if you alternate numerals and letters, things stay in the correct order. motivation: I prefer search/filter over clicking into sufolders.
Why?
I was reflecting on what @johnnydecimal said in his last video about how ID’s have grown bigger over the last decade, so subfolders are more justified now. I was thinking how this makes the ‘jump’ from level to level bigger (or smaller?). In any case, it feels like it makes it harder to know whether to make something a category or an ID …
So I thought: what if you could make it more of a sliding scale, without adding more folder levels. Maybe you could do this with Categories, too (in front of the decimal point).
Doesn’t it break the max-100-IDs rule??
Yes, it does. However, I feel like it kind-of doesn’t, because these are clearly defined as sub-ID’s of something. After the House Components (.1000, so really just .10 lengthened), the list continues with 1100_Maintenance.
How would this generalize?
My current thought is that if you ever came to the conclusion that you really needed to expand an ID into a kind of sub-ID like this, you would take your ID (e.g. 10 House Components) and rename it with more zeros, and maybe put a '301 moved permanently` record inside it, and split its contents up between new sub-IDs.
Downsides
To keep things sorting in the desired order, all the IDs have to at least the same number of numerals before the first letter or punctuation sign. (like 0001_Index). That’s silly because then you have to predict how deep you’ll go … but it’s not hard to left-pad later if necessary (if your setup can handle directory name changes). The alternative is to live with the shorter IDs coming before the longer ones.
(also, spot the problem with the ‘Floor’ section. ranger sorts 11.1013_Floor before 11.1013a1a_Subfloor, but thunar does NOT.)