Audit Your Routines and Retire the Ones You No Longer Use

Standing routines pile up quietly: a weekly check you no longer read, a daily summary that duplicates another one, a watch that keeps failing. A muse can audit every routine it runs for you, read-only, and show you which ones to keep, merge, slow down, or retire, with each change waiting for your yes.

What it does

You ask for a review of the routines, scheduled tasks, and standing instructions your muse runs. It lists every one: what it does, how often it runs, and roughly how much work each run takes. For each routine it gives an honest read on whether its output got used lately, whether it overlaps with another routine, and whether it runs more often than it needs to. It flags routines that keep failing, keep producing the same result, or run at times when you are unlikely to read them. Then it puts the suggestions in one table: keep, merge, slow down, move to a better time, or retire, with a one-line reason for each. For anything it suggests rewriting, it shows the improved instruction side by side with the old one. It can also point out one or two new routines that would save real time, based on what you actually ask for. Nothing changes during the audit. The muse waits for you to approve changes one at a time.

How to use it

1. Ask for a read-only audit of every routine and standing task, and say plainly that nothing should change yet.
2. Read the full list first. A routine you forgot you set is the main thing this audit is for.
3. Check the table against your real habits: what you read, what you ignore, and what annoys you.
4. Approve, reject, or adjust each suggested change one at a time.
5. Repeat the audit every few months, or whenever the reports start feeling like noise.

What you need

• A muse with at least a few routines or scheduled tasks running
• A few minutes to read the list and decide, one change at a time

What to watch for

• It is normal if the size of the list surprises you. Routines are easy to start and easy to forget, which is the whole reason to audit them.
• Do not retire a routine just because you skipped its output once. Look for a pattern over several runs.
• Keep approvals one at a time. A bulk yes to a page of changes is how a useful routine gets deleted by accident.