The capability template owns no parallel state or timing descriptor. Its
active node set mechanically selects the concrete Fabric-owned
`ResourceState`, `UsePattern`, transition timing, progress, and physical
refinement closure of those nodes. An RTL provider consumes those exact
contracts through resolved Fabric views; provider availability cannot add
members, change the selected graph, or replace its state and timing semantics.