Composition Is The Useful OOP Analogy
An object can hold state, expose an interface, contain other objects, and preserve identity while its internal state changes. Cartilage borrows that compositional intuition, not the entire semantics of a particular object-oriented language.
The important questions are ownership and boundary. A parent knows which child it owns. Communication crosses an interface. The child has local state. Replacement changes the child without requiring every other component to become one flat global object.
A Named Helper Is Not A Region
A source-language function, macro, class, module, or repeated helper can be expanded into ordinary logic inside the current region. That is useful hierarchy for humans and tools, but it does not automatically create an independently reconfigurable child.
The current QuadFlow semantics make this distinction explicit:
A child region exists only when the concrete configuration declares one. Naming alone does not allocate space.
The Boundary Is Executable
A spatial boundary is made of cells, side connections, ports, and routes. It determines where application values cross, where configuration enters, and which cell owns the transition between parent and child.
That makes the interface inspectable. A missing route, wrong orientation, misplaced port, or broken ownership pointer is not hidden inside a global runtime table; it appears in the fabric state and propagation path.
Independent Replacement Requires A Configuration Surface
Ordinary application ports carry the computation the child performs. An independently replaceable child also needs a way to receive a new description of what its region should become.
In the Cartilage model, a local reconfiguration port connects the parent-facing configuration stream to the daughter's ownership tree. A complete image can replace cell roles inside that bounded region: wires, intersections, constants, MUXes, and port roles. The port is part of the image-dependent spatial mechanism, not a permanent magical pin outside the fabric.
Identity And Lifetime Become Spatial Questions
If a child is replaced, what remains the same? Its boundary location may remain while its interior roles change. Its parent relationship may persist while application behavior is replaced. A later configuration could also relocate which cell acts as the port if the architecture and install path support that transition.
The current compact Core example proves one manually specified 6x6 installation through one port arrangement. It does not prove a second install through a relocated port. The broader preserved substrate demonstrates nested spatial behavior, but a general high-level allocator and placer remain separate work.
“New Variable” Means Allocate A Neighboring Machine
The teaching analogy is dynamic variable instantiation: a running parent requests a new child, an adjacent bounded region becomes the child's storage and logic, and a local stream defines what the child is. The variable is not an address into hidden global memory; it is a new owned machine occupying space.
That is an architectural interpretation of the nested-instantiation line, not a claim that a public high-level new syntax currently compiles into arbitrary Cartilage placement. The next page shows the canonical live artifact and the concrete local mechanism it does establish.