chore: remove orchestration (#471)

Author: reubeno

FUTURE.md docs/ideas/IDEAS.mdFUTURE.md renamed to docs/ideas/IDEAS.md

@@ -2,17 +2,9 @@
 
 ## Package building
 
-### Full builds happen in build dependency order
-
-For full package build within one project, if a package (A) depends on another package (B), the dependent package (A) must be built after the package it depends on (B). The freshly-built (B) must be present in the build environment while (A) is built.
-
-### The build orchestrator understands static and dynamic build dependencies
-
-The build orchestrator is responsible for determining the correct build order based on both static and dynamic dependencies. Static dependencies are those explicitly declared through the `BuildRequires` tags in the spec file. Dynamic dependencies are the ones generated in the `%generate_buildrequires` section of the spec file.
-
 ### Parameterized components
 
-A single component can be defined to be built with a matrix of parameters, where each set of parameters results in a different "flavour" of the component being built. The build orchestrator must be able to handle such parameterized components and build all combinations of the parameters.
+A single component can be defined to be built with a matrix of parameters, where each set of parameters results in a different "flavour" of the component being built.
 
 Sample use cases: