Spent the whole day making my system more robust
Fable access got extended by another week or so. Yay! So obviously, I had to use its superpower to judge my ‘brain’ (the vault of files and code I have been building to train my AI to cater to my requirements more closely and autonomously).
It found several areas to improve, along with the recommendations from the first agent team meeting.
We spent the whole day tightening screws across various steps of the process, including:
- Catching when Claude started drifting, so we could start a fresh session and not lose context-based behaviour.
- Adding self checks for each script where fake violations were planted to confirm the ‘alarm’ was actually working.
- Building a monitoring dashboard for system health that stays live and is built from the files in the vault (so no duplication and no drift risk).
They all worked like a charm. I’d highly recommend anyone getting frustrated that their AI starts deviating from its original behaviour to do this:
Add a line on top of your Claude.md (or equivalent markdown file):
Drift canary: begin every response with Keyword · [focus] · turn N (chat and every agent’s final message). Its absence, or a frozen/stale tag, is my signal that adherence is degrading. NEVER automate it: the fragility is the instrument; a canary that cannot die tells me nothing.
Essentially, each time the AI responds it will first say the Keyword, followed by the question you are asking and the turn number, i.e. how many times it has replied to you in that session.
If the AI starts drifting, you will notice it doesn’t show those things, and that is your signal to clear or start a new session. For me this happened after the 40th turn, but it all depends on the depth and length of your conversation.