CAN should inform the user of changes made after a command runs

CAN should build trust that it only makes sensible changes that are within its remit. It should also let the user build an accurate mental model of what each command does. For similar reasons, CAN will not change the file system without a user command.

When a command completes, CAN should inform the user of any changes made in simple language.

Backlinks

• CAN's scratch command should create a scratchfile if none exists
  • The scratch command within CAN is intended to prepare the scratchfile for writing a fresh note. If a scratchfile doesn't exist, it should create it and inform the user (CAN should inform the user of changes after a scratchfile is run).
• CAN's init command should inform the user when successful
  • CAN should always respond with the changes that have been made when a command is successful (CAN should inform the user of changes made after a command runs)