A region that lives somewhere else
One region of your page rendered by another deployment, over the protocol the page already speaks.
Goal
Move the recommendations feed to a service that owns it, and find that nothing about the page changes except where one hole is filled from.
The feed belongs to another team. That is an organisational fact, and it usually becomes an architectural one — an iframe, a build-time package, a second bundle. Here it is a slot whose fill arrives from somewhere else, because a slot was always a boundary.
1 · Point the slot elsewhere
feed: { fragment: 'feed', stream: true,- run: 'isolate' },+ from: 'https://recs.internal/regions/feed' },
No new protocol. The remote answers with the same wire forms this page already negotiates — full markup, a patch or a delta — so the client that adopts the region does not know or care which deployment rendered it.
2 · What crosses the boundary
| Crosses | Does not |
|---|---|
| The values the slot declared it needs | Your session, unless the slot declared it needs it |
| The region’s markup, patch or delta | Your database, your ports, your intents |
| A budget, and what happens if it is missed | Any authority the region did not ask for |
A region that writes into a sibling’s slot is E_REGION_ESCAPE, and that rule does not relax because the region is remote — it is the property that makes this safe rather than convenient. See a region that lives somewhere else.