Simple unalterable "decision log" would be: 1)set up an email alias decisionlog@ . It mails to a folder people can read. This is the unalterable part. Digita

Simple unalterable "decision log" would be: 1)set up an email alias decisionlog@ . It mails to a folder people can read. This is the unalterable part. Digital signatures etc are not needed unless you're worried about your employees pwning your mail server. 2)Post emails in that folder to slack using one of the solutions here https://slack.com/intl/en-gb/help/articles/206819278-Send-emails-to-Slack https://slack.com/intl/en-gb/help/articles/206819278-Send-em... . Or don't, you know. Not everything has to be in slack. 3)Get beer. You're done In my experience much of the time when people say they need a knowledge hub/decision log/wiki etc those things are available but underused or not useful. The challenge is that when corporate knowledge gets past a certain threshold the amount of time needed to catch up on parts you've missed and the tendency for the usefulness of those information resources to decay over time comes to dominate. However you store your decision log, in a year you'll have hundreds or thousands of decisions in the log and entropy will rapidly set in.