change_tracking_text_editor_1: Create Workflow

I'm wondering if the "Change Tracking Text Editor" might be too difficult to use for regular users for the following reasons:

• input.txt file needs to be created/present
• output files can't be overwritten existing text can't be loaded, but instead must be copied into the input.txt if the editor shouldn't start out empty
• little control over where files are saved to, so organizing a text repository would require manual actions and discipline

These requirements are in place for a reason, but regular users and the lack of the system engine prevent the editor from being fully usable as a standalone tool. Therefore I already started with a workflow, that is supposed to do the following things:

• Allow the selection of an output directory to receive the files that get written/saved/generated
• Allow to select an input file to be loaded into the editor
  • Should get copied to the output directory as backup
  • If plaintext or unknown, load as initial text, ideally with an option to add it as the first instruction in the output change history
  • If a change history, execute it to arrive at the last, most recent text revision, open that as initial input, and then append change operations from the editor to the existing history, which might require a change history concatenator capability.