How work runs
Playbooks, triggers and handoffs
A playbook says what an agent does. A trigger says when. A handoff passes work to the next agent.
Playbooks
Written in plain language, read by people and agents
A playbook says what the agent does, step by step, and where it stops for a person. You can read it the way you read a job description.
The playbook is part of the agent's record. Ready-made agents come with one. Yours starts from a blank page or from the Architect.
Changing a playbook goes through review and a canary that rolls back on its own.
playbook / lead qualifier (example)
- Goal
- Qualify new inbound leads for the sales team.
- When
- A new lead record is created.
- Steps
- Check the company against the ideal customer notes. Score the lead. Write the reasons on the record.
- Hands off to
- SDR Outreach, for leads that qualify.
- Waits for a person
- Before changing who owns a lead.
Triggers
Six ways work starts
Every trigger becomes work the kernel schedules. Nothing reaches your systems without passing the gate.
01
A schedule
Every weekday morning, or the first of the month.
02
A webhook
A signed vendor webhook, verified and deduplicated.
03
A changed record
A deal moves stage, a ticket is reopened, a lead is created.
04
A mention
Mention an agent and it acts for the person who asked.
05
A handoff
Lead Qualifier hands a qualified lead to SDR Outreach. The outreach email waits for the rep to approve it.
06
A person's ask
Ask an agent for something directly.
Frequently Asked Questions
Put an agent on real work, with people in charge
Design partners run one real workflow on OrchKernel and work directly with the engineers building it.
OrchKernel is source-available and self-hosted.