The examples are ordered in a simple to complex manner,
the most powerful being last.
Right now, your design doesn't work with xlist as it is,
since you would first have to discard using fields at your entries
and to use tags instead.
However, I don't really want you to do that,
I actually want you to get a variant of xlist from me
that allow you to keep using those fields as list fields.
It is not more complicated... the opposite is true.
If you eventually get to have your index tiddlers to
automagically show the right entries by the right groups,
things couldn't possibly get any simpler.
New period, e.g. Dark Ages,
bam there are your indexs doing the right thing,
e.g. in the form of domain tabs.
All you needed to do is specify somewhere
which categories you wish to cross index at some index tiddler,
e.g. Renaissance by Domain would need to specify
that Domain provides the categories to look for,
currently via tagging tiddlers, in your case via field values (big difference!).
Also, instead of a tiddler Renaissance by Domains,
I would first start with a tiddler Renaissance.
In that tiddler I would link all the possible index tiddlers,
tagged, of course, Index,
Renaissance being tagged Period,
so that — at some other Foo by Period index tiddler —
you could use all tiddlers tagging to Period in just the same manner.
These categorization tags for your index tiddlers are essential for xlist to work.
That's why xlist by default uses categories from the core list field,
so that — at some point — you can reorder your Periods by their start time....
and then have any index Foo by Period automagically show periods
in the right chronological order, provided it knows that Period is the thing to group by.
In fact, with the filter parameter you can already do that right now,
assuming each Period had a field called begin,
containing a valid (hence sortable) date format, e.g. 18900101 => 01. Jan 1890.
Of course, automatic indexes do need some more brain-power invested in the setup,
rather than the kind of typng power you are using in your current setup,
i.e. a lot of repetition of lists and many things to tweak if you want to change anything.