A person or one employee owns pipeline stages

The idea

Plan, build, verify and deploy stages each have an owner; a person owner must approve or send back before work passes, and setup can make one AI employee responsible for all four.

The problem
Work could pass a stage without the accountable owner deciding.
Why it matters
No stage passes without its owner's decision, and a solo-employee org has clear responsibility.
Where it stands
In production as of

Recorded evidence

  • Production · One explicit choice, one config event, phone and desktop reload

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

Where it lives in the product

  • People on the chart and teams

    People hold titles and chart positions, AI workers can report to a person, and teams group workers and people across the chart.

  • Approvals on web, WhatsApp, Slack and Teams

    A governed action waits for an approval that eligible people decide on the web, WhatsApp buttons or Slack/Teams direct messages; the requester never decides, and owned resources are approved by their owner.

  • Flow signal triage

    Ideas, requests and problems arrive as signals. Rules decide each signal at once, using the triage employee's accepted lessons, while System One is measured next to them. Each decision becomes held work or started work.

  • Main-line CI watch

    The build stage owner reads the CI result of each watched branch head through the gateway. A red head opens one urgent incident, and a green head records the recovery time.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.