# network
A direct network declaration becomes the harness builders its declaration site compiles.
## Boundary
This child is the compiler descriptor adapter for one question: what conforming harness constructor data does the declaration state?
Capture admits the physical harness path, names, directed links, schedule membership, and fault material that the authored tokens can settle.
Rendering uses only that informed declaration to emit one module containing the topology and schedule builders.
The generated functions still call the harness's public smart constructors, so harness-owned value refusals remain harness-owned rather than being predicted here.
The physical harness path is declared input because a direct expansion compiles where it stands.
A renamed dependency and a facade re-export therefore cross through the same binding instead of a guessed crate name.
## Composition
Capture preserves authored order and resolves each schedule phrase to the link it names before a declaration can exist.
Canonical content commits to that ordered meaning and the physical binding before planning.
The descriptor door walks the generic request road and delivers the rendered module as one declaration-site unit.
The declaration chooses no campaign, opens no simulation, and judges no network behavior.
Those decisions remain with the adopter and the harness network home.