| State | Description |
|---|---|
| Starting | Initializing the non-pipeline infrastructure then loading and starting the base pipeline. |
| Updating | Discarding all exo.spec.ae modules that have been loaded. Updating the OPS source code from git and merging in the PRE-OPS branch. |
| Loading | Load all of the exo.spec.ae modules. Determine the AE module hierarchy. Check for new software versions and schedule accordingly. |
| Running | Process the TODO list and initiate any periodic tasks as they become due. Command, Database, and Schedule pages will be responsive. |
| Archiving | Snapshot the database state for posterity. Keep 20 historical versions. |
| Gitting | Merge the user submission from the Command page into the PRE-OPS branch. Verify the code is compliant (exo/spec/tools/compliant.py) before pushing branch back to github. |