Just as a suggestion, I have been representing “topic notes” as follows.
Have a file-node explaining the topic. I tag it as “Index”
In each of file-nodes related to the topic, I create link to the Index node for the topic.
Note that you can have multiple topics in each node
The topic note (= the file-node tagged “Index”) can then show the related notes in its backlinks buffer (org-roam-buffer-toggle)
What this does not do from your list is to sort the notes by a “header property value” – by default, backlinks are sorted by the title in alphabetical order (source).
If you wish to achieve sorting backlinks by a property value, a simple way is to override function org-roam-backlinks-sort in the way you would like – that is, to write your own function in your configuration with the same function name and evaluate the new function definition after loading the original.
I would lean toward keeping the original sorting logic as it is; I don’t see the value in investing my energy sorting in a custom way, but of course that’s just me.
For known volumes, it’ll be either that or what @nickanderson suggested.
For my own in-development sequences I’m “embracing the graph” now. Adding a previous / next links to node. That way I only have to change 2 files when I add something in between. Better than changing ALL files after it. And it’s kinda like a digital choose your own adventure book which really helps figuring out structure.