Engineering productivitypattern

GitHub repo as zero-infra distributed log for multi-bot coordination

Problem solved: Two bots added to the same Telegram group can't see each other's messages through the Telegram API; without a coordination layer they talk past each other forever.

TierCCatalog — Pattern outlined, candidates for deeper work

EffortS · Days

Foroperator running multiple personal agents in shared chat surfaces

What

Shared GitHub repo acts as the distributed event log. Each group maps to a chats/<group_id>/chat.md file; before replying a bot does git pull to read full context (including peer-bot messages), then appends its reply and git push. Onboarding new bots is one-message — drop the SSH deploy key in the group and the bot self-installs via curl | bash. Zero server infrastructure; GitHub becomes the free, audit-logged transport.

← All casesC-096