What We Actually Ship With MissionControl

What We Actually Ship With MissionControl Two days. Twenty-one commits. English in, pull requests out. If you're joining mid-series: Post 1 covered the 16-hour build — Telegram bot in, pull requests out, ports-and-adapters architecture. Posts 2 and 3 were the bug safari that followed, including a $5.84 task that produced zero useful work and forced a rethink of the entire trust chain. This is what the system looks like after surviving all of that. The Interface MissionControl runs as a Telegram bot. No web UI. No dashboard. You message it, it does work, it messages you back. Every interaction fits in a chat bubble. Send a task from your phone while walking the dog, get a PR link back before you're home. That constraint — everything must fit in a Telegram message — turned out to be a feature, not a limitation. The full command set: /task <description> — Queue a task against the default project. The agent picks it up, creates a branch, does the work, pushes, and opens a PR. /task slug: <