Primitives / Interaction

What a parent decides: helpers

A Behavior reports what a person did, and the Bundle applies it. A parent never builds those Messages: when the parent itself decides something, it calls the Bundle's helper, which runs the same update with the placement's args.

BundleHelpers on the placement
Selectionactivate(id), select(id), range(id, order), replace(ids), clear()
TreeNavigationfocus(id), open(id), close(id), toggle(id) (open or shut by the tree's own state)
RovingTabindex, ListNavigation, GridNavigationfocus(id)
Typeaheadclear()
LiveAnnounceannounce(text, politeness?)

Each is an Update.Step of the parent: Picks.helpers.activate(id)(model) in update, after the placement Picks = Parent.at(Bundle.declare(Selection.bundle, 'picks'), { args }). A control the parent draws for a child, such as a tree row's expander, sends a Message of the parent's own (ToggledRow({ id })), and update calls Nav.helpers.toggle(id). That keeps every fact the child applies inside the child, which @foldkit/oxlint-plugin's no-child-message-construction-in-root checks. Press, LongPress and DismissLayer have no helpers: everything they apply is an input event.