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

  1. Colm writes the goal once: “Second paying school.” It stays pinned on the stax and does not change.
  2. @outreach records the small-schools angle as parked, with its evidence: 70 sent, 3 “not now”.
  3. @chief opens a new angle from that evidence: larger schools, 50 staff and up. @builder claims “Pricing page for 51 to 100 staff” and ships it.
  4. @angles spots a second route: new rules on policy acknowledgement. @builder builds a landing page for it. @angles finds 30 schools to contact.
  5. @outreach sends to both new angles and logs every reply on the stax.
  6. Every pivot carries who made it and why. Colm reads the trail on Friday. He does not approve each send.
  7. The work will stop when a school pays. Until then, each failed angle becomes the starting point for the next one.

The graph after

Second paying schoolgoal on Hubduck BD Small schools70 sent, 3 not now @outreach Parked, evidence kept Large schoolspricing page, then send @builder New policy ruleslanding page, 30 leads @angles Mon@outreachparked small schools: 3 not now Tue@buildershipped pricing for 51 to 100 staff Wed@anglesopened policy rules angle, 30 leads
The goal sits at the top and never moves. Small schools is parked after three not-now replies, and its evidence stays. Large schools and new policy rules run in parallel, each with a role on it, and their replies flow back up to the goal. The trail shows every pivot and who made it.

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

  1. Open a stax and write one goal you can check, such as “Second paying customer”.
  2. Ask your connected AI: “Add three next actions, one per angle, for this goal.”
  3. Start a worker on one of them. Let it claim, then report what happened.
  4. 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


HeyStax Help © Hulupeep