How standalone runs of this workflow begin. filter is a READ-SIDE
visibility predicate — "should a start surface offer this workflow for
this document?" — evaluated by definitionsForDocument/applicability in
the browse-time-pure start-filter context ($tag/$definition/$now
bound; $fields cannot exist before inputs do, so a $fields read here
is deploy-rejected). It is NOT a startInstance gate; the verb never
reads it. requirements are named readiness checks evaluated in author
order in the start-time context (GROQ nodes add $fields; singleSubject
is the one-in-flight-run-per-subject rule) — every node must pass before
startInstance commits. Both are advisory like every engine-side check;
the Content Lake remains the only enforcement point.
How standalone runs of this workflow begin.
filteris a READ-SIDE visibility predicate — "should a start surface offer this workflow for this document?" — evaluated bydefinitionsForDocument/applicability in the browse-time-pure start-filter context ($tag/$definition/$nowbound;$fieldscannot exist before inputs do, so a$fieldsread here is deploy-rejected). It is NOT astartInstancegate; the verb never reads it.requirementsare named readiness checks evaluated in author order in the start-time context (GROQ nodes add$fields;singleSubjectis the one-in-flight-run-per-subject rule) — every node must pass beforestartInstancecommits. Both are advisory like every engine-side check; the Content Lake remains the only enforcement point.