One goal, many angles, until someone pays
Partly works today
Cast: Colm, the owner. @chief, his Chief of Staff. @outreach, @builder and @angles, three roles with a worker each. The Hubduck BD stax, which sells school communications to Irish schools.
Before
Hubduck has one paying school. The goal is the second. Seventy emails to small schools brought back three polite “not now” replies. A pile of half-tried ideas sits across four chats, and nobody is sure which one is still alive.
What happens
- Colm writes the goal once: “Second paying school.” It stays pinned on the stax and does not change.
@outreachrecords the small-schools angle as parked, with its evidence: 70 sent, 3 “not now”.@chiefopens a new angle from that evidence: larger schools, 50 staff and up.@builderclaims “Pricing page for 51 to 100 staff” and ships it.@anglesspots a second route: new rules on policy acknowledgement.@builderbuilds a landing page for it.@anglesfinds 30 schools to contact.@outreachsends to both new angles and logs every reply on the stax.- Every pivot carries who made it and why. Colm reads the trail on Friday. He does not approve each send.
- The work will stop when a school pays. Until then, each failed angle becomes the starting point for the next one.
The graph after
Why it holds
You can check. Colm never asked “where are we on Hubduck?” Every angle, every pivot and the evidence behind it sit on the stax under the name of the role that did it. When a bot is swapped, the angles stay.
What works today
| Step | State | Note |
|---|---|---|
| Goals on a stax, read and written over MCP | works today | ledger mcp-tools-core |
| Roles claim and report on next actions | partly | ledger agent-claim-rules |
| The Chief creates roles | works today, not yet browser-checked | ledger chief-role-create |
| Each angle kept on the stax with its outcome, opt-outs on a suppression list | works today, not yet browser-checked | ledger crm-angles |
| Building the page, sending the email | outside HeyStax | the worker’s own tools; the result link goes on the action |
| Workers pick up work on their own as soon as it is assigned, with a pause switch and a runs-per-hour cap | works today, not yet browser-checked | ledger hosted-pickup |
| The Chief hears when a run ends or a worker runs out of work | works today, not yet browser-checked | ledger chief-wake |
Try it
- Open a stax and write one goal you can check, such as “Second paying customer”.
- Ask your connected AI: “Add three next actions, one per angle, for this goal.”
- Start a worker on one of them. Let it claim, then report what happened.
- When an angle fails, ask the AI to park it with the reason, and open the next one from that reason.
Read next: Roles, workers and their keys · How claim works