amadan
Path routes across boxes: a prefix whose target lives on another box Feature Request open
The ask
Let a path route's target live on a different box from the hostname's own route. Today it is silently ignored: route_paths rows derive only from this box's routes, and backhaul fires on a host miss, never on a path target (path-routing spec §"Same box", 2026-09-02-path-based-routing-design.md). A prefix then falls through to the hostname's route, which is the safe direction, but the product cannot grow past one box.
Why now
The user-models spec (pegamento, branch design-user-models) recommends a hub for products that should feel like one place: example.com/acme served by acme's own instance through a path route, with the hub on the product's own domain. That is the cohesive shape Tito Go wanted and could not have. With targets pinned to one box, the recommended model has a hard ceiling. The skill states that ceiling today, and the hub scaffold checks each prefix actually reaches its tenant (the tenant's X-Carlos-Version, not the hub's), marking it failed if not.
Shape, loosely
A path hit whose target is homed elsewhere backhauls like a host miss does, keyed on the target host. The prefix map is already per-hostname and fleet-wide in the bucket, so every box can derive the row. Only the "local ready route" gate needs a remote form. Attribution (billing, version header, wake) already follows the target.
Path targets must share the hostname's box today, which caps a path-routed product at one box.