Direction still matters when you are away from the work screen
People need to set direction and check results even while away. Instructions and reports on progress or problem causes keep those decisions connected to the team’s work.
Marblo’s Telegram conversations with the orchestrator provide that connection. During the hypemarc.com work, the CEO’s direction led to site updates and a deployment report.
Give instructions while away and receive progress and cause reports
Through Telegram, you can give the orchestrator instructions while away and receive reports on progress and problem causes. Use those reports to follow the work, understand problems, and communicate further direction without returning to the work screen.
In practice: the CEO's direction becomes site updates
In this hypemarc.com work, the CEO used Telegram to give direction for replacing examples, creating the build note series, and updating version labels. The orchestrator created and assigned tickets under that direction, reviewed the results, and merged the changes. It then reported the deployment result through Telegram.
Telegram supported both the initial direction and the result check. Between those conversations, workers carried out the assigned tickets and their results passed through review and merging.
| Stage in this work | Role actually performed |
|---|---|
| Setting direction | The CEO used Telegram to direct example replacement, build notes, and version label updates |
| Carrying out the work | The orchestrator created and assigned tickets, reviewed results, and merged changes |
| Reporting the result | The orchestrator reported the deployment result through Telegram |
Why it helps: connect direction and result checks through conversation
Human direction and result checks stay connected to the workflow. The CEO gave direction through Telegram; the orchestrator turned it into work and reported the deployment result.
Follow what happens after an instruction. In this example, site changes progressed through ticket creation, assignment, review, and merging before the deployment report returned.
When to use it
- When you need to communicate direction to the orchestrator while away
- When you want reports on progress and the causes of problems
- When you want to check the results of directed work, such as site improvements, through conversation
Evaluate what work followed the instructions and what result was reported.
In this series
- Marblo Build Notes 1 — The Closed Loop Release
- Marblo Build Notes 2 — Completing a Mission with the Closed Loop
- Marblo Build Notes 3 — Agent Mosaic
- Marblo Build Notes 4 — Orchebrain
- Marblo Build Notes 5 — Web Tabs
- Marblo Build Notes 6 — Merge Train
- Marblo Build Notes 7 — Multiple AI Accounts
- Marblo Build Notes 8 — Risk-Based Independent Testers
- Marblo Build Notes 9 — Telegram Conversations with the Orchestrator