Pick a proven path, 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.
A buyer pays for a factory product; checkout:resume wakes the run, the storyteller tells it, the meeting opens on /in, a head drafts the promise, and the order is filed on the board tagged factory and the product.
Someone asks for a product with a signal tagged factory; world:route hands it here, the story and the meeting follow, and a person accepts the drafted promise before any row is built.
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.
A URL becomes a client. Two doors, one graph. Shared in chat by an owner (no workspace on the payload): crawl the site, create the client workspace under the sender, populate its soul, confirm in chat. Pasted into a URL block (lib/site-builder: the funnel has already minted the sponsored workspace and read the site): write the soul so the chatbot knows the business, then build what the block chose — a movers site + quote desk, a store (catalogue, photos, twelve pages, shop assistant, test mode) or a five-page business site with its front desk — and park for a person to review. Approving publishes exactly what was built. Payload (URL block): workspace, builds (movers | store | site), facts, description, soul, businessName.
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 (checkout:started), wait an hour, then — if the buyer left an email — ask a person to confirm the checkout is still unpaid before the buyer is nudged to finish. Nothing reads a session's payment yet, so nobody is nudged without that confirmation.
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.
The site-builder intake's store: one sentence or a URL becomes a whole store — shop:build writes the catalogue with photos, prices and stocked variants, the twelve shop pages and the shop assistant, all kept private and every product a draft — then the run parks for a person to review what was read off the site. Approving puts the products on sale, opens the storefront in TEST mode, publishes the twelve pages and adds the order-confirmation and lead follow-up starters. Payload: workspace, description, facts (ShopBusinessFacts), and optionally products [{name, price in minor units, description}] — created under exactly those names and prices, the model filling only the gap to six — and heroPrompt, the prompt the hero image is drawn from.
The site-builder intake's business site: pages:build-site writes five draft pages (home, about, services, contact, FAQ) for the business from its own facts, with the template proof it cannot back removed and a front-desk chat on every page; a person reviews, and approving publishes exactly those five. Payload: workspace, facts (BusinessFactsCandidate), description.
One run builds a whole store: open the storefront, seed the twelve shop pages, read the seller's site when no facts were typed, make the hero, picture and create each proposed product (as drafts, each paired with its own image), fill the pages, save the store lifecycle, add the store's starter workflows, then a person reviews before the products go on sale and the shop pages go live. Nothing is public or buyable until that approval — and facts read from the site are candidates, so that review is also where they are confirmed. Payload: workspace, facts or url, heroPrompt, products [{name, description, price in cents, currency}], at most 6. The hero image lands in the media library; the pages do not use it yet.
Thank a buyer by email when their order is paid. It arms on order:paid, which fires once per order after the payment settles (payload: slug, oid, email when known, amountCents, rail). An order whose event carries no email stops at the check, never fails. The thank-you is sent as transactional: a receipt skips the newsletter-consent bar, never suppression.
A form on the store becomes a known person: identify the visitor from the email they left, then move them to lead. A lead with no email (phone only) stops at the check.
Ask a buyer for a review a few days after their order ships. It arms on order:fulfilled, which fires once per order the first time it leaves unfulfilled (payload: slug, oid, email when known). An order whose event carries no email stops at the check, never fails.
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.
A visitor lands from a credits ad and the centred chat sells the agents: it opens with what an agent does for their business, hears what they need, shows how it works, puts the credits link in front of them ($1 for 1,000), takes their email and moves them to lead. Pin it as the landing page AIChatBlock workflowId.
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.
The eight stages of an Education, Health and Care plan from request to transition, with the three statutory windows of the SEND Regulations 2014 (decision by week 6, advice by week 16, final plan by week 20) as delay steps counted in days. Cut from a worked plan and stripped of that young person's artefacts, so it is the road rather than the case: each step still names the sections of the plan it bears on.
A key's life on the server side: a registered address arrives, we read its live chain balance, and the run either takes the holder to credits or nudges them once and stops. The mint, the derivation and the keeping happen on the holder's device and are deliberately not steps — a signal that carried them would carry the key.
Call your own endpoint with what the buyer sends and hand back the result — the shape to publish at a price with workflow:publish. After cloning, replace the endpoint handle 'thumbs' with the name you registered.
Draw an image from the title the buyer sends and hand back its url — no endpoint of your own needed. Publish it at a price with workflow:publish; edit the style guidance after cloning.
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.
A chairman's meeting as a run, not a session: the board and ledger packed with no model, one thread opened, every ready card fanned to card-flow, cheap assistants digest each lane, a head thinks only where a question or verdict waits, astra refutes the wave, and the chairman decides the next wave or stops at the cap.
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.
A card-flow row as signals (v2): the router picks the model, the attempt opens, factory-builder builds, then the FREE gate parks for factory-hands before the paid factory-judge reads the build; a red gate or a FAIL retries by a new tasks:announce (attempt 2, then 3, then Opus once) and a PASS parks at land for factory-hands.