ESC

Claude

Coding team - claude.ai, claude code and me

Coding team - claude.ai, claude code and me

The three-role model: a better way to build software with AI

There is a failure mode that almost everyone hits when they start building seriously with AI coding assistants. It goes like this: you have an idea, you describe it, the AI starts writing code, you react to the code, the AI adjusts, you react again, and somewhere around the third or fourth iteration you realise the thing being built has drifted significantly from what you actually wanted. The code is fine. The direction is wrong. And because the AI is responsive and capable, it just keeps going — confidently, productively, in the wrong direction.

Early OpenClaw Multi-Agent Organisation Blueprint

Early OpenClaw Multi-Agent Organisation Blueprint

Hawk Inc. — OpenClaw Multi-Agent Organisation Blueprint (v2.0)

Owner: user (Your Name) Infrastructure: Minisforum X1A1 (+ 2013 MacBook Pro Primary Hub: OpenClaw Gateway (single process, multi-agent) Operating Philosophy: Right Model, Right Task — Cost-Conscious, Data-Sovereign


Agent Name Registry

All agent names, Telegram bots, and emojis are configured. Each agent has its own Telegram bot with dedicated routing via bindings.

RoleAgent IDNameTelegram BotEmoji
CEO / OrchestratorceoHawk@botname-CEO_Hawk_bot🦅
Executive AssistanteaDi@botname-EA_Di_bot❤️
EngineerengSaeed@botname-ENG_Saeed_bot🔧
Finance / SecurityfinCraig@botname-FIN_Craig_bot💰
Social MediasocialEleri@botname-SOCIAL_Eleri_bot💬
General Purpose / DogsbodydougDoug@GrantsClaw_bot🐈
Heartbeat (background)heartbeatDoug_Heartbeat— (no bot)

Critical Corrections from v1.0

The original blueprint contained several fundamental errors about how OpenClaw works. This version corrects them: