The three parts of a Flow answer different questions:
transitions what may happen
targets what counts as done
entries which target this invocation pursues
A Flow may contain several marked targets, such as published-pr and
safely-abandoned. Each entry names exactly one target. Boatstack carries that
program-scoped target through resolution, prescriptions, receipts, recovery,
and replay.
An entry may also declare typed inputs. The software-delivery inbox helper
requires exactly one eligible Markdown plan. Input resolution happens before a
managed run is created; zero or multiple plans stop with a typed blocker.
Targets are predicates over declared facets. They do not select a hard-coded Boatstack mode. The supervisor chooses admissible, target-coreachable transitions from the repository's declared relation.