This venue's process tree — internal.

The limiter is configured from what capabilities/0 declares

The declaration is not decoration beside the mechanism; it is the mechanism's configuration, so the two cannot drift.

Webull is the venue whose REST budget is the binding constraint in the family — the prior adapter measured 118 ms per call across 342 symbols — so the ceiling here matters more than on venues with room to spare.

Production and UAT run side by side, with separate everything

A consumer trading live while testing against UAT is running two of this venue at once. Every default name derives from the environment so the two neither collide nor share a rate-limit bucket — the second of which is the dangerous one: UAT traffic metering against the production budget would surface as a throttle on a real order, with nothing pointing back at the cause.

Explicit :name / :feed / :limiter still win, for running two of the same environment under different credentials.