EXIT audit: teach every bot when to stop, not just how to start

Run an EXIT audit across my Grok Bot team.

Find every active Bot and routine that performs recurring tasks, monitors something, follows up with people or works towards an outcome.

For each one, evaluate these four EXIT rules:

E — END CONDITION

Define exactly what success looks like. Identify the event or result that should mark the job as complete and stop further work.

X — EXCEPTIONS

Identify situations that should immediately stop or pause the Bot and hand control back to me, including unexpected replies, changed circumstances, errors or decisions requiring my judgement.

I — INACTIVITY LIMITS

Set appropriate limits on retries, follow-ups, elapsed time and repeated attempts that aren't making progress. Identify when a job should stop rather than keep consuming resources.

T — TERMINATION CONFIRMATION

Define how the Bot records why it stopped, what it completed, what remains unresolved and whether anything needs my attention.

Now:

1: Review each Bot and routine against all four EXIT rules. Show me which protections already exist and which are missing.

2: Flag jobs that could run indefinitely, repeat unnecessary work or continue acting after their original purpose has been fulfilled.

3: Recommend specific EXIT instructions for each Bot and routine, prioritised by risk and wasted effort.

4: Preserve all existing safeguards and approval requirements. Do not interrupt or modify any active job without my approval.

5: Present your findings and proposed changes in one report. Wait for my approval before implementing anything.

Never send, post, spend, or buy without my explicit yes.