I having a difficult time making sense of your question.
Take this statement “Basically whenever I try to move a rem to a reference rem, the reference rem doesn’t show up as a parent when hitting the ⌘+shift+opt command on a Mac”. First, for the creation of a reference, you don’t move anything. You turn a rem (or part of the text in hat rem) into a reference. A separate, top level document is created to track the creation and use of that reference. Also, on Microsoft Windows systems, the key analogous key sequence is Ctrl + Shift + Alt. Ctrl + Shift + Alt + what? Or ⌘+shift+opt + what? They key sequences Ctrl + Shift + Alt or ⌘+shift+opt, by themselves, don’t do anything. But your use case is one of organizing documents and rems, not creating references.
“You decide that mission X can have a “project” aspect, you decide to create a reference to it called “Mission X-p”, then tag it as a doc, and move the doc under a parent rem folder called “Projects”.” The more logical approach is to create a document called “Mission X-p” (which you can do by creating a rem and tagging it as a document), and in the navigation pane, place that underneath Mission X, so that Mission X becomes a Folder and Mission X-p is a document in that folder.
“So now you want to move any project docs or rems related to “Mission X-p” as a child of “Mission X-p”” If you want to move any project docs as a child of Mission X-p on the navigation pane, then they would be "children of Mission X-p, and Mission X-p would become a folder housing those documents. As for rems, use a split pane to move the individual rems to whichever document you want them in. Or use the /move command and specify your target rem.
“Problem is whenever I try to do this… the only thing that pops up when activating the move to another parent command is “Mission X”.” The /move command will let you move the rem you are focused on to whatever rem you want to move it to.
