Execution And Build Descriptors
Execution and build ownership in Morph is descriptor-driven.
Execution Descriptors
Execution packages can describe:
- execution artifacts
- execution engines
Real examples exist in the Vcon package:
[execution.artifact.vcon]
[execution.engine.vcon]
This is how execution ownership stays package-owned.
Build Descriptors
Build packages can describe:
- build pipelines
- target platforms
- artifact transformations
The generic build system then resolves providers through the package graph instead of through core platform branches.
Why Descriptor-Driven Matters
Descriptors let packages declare capability without hiding policy in source code.
That means:
- build providers are explicit
- execution engines are explicit
- artifacts are explicit
- platform behavior stays in packages
Package Split
A useful mental model is:
| Package | Owns |
|---|---|
Build | generic orchestration |
Windows / Web / others | concrete platform provider behavior |
Vcon | execution format and engine |
That split keeps the framework extensible.
Design Rule
If a new execution or build behavior is needed:
- first ask which package owns it
- then add or extend descriptors in package space
- widen the generic execution/build SDK only if package declarations cannot express the new behavior
Next Steps
- Generated Glue And Factories - how descriptors become runtime registration
- Extending Existing Packages - applying these ideas to real package work