Self-modifying playbook
The problem
The rules the support agent follows change constantly — a flavour goes out of stock, a promotion starts, a policy needs tightening. Every change meant opening an editor, editing a markdown file, committing, and pushing. For a plain-language instruction sent over Telegram, that's a lot of friction for a one-line policy tweak.
The replay
Under the hood
A plain-language Telegram message is classified as either a documentation-only policy change or a change that requires real code. Documentation changes are edited directly, committed, and pushed — the deploy pipeline picks them up automatically, no separate release step. Anything that touches actual application logic is never edited by the agent; instead it raises a GitHub issue so a human makes the code change deliberately.