I'm not sure what would be most idiomatic, but if there were like "lifecycle" triggers, for example, like spring's ApplicationContextStartedEvent or something. that is my reference point. in spring, you get start, refresh, then stop, then closed, iirc. but a lot of stuff is just simply handled through the bean framework. you can register yourself as a bean which depends on other thing, or register beans of a type which other things depend on, and establish a startup order like... run my migration first, then create the dagster ops/jobs/etc