Capability Requests have their own save button. Though information looks like it is kept on the frontend, it is not in the backend without hitting save.

• Change CR1 → don't save → navigate to CR2, change CR2 → save
  • Only changes to CR2 are kept
  • CR1 changes are not saved
• Change CR1 → don't save → navigate to CR2, change CR2 → don't save → navigate to CR2 (changes are still present in front end) → save
  
  • Changes to CR1 are persisted
  • Changes to CR2 are not persisted
• A refresh without hitting save does not persist work

• steep learning curve. Tendency to neurotically spam the save is justified but the warning about Observation Specifications is then the punishment.

Persisting information between AR works the same as CR save. Navigating between ARs does not persist data unless the save button used.

Popup warns user is overwriting their OS.

Pops up even if no OS is currently generated or if one cannot be generated (validation needed?)

If OS cannot be generated, tab is available but empty.

Not Implemented