We describe behavior we expect of html scripts in their role as nodules in the connectome. We draw on insights offered in Automation as Team Player
A nodule must be clear as to its purpose and aware of how this might fit into workflows in the present and the future. A nodule is improved by meeting its off-purpose responsibilities in the simplest possible way. The smallest whole with potential to delight.
A nodule begins execution when a page containing it is rendered into the lineup. A nodule must assess its context and report through counts or other high level assessment the information it finds available.
A nodule performs complex computations when requested via button press. A fast computation still waits for a request before opening additional pages or downloading files. A slow computation provides some indication of progress, possibly dots, more likely summary-details of progress that can be checked for validity.