Skip to content

Commit 554bea2

Browse files
committed
docs(skills): say when os validate judges a bare flow-condition name exactly
The flow-condition callout said bare names are judged "only while every node's bindings are declared"; the scope also stands down for an entrance that hands a record not in hand and for a contract-less screen, so it now says "only while the flow's bound names are provable". Same line count, same token reading. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WGufzfSZ55f7xwAfpfkPgY
1 parent d97d2e3 commit 554bea2

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎skills/objectstack-formula/SKILL.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -400,7 +400,7 @@ When migrating Salesforce-flavor metadata, apply these rules in order:
400400
> trigger record's fields, nulls included, to top level wherever no flow variable
401401
> or node id holds the name, so in a start, edge or `decision` condition a bare
402402
> `budget` IS `record.budget`: `os validate` judges either spelling (bare names
403-
> only while every node's bindings are declared) and a guard on one guards both.
403+
> only while the flow's bound names are provable) and a guard on one guards both.
404404
> What the start condition proves non-null is presumed at every edge and branch;
405405
> spell that guard `record.budget != null` — the runtime publish gate judges the
406406
> written flow alone and resolves no bare name. An unguarded null fails the

0 commit comments

Comments
 (0)