@@ -3,25 +3,36 @@
 '@objectstack/spec': major
 ---
 
-A flow CEL expression that reads a root the flow does not bind is refused at `objectstack validate` and at the runtime publish gate. The run fails such an expression with `Unknown variable: X` (X being the root) on every evaluation, and the build door used to pass it. The reachable case is the run user: `user.id == "u1"`, `ctx.user.id == "u1"` and `os.user.id == "u1"` — the spellings formulas, row-level security and the client accept — are refused, naming `current_user`, the one spelling flow CEL binds.
+A flow CEL expression that reads a root the flow does not bind is refused at `objectstack validate`. The run fails such an expression with `Unknown variable: X` (X being the root) on every evaluation, and the build door used to pass it. The reachable case is the run user: `user.id == "u1"`, `ctx.user.id == "u1"` and `os.user.id == "u1"` — the spellings formulas, row-level security and the client accept — are refused, naming `current_user`, the one spelling flow CEL binds.
 
 Clause-②: no (narrowing)
 
 <!-- adr-0087: registered flow-cel-unbound-root-refused -->
 
-**BREAKING**: an accept-set narrowing on a published authoring surface (`objectstack validate`, and the runtime publish gate's `expression-invalid` rule for a flow write).
+**BREAKING**: an accept-set narrowing on a published authoring surface (`objectstack validate`'s `expression-invalid` rule).
 
 **Why.** Flow CEL evaluates in one scope per run: the flow's variables spread to top level, the trigger record's fields flattened beside them, and `record`, `previous`, `vars` and `current_user` bound by the engine. Formulas, row-level security and the client also bind the run's user as `user`, `ctx.user` and `os.user`; flow CEL does not, because a top-level `user` would collide with a variable or a lookup field of that name. So an author who wrote the alias by habit shipped a flow that faulted at its first evaluation, and nothing warned.
 
 **What is refused.** At every flow CEL site the build door reads — a node's `config.condition` (the start node's trigger gate included), an edge `condition`, a `decision` branch `expression`, a screen field `visibleWhen`, and the CEL value envelopes of an `assignment` and of a `create_record` / `update_record` `fields` map — a root that is none of:
 
 - the engine's roots: `record`, `previous`, `vars`, `current_user`;
 - a name the flow binds: a declared variable, an `outputVariable`, an `iteratorVariable` (a `loop`'s default `item` included), an `indexVariable`, an `errorVariable`, an `assignment` target, a node id, a screen field's `name`;
-- a field (or a registry-injected column) of any object the stack declares — the run flattens whichever record its entrance hands it.
+- a field (or a registry-injected column) of any object the stack declares — the run flattens whichever record its entrance hands it (an object-less flow action hands only the row `id`).
 
 The user spellings are told to write `current_user`, with the guard for a flow that can run without a user; any other root is named with what could have bound it, and the nearest in-scope name. The error is `expression-invalid`, `error`. Where the flattened-scope near-miss advisory ("`X` is not a field of … If `X` is a flow variable this is safe to ignore") named the same root, the refusal replaces it.
 
-**Not judged — the door stands down where the run can bind a name it cannot see.** A flow carrying a `script` or `connector_action` node (each hands its code the live variable map), a `wait`, `subflow` or `map` node (a resume folds the caller's `variables` bag in under their plain names), a screen with no field list, a node type outside the builtin set, or a trigger object the stack does not declare. A `$` name has no CEL spelling (`$runId == "x"` does not parse), so the `$` roots stay the text-slot rule's.
+**Not judged — the door stands down where the run can bind a name it cannot see.**
+
+- **A node:** a `script` or `connector_action` node (each hands its code the live variable map), a `wait`, `subflow` or `map` node (a resume folds the caller's `variables` bag in under their plain names), a screen with no field list, or a node type outside the builtin set.
+- **An entrance the stack declares that hands the flow a record whose keys are not in hand:**
+  - a record trigger (`config.objectName`) or a time-relative sweep (`config.timeRelative.object`) on an object the stack does not declare;
+  - an `api` trigger, whose inbound hook hands the request body in as the record;
+  - a `type: 'flow'` action launching the flow on an undeclared object;
+  - a `map` node feeding the flow whose `itemObject` is undeclared or absent;
+  - a `subflow` or `map` parent that is itself such a flow.
+- **The runtime publish gate:** a flow write there is not judged for unbound roots yet. Its per-write snapshot carries no actions or other flows, so it cannot see those entrances. Every other expression verdict at that door is unchanged.
+
+A `$` name has no CEL spelling (`$runId == "x"` does not parse), so the `$` roots stay the text-slot rule's.
 
 ## FROM → TO
 
@@ -34,9 +45,9 @@ The user spellings are told to write `current_user`, with the guard for a flow t
 
 **The one-line fix: write `current_user` for the run user, and bind or correct every other root the refusal names.**
 
-**Who is affected, measured.** The last published spec line, 17.x, judged a flow expression's syntax only, so it accepts every refused source. Measured with the judge over every flow CEL site: the example apps (`app-crm`, `app-todo`, `app-multi-package`, `app-showcase`: 35 flows, 45 sites), `packages/platform-objects` (no flows) and `objectstack-ai/hotcrm` at `f0afcbda07` (32 flows, 65 sites) — 0 refusals; every root those flows read is an engine root, a binding of the flow's own or a field of its trigger object. Deployed metadata and other repositories were not measured.
+**Who is affected, measured.** The last published spec line, 17.x, judged a flow expression's syntax only, so it accepts every refused source. Measured with the judge over every flow CEL site: the example apps (`app-crm`, `app-todo`, `app-multi-package`, `app-showcase`: 35 flows, 45 sites), `packages/platform-objects` (no flows) and `objectstack-ai/hotcrm` at `f0afcbda07` (32 flows, 65 sites) — 0 refusals; every root those flows read is an engine root, a binding of the flow's own or a field of its trigger object. One flow of the 67 is left unjudged by an entrance (`showcase_inbound_task_webhook`, an `api` trigger). Deployed metadata and other repositories were not measured.
 
 ### The kit
 
-- **The judge.** `flow-cel-root-scope.ts` in `@objectstack/lint`, called by `validateStackExpressions` at each flow CEL site. One bound set per flow, read once like the shadowing pass's variable set.
+- **The judge.** `flow-cel-root-scope.ts` in `@objectstack/lint`, called by `validateStackExpressions` at each flow CEL site. One bound set per flow, read once like the shadowing pass's variable set, and one entrance index per stack (`flowCelEntrances`).
 - **The ledger.** The D3 semantic entry `flow-cel-unbound-root-refused` (protocol 18). There is no D2 conversion: none of these roots ever evaluated in a flow, so there is no behaviour to carry over.
@@ -30,12 +30,17 @@ export const entry: SemanticMigration = {
     + 'and the build door, which judged a flow expression\'s syntax only, passed it. The run-user spellings are '
     + 'the reachable case: formulas, row-level security and the client bind the run\'s user under user, ctx.user '
     + 'and os.user as well, and flow CEL does not, because a top-level user would collide with a variable or a '
-    + 'lookup field of that name. objectstack validate and the runtime publish gate now refuse such a root, naming '
-    + 'current_user for the user spellings and the in-scope names for any other. A flow whose run can bind a name '
-    + 'the reader cannot see is not judged: one with a script or connector_action node, a wait, subflow or map node '
-    + 'a resume can fold a bag into, a screen with no field list, a plugin node type, or a trigger object the stack '
-    + 'does not declare. No D2 conversion exists: none of these roots ever evaluated in a flow, so there is no '
-    + 'behaviour to carry over, and a run without a user needs a guard only the author can choose.',
+    + 'lookup field of that name. objectstack validate now refuses such a root, naming current_user for the user '
+    + 'spellings and the in-scope names for any other. A flow whose run can bind a name the reader cannot see is not '
+    + 'judged: one with a script or connector_action node, a wait, subflow or map node a resume can fold a bag into, '
+    + 'a screen with no field list, or a plugin node type; and one an entrance the stack declares hands a record '
+    + 'whose keys are not in hand: a record trigger or time-relative sweep on an object the stack does not declare, '
+    + 'an api trigger (the inbound hook hands the request body in as the record), a flow action on an undeclared '
+    + 'object, a map node whose itemObject is undeclared or absent, or a subflow or map parent that is itself such a '
+    + 'flow. The runtime publish gate does not give this verdict yet: it judges a flow write without the stack\'s '
+    + 'actions and other flows, so it cannot see those entrances. No D2 conversion exists: none of these roots ever '
+    + 'evaluated in a flow, so there is no behaviour to carry over, and a run without a user needs a guard only the '
+    + 'author can choose.',
   acceptanceCriteria:
     'Run objectstack validate: it reports each refused root as expression-invalid at the flow, the node or edge and '
     + 'the slot, naming the root and its remedy. Replace each run-user spelling with current_user, guarded where the '
 
@@ -5701,14 +5701,15 @@ const STEP18_RATIONALE: readonly RationaleFragment[] = [
     id: 'flow-cel-unbound-root-refused',
     order: 92,
     text:
-      'It also refuses, at `objectstack validate` and the runtime publish gate, a flow CEL root the flow does not '
-      + 'bind — in a trigger gate, an edge, a `decision` branch, a screen field `visibleWhen` or a CEL value '
-      + 'envelope. Such a root fails every run that reaches it with an unknown-variable fault, and the build used '
-      + 'to pass it. The run-user spellings formulas, row-level security and the client accept (`user`, '
-      + '`ctx.user`, `os.user`) are the reachable case: flow CEL binds the run\'s user as `current_user` only, and '
-      + 'the refusal names it. A flow whose run can bind a name the reader cannot see is left unjudged, and no D2 '
-      + 'conversion exists: none of these roots ever evaluated in a flow. Its D3 record is the semantic entry '
-      + '`flow-cel-unbound-root-refused`.',
+      'It also refuses, at `objectstack validate`, a flow CEL root the flow does not bind — in a trigger gate, an '
+      + 'edge, a `decision` branch, a screen field `visibleWhen` or a CEL value envelope. Such a root fails every run '
+      + 'that reaches it with an unknown-variable fault, and the build used to pass it. The run-user spellings '
+      + 'formulas, row-level security and the client accept (`user`, `ctx.user`, `os.user`) are the reachable case: '
+      + 'flow CEL binds the run\'s user as `current_user` only, and the refusal names it. A flow whose run can bind a '
+      + 'name the reader cannot see is left unjudged — through a node, or through an entrance the stack declares that '
+      + 'hands it a record whose keys are not in hand — and so, for now, is every flow write at the runtime publish '
+      + 'gate, whose snapshot carries no actions or other flows. No D2 conversion exists: none of these roots ever '
+      + 'evaluated in a flow. Its D3 record is the semantic entry `flow-cel-unbound-root-refused`.',
   },
   {
     id: 'flow-decision-edge-branching-first-match',
@@ -13818,12 +13819,17 @@ const step18: MigrationStep = {
         + 'and the build door, which judged a flow expression\'s syntax only, passed it. The run-user spellings are '
         + 'the reachable case: formulas, row-level security and the client bind the run\'s user under user, ctx.user '
         + 'and os.user as well, and flow CEL does not, because a top-level user would collide with a variable or a '
-        + 'lookup field of that name. objectstack validate and the runtime publish gate now refuse such a root, naming '
-        + 'current_user for the user spellings and the in-scope names for any other. A flow whose run can bind a name '
-        + 'the reader cannot see is not judged: one with a script or connector_action node, a wait, subflow or map node '
-        + 'a resume can fold a bag into, a screen with no field list, a plugin node type, or a trigger object the stack '
-        + 'does not declare. No D2 conversion exists: none of these roots ever evaluated in a flow, so there is no '
-        + 'behaviour to carry over, and a run without a user needs a guard only the author can choose.',
+        + 'lookup field of that name. objectstack validate now refuses such a root, naming current_user for the user '
+        + 'spellings and the in-scope names for any other. A flow whose run can bind a name the reader cannot see is not '
+        + 'judged: one with a script or connector_action node, a wait, subflow or map node a resume can fold a bag into, '
+        + 'a screen with no field list, or a plugin node type; and one an entrance the stack declares hands a record '
+        + 'whose keys are not in hand: a record trigger or time-relative sweep on an object the stack does not declare, '
+        + 'an api trigger (the inbound hook hands the request body in as the record), a flow action on an undeclared '
+        + 'object, a map node whose itemObject is undeclared or absent, or a subflow or map parent that is itself such a '
+        + 'flow. The runtime publish gate does not give this verdict yet: it judges a flow write without the stack\'s '
+        + 'actions and other flows, so it cannot see those entrances. No D2 conversion exists: none of these roots ever '
+        + 'evaluated in a flow, so there is no behaviour to carry over, and a run without a user needs a guard only the '
+        + 'author can choose.',
       acceptanceCriteria:
         'Run objectstack validate: it reports each refused root as expression-invalid at the flow, the node or edge and '
         + 'the slot, naming the root and its remedy. Replace each run-user spelling with current_user, guarded where the '