ADR-0150: the flow doors held at main under R4-G judge the served holders (what a disabled holder's flow slot answers) #33386

domain:server#5 · os-elon-musk · session_016WV4cyrFFk86Jqf7Mp5Rzw

Parent: #32670 (its R4-G sweep). Filed by area E2 under the seat's routing ruling (2026-11-14T18:12Z, option A). Area-lease pilot #33059, lease:E2.

Premise

#32670's sweep clause asks that any other door held at main under ruling R4-G (PR #32497) judge the served holders. The doors found are flow doors: flow-slot-view.ts, automation-address.ts, packages/services/service-automation/src/engine.ts, and flowDispatchHolder. They resolve a flow's slot (dispatch), not an email bundle (read), so the email rule cannot be copied over. PR #33361 keeps them byte-identical to main.

Open question for the seat (ruled when claimed)

When the holder of a flow slot is disabled, what does the slot answer?

1. No flow (the name has no served answer at that slot).
2. The served holder's flow (another package that holds the name and is enabled).
3. A refusal naming the holders (reported, never guessed).

Fix shape (after the ruling)

• Each door judges the served holders under the ruled answer.
• A Clause-② table of its own: every moved answer FROM→TO with its arm, pinned per door, both registration orders.

Acceptance

• CONTROLs: all enabled, one holder, no holder.
• Red line: resolution is never loosened; an ambiguity is reported, never guessed.