One authored source-to-parameter connection.
A route is not an automation lane, and the difference is what it writes. An automation lane authors a parameter's base value over time: at a given position the lane says what the parameter is. A modulation route instead contributes a relative offset on top of whatever base is in force, so the two compose rather than compete — the base can be automated, a knob, or a preset value, and modulation still applies. This is CLAP's param_value/param_mod separation, and it is the engine seam this schema exists to keep open.
Two consequences the document must therefore preserve, and does: several routes may reach one parameter and their offsets sum, where two automation lanes driving one parameter is a contradiction the model rejects; and a route's depth is a property of the connection rather than of its source, so one macro reaches many parameters with a different amount for each.
1.15.0