Chapter 16
Runtime Assembly
"A Build describes what should exist. Runtime Assembly is responsible for making it exist."
Why This Chapter Exists
The previous chapter introduced the Build Pipeline.
By the time a Build reaches Runtime Assembly, all required information has already been collected, validated and prepared.
The responsibility now shifts.
Preparation ends.
Construction begins.
Runtime Assembly represents the moment where authored knowledge crosses the boundary into executable runtime.
Within the Cube Framework, this transition is one of the most important architectural responsibilities.
What Runtime Assembly Is
Runtime Assembly is the process of constructing a runtime representation from a prepared Build.
It consumes information.
It creates runtime.
It establishes relationships.
It prepares the runtime object for initialization.
Runtime Assembly does not determine what should be built.
That decision has already been made by the Build Pipeline.
Its responsibility is purely constructive.
Assembly Is Not Initialization
One of the most important distinctions within the Cube Framework is the separation between assembly and initialization.
Assembly creates runtime objects.
Initialization prepares those runtime objects for use.
Although these phases happen close together, they solve different problems.
Assembly focuses on structure.
Initialization focuses on readiness.
Keeping these responsibilities separate prevents construction code from becoming responsible for runtime behavior.
Constructing the Runtime
During Runtime Assembly, the framework begins transforming architectural descriptions into executable systems.
Runtime objects are created.
Runtime Components are attached.
Relationships are established.
Ownership is assigned.
Required references are connected.
At the end of Runtime Assembly, the runtime structure exists.
However, the runtime object should not yet be considered operational.
Construction has completed.
Execution has not yet begun.
Runtime Assembly never creates the final gameplay experience immediately.
Instead, it creates the structural foundation upon which gameplay can safely operate.
Runtime Assembly Does Not Make Decisions
A common misconception is that Runtime Assembly should interpret authored content.
Within the Cube Framework, this is intentionally avoided.
Runtime Assembly assumes that every architectural decision has already been made.
Validation has completed.
Dependencies have been resolved.
Configuration has been prepared.
The Build already represents the desired outcome.
Assembly simply transforms that prepared description into runtime.
This keeps Runtime Assembly deterministic and predictable.
A Shared Architectural Process
Runtime Assembly belongs to the Cube Framework rather than to individual modules.
Whether constructing:
- a Weapon,
- a Vehicle,
- Equipment,
- or a future runtime system,
the architectural responsibility remains identical.
Only the participating runtime components change.
The assembly process itself remains consistent across the entire framework.
This consistency allows every Cube module to share the same architectural foundation.
Building Structure Instead of Gameplay
It is important to understand that Runtime Assembly does not create gameplay.
Gameplay begins later.
Runtime Assembly creates structure.
It establishes the runtime representation that gameplay will eventually use.
By separating these concerns, the Cube Framework allows infrastructure to remain independent from gameplay implementation.
The result is an architecture where gameplay systems can evolve without affecting the assembly process itself.
Why Runtime Assembly Exists
The Cube Framework deliberately introduces Runtime Assembly as its own architectural stage because construction is fundamentally different from execution.
Preparing information is one responsibility.
Constructing runtime is another.
Executing gameplay is yet another.
Separating these stages allows each subsystem to remain focused on a single responsibility while contributing to the overall Runtime Pipeline.
Design Note
Whenever Runtime Assembly requires additional information in order to construct a runtime object, ask whether that information should already have been prepared by the Build Pipeline.
Runtime Assembly should consume prepared knowledge rather than discover new knowledge.
Framework Law XVI
Runtime Assembly constructs runtime. It should never redefine it.
Assembly transforms prepared knowledge into executable structure.
The architectural decisions have already been made.
Looking Ahead
Runtime Assembly establishes the structural foundation of every runtime object.
The next chapter explores Runtime State and explains how the Cube Framework gradually transforms assembled structures into fully operational runtime representations.
Revision History
Version 1.0
Initial publication.