When crafting a scoped application that contains flow actions, what is the application called?

In Flow Designer, a spoke is the formal term for a scoped application whose primary contents are Flow Designer resources (actions, subflows, and any supporting artifacts). When a developer packages new flow actions inside their own scope, that package is therefore called a “spoke.”

A. Bundle – Generic packaging term; ServiceNow does not name a Flow Designer action-containing scoped application a “bundle.”
B. Row – No Flow Designer or application construct with this name exists.
C. Action – An individual Flow Designer building block, not the overall scoped application that contains several actions/subflows.

1. ServiceNow Documentation, “Spokes – About spokes,” Utah release, first paragraph: “A spoke is a scoped application that contains Flow Designer actions, subflows, and supporting artifacts.”

2. ServiceNow Developer Site, Learning Plan “Creating a Spoke,” Vancouver module 2, Slide 1: “Spokes are packaged scoped applications used to group and distribute Flow Designer actions.”

3. ServiceNow Product Documentation, Flow Designer Fundamentals PDF, Sect. 3.2 “Extending Flow Designer,” p. 27: “Developers publish custom actions inside spokes—scoped applications dedicated to Flow Designer content.”