Pick a proven workflow, run it, and watch each step light up live. Every run teaches the system which branches actually work — so the path gets faster the more you use it.
Wondering where these fit? See the whole factory — how a message becomes a job, who picks it up, and where a workflow starts.
The ten gates of a deploy, in spine order — tree, credentials, typecheck, tests, build, smoke, human approval, migrations, ship, health. Each gate reports through deploy:event into the same run the deploy page reads, and the deploy tasks template files one open row per gate before the run starts.
Turn a business's real facts into a ten-page movers site — instantiate the pack, fill it with their name/city/license/pricing, then a human reviews before anything publishes.
Welcome a new client, get the contract approved, then provision their workspace.
A visitor asks to talk to someone: read the standing room first, hand them that room when a person is already in it, otherwise open their own and page the team.
A booking request waits for a human OK before the calendar event is created.
Draft campaign copy, review it, then publish across channels.
Triage an incoming ticket, branch on urgency, auto-reply or escalate.
One URL in - read the homepage, map the site, read the pages worth reading, and build a provenance-tracked company profile in the Foundation.
Someone shares a URL in chat → crawl the site, create a client workspace, populate the soul with their content, and confirm in chat.
Scrape today's top AI news, generate platform posts + images, then approve before publishing.
A buyer requests a session → pay at a `sell` step → the run resumes and delivers the booking once checkout completes.
When a contact confirms their subscription, welcome them, then follow up a week later.
When a checkout starts, wait an hour, then nudge the buyer to finish — unless they already paid.
A daily batch that re-engages contacts who have gone quiet for 60 days. Queries dormant subscribers and sends one re-engage email each through the suppression-checked send path.
When a trial nears its end, place an outbound voice call to check in, then wait for a human to review the transcript.
Wait, then send a follow-up; branch on whether the lead replied.
Route a campaign brief to the CMO — strategy, then copy — get a human OK, then email the audience.
Route a new lead to the CRO — qualify, branch on fit, draft a proposal, then email it.
Route an open ticket to the CXO — branch on urgency, auto-draft a reply or escalate, then send it.
When a customer is won, route to the CXO — welcome them, wait, then send the first onboarding lesson.
When someone passes the 24-word quiz, ask a person to confirm the words are written on paper, then record the paper backup on the wallet lifecycle.
A provisioned agent is bootstrapped but not yet discoverable. A person approves, then the agent is published on the internal-agent lifecycle.
An external agent has handed over its public address. A person confirms the key is stored in the agent environment, then the stored bearer is recorded on the external-agent lifecycle.
A capability is listed for sale. A person confirms the escrow payment landed on the pay rail, then the payment is recorded on the money lifecycle.
When a contact reaches a stage, mint a personalised tracked link bound to them and email it — they land on a page that already knows them.
Draft a social post with the social media manager, get a human review, then publish to connected platforms on schedule.
Take a published page or article and repurpose it into platform-specific posts. Agent adapts tone for each network, human approves, then posts go live.
Every Monday, the social media manager plans the week's posts from your content, brand, and campaigns. Drafts land in the social calendar for review.
Pull SERP positions for every keyword in seo_rank_configs once a week; snapshot results to seo_rank_snapshots and mark/warn the keyword→page strength path.
Run a DataForSEO OnPage audit on a target URL once a month; store the result in seo_audits and mark/warn the domain health path.
Run a product concept past a panel of synthetic consumers and get back a calibrated 1-to-5 purchase-intent distribution.
Turn a course brief into a published course — outline, approve, draft lessons, review, then gate access behind payment if the course is priced.
Create a product from chat, approve the pricing, mint a payment link, then announce the launch.
Turn a goal into a landing funnel — draft the page structure, create the page, approve it, publish it.
Watch a workflow's edge weights, propose one evidenced fix for the worst bottleneck, then apply it once a human approves.
When no surface has volunteered an identity, ask once — and never ask someone already identified.
The standing chat pipeline every workspace gets: a message arrives, the arithmetic router (world:route) picks the proven handler (highway) or falls to the CEO, then an agent answers. Pinned per page via ChatWidgetConfig.workflowId; unpinned chats use this default.
One workflow builds the site AND the agent from one set of facts, publishes both live in one call, then puts the mover on the Revenue Engine plan.
A form submit on the mover's site becomes a qualified, nudged lead that routes into the quote — the ELEVATE Identify/Engage stages, not a dead-end form.
A quote converts to a booked move with a real Stripe deposit — the ELEVATE Sell stage.
The move-day service arc runs as steps — a reminder, then a check-in after the move — the ELEVATE Nurture/Educate stages.
After the move completes, ask for a review, then a referral — the ELEVATE Share stage.
A visitor lands from the sovereign-keys ad and the centred chat runs the conversation itself — it opens with the key offer, hears what they want to sell, shows what the generator does, names the free/credits line, takes their email, and moves them to lead. Pin it as the landing block’s workflowId. Every visitor-facing line is an entity:reply (the one door that reaches a web chat); the two human steps exist only to wait for a reply. The copy is held to text/ad.md §4 — the page and this workflow must tell ONE story — and to §8, which bans the sentences this offer cannot honestly say.
Mint an arm-scoped tracked link, draft ad and social copy, gate the spend on one approval, then split the email by arm and announce the creative to the ads and social board.
Read a diff against what it claims: correctness findings with failure scenarios, the auth seam probed, the test lane named — then one human merges it or sends it back.
Decide the shape before anyone writes the diff — reuse verdict and stated tradeoff from the architect, the auth seam from the security auditor, then one human accepts the design.
Production is broken: blast radius established first, the smallest reversible mitigation proposed for a human to authorise, then the trap written down so it cannot recur quietly.
A sentence becomes work somebody can finish: the sizer answers first, and only where it refuses does the architect name the paths and write the one Proof: line that says what done would mean.
Weekly measurement of the gates and the suite — every number carrying the clock it came from — with the binding constraint named and a human deciding whether it is worth acting on.
Hold the line between "the cycles are done" and "the thing is live" — the five gates walked and the failing one named, docs reconciled to what actually shipped, then a human ships it.
A visitor gives one URL: it is read through the single hardened door, three readers take the page apart — what it says it is, which of its promises it actually supports, and which of its claims a crawl cannot verify — and the profile lands where the workspace agent reads it on every turn. The logo, the colours and the theme are drawn dark, because no receiver can reach them yet.
The deploy said green — now go and look: the live sha against the merged one for every worker, the route proven under the landing rule, the failing gate named, and only then is the attempt verified.
A FEATURE or SCHEMA sentence becomes rows, not prose: the spec skill writes the eight fields with deliverables as an array, and one child task is created complete per row — a spec that arrives as bullets creates nothing and fails the run rather than closing empty.
One tick of the factory, zero model calls: the six funs asked, one handler each — launch every ready child, name what is missing, park on a deadlock — and a close that refuses to read an empty board as a finished one.
A sentence becomes a promise somebody signed: recon reads what it touches, the AI states terms it will build and freezes them, the sizer answers, and where it refuses the architect writes one accept: per Want and the Proof: line that joins them. It ends at a person — the teller approves the frozen terms or rejects them, and a rejection dissolves the promise with a receipt rather than leaving the sentence half-owned.