Document guidance for deciding at which layer a piece of logic should go about dodal HOT 5 OPEN

Approximate guidelines I think is fine. We're never going to be able to police something that's very strict

from dodal.

I think where you say ophyd-async in the above do you actually mean dodal @olliesilvester?

from dodal.

Yeah, I really mean creating the devices using the ophyd-async library, rather than putting it into the repo

from dodal.

I like this, my only question is how strict to make it? Do we want a prescriptive flowchart, a set of approximate guidelines, or somewhere in-between?

from dodal.

Other random thoughts on the topic:

• Things the science team are likely to want to read/edit are better placed in bluesky than EPICS
• ophyd-async must remain facility agnostic, no DLS EPICS naming conventions or EPICS support modules that are not on GitHub
• We may prototype in dodal and push to ophyd-async when it has been made more generic

from dodal.