Host first, then optional path prefix
MinuteWork public ingress resolves properties by host first. When multiple public properties intentionally share a host, MinuteWork can also evaluate a path-prefix layer to choose the right property without changing the release model. The separate developer docs app now lives on docs.minutework.com; shared-host prefixes such as /docs still belong to tenant public-site use cases.
Longest prefix wins
When multiple verified bindings exist for the same host, ingress resolves the most specific matching path prefix.
docs.minutework.com/guides/...resolves to the dedicated developer docs app by hostwww.example.com/docs/guides/...can resolve to a tenant public docs property by prefix/pricingresolves to the root property on that host- all other unmatched paths fall back to the root binding if one exists
Property selection comes before release selection
Routing answers one question first: which property should receive this request?
Once the property is selected, the existing release model still decides whether the request resolves to a preview or live release. Path prefixes do not invent a second deployment system. They only refine property selection on a shared host.
Preview still works
Preview bindings and preview grants still work at the property level. A docs property can have its own preview release and its own canonical live release, independent of the product surface that shares the domain.