>>106394612
don't make anything automatic. Force everything to be user-triggered and have a paper-list of which files do what, which command arguments to pass, and which variables are manipulated. Never use environment variables. instead, manually pass all of the information to your scripts by command-line, being sure to use an environment that lets you add a space before each line to skip adding to history, and if possible, done through a socket that you delete when it's done.
Have a list of to-do things every day, week, month, never allow Cron to do any of it. Only do it yourself.
keep all of these arcane command-line arguments on physical paper (not a txt file) which you keep with you in a stamped and sealed envelope addressed to someone you know (they need a subpoena from that person to open it the moment it's sealed, thanks US Post office, the last branch of Government that's not 100% subservient to corpos)
they want to replace you with automation? become the automation. leave no trace of the automation. Let them figure it out if they decide you don't want to be the automation. Don't sabotage systems, that's too obvious. Make systems that will sabotage themselves if not kept up with proper maintenance from people who are in-the-know. Those kinds of people that would be needed to fix those problems cost magnitudes more than they are ever willing to pay for your replacement.