This venue's process tree — internal.

A limiter and a feed, exactly as every other venue in the family, even though the feed behind them is a poll rather than a socket. That sameness is the point: a consumer's supervision tree looks identical whichever venue it holds.

The limiter is configured, not declared

Every other venue in the family takes its limits from capabilities/0. This one cannot: Schwab's documented ceiling is 0..120 order writes per minute per account, set per application at registration, so there is no venue constant to read. A number baked in here would be a claim about somebody else's registration.

So the limits come from options, and the default is deliberately generous for reads — which the venue documents as unthrottled — while a host that places orders should pass :order_limit_per_minute matching what its own app was registered with. Zero is a legal registration value, and a host with it should pass 0 rather than discover the ceiling by being refused.