Feature request for supporting document publication tree

As a CMS user I want to be able to define document publication trees.
------------------------------------------------------------------------------------------
1. What is a document publication tree?
When I have several documents in my CMS I should be able to build up a kind of logical tree of documents which are connected to each other therefore they needs to be published in a pre-defined order, or/and at the same time, or/and different time.
------------------------------------------------------------------------------------------

2. How to identify a document publication tree from the now existing data?
Possibly it's not possible. I mean if you count on the relevance between the documents based on links that's probably a good starting point but imagining the different setups out there, could be also other documents that are not linked inside the tree but should be part of the publication.
So at the end maybe the best would be to give the user the ability to define this kind of connections between his/her documents inside the CMS.

3. Moving one step forward.
Nowadays in Software Engineering at least in Agile terms we have sprints. This sprints are planned, the tickets are commited on meetings to the sprints. The main point that it's pre-planned.
Now what about if we could give the user something similar:

• Planning the documents(by type and name) that he wants to push out in the same tree.
  -Add the possibility to give the document Type and the Document Name to the system to start build the tree.
  -After the user has the first version of the whole plan the documents that are in the tree should be created. So the user also needs to pre-think about where each document should be placed and that information input to the system.
  -Once the documents are created the user should be able to edit them.
  -Once the user finished the feeding with data the documents, he is ready to publish the tree.

4. What are the pre-conditions of publishing such a tree:
-All the documents that are included in the tree should be verified that all the required fields are not empty.
-Make the user attention that before doing the publication a last review is recommended over the included documents.

5. Give the possibility to add/remove documents from the publication tree.
-Removing case:
This should not affect documents that are already published in the tree, just make a notice to the user, that from now he needs to take it offline by "manually" if he wants.
-Adding case:
If the tree is already published ask the user do he/she wants to publish it now, or later(giving the exact time) or manually.

6. One specific document can only belong to one publication tree.
-Moving from one tree to another should be possible. Copy is not allowed.

7.Relationship between publication trees:
Maybe there could be a case when a complete tree is published but in the background I'm creating a new tree with new documents. In this case I want to replace my documents with the new tree. So give me the possibility to define the relation between the trees and define the action between them that needs to be taken.