Recipes by Category

Every recipe is cross-element by design — that is the point of a recipe. This index groups each one under the element category it best showcases, so you can find a worked example near whatever you are building. A recipe listed under one category almost always pulls in elements from several others; follow the links to see the full combination.

Categories follow the chemistry taxonomy — see the Chemistry pillar for the category index, and each element page at /docs/chemistry/:category/:type.

Foundation — circles & tenancy

• Bootstrap a Personal Circle — the first recipe: how a circle comes into being and what you get for free.
• Multi-Tenant SaaS Skeleton — circle + circle-ref + auth-policy + api-token for per-customer isolation.

Agents — autonomous workers

• Agent Swarm Orchestration — a lead triformer delegates to worker agents, tracked on a board.
• Evaluator-Gated Agent Loop — triformer + evaluator as a self-correcting, rubric-graded loop.

Actions — executable steps & humans

• Human-in-the-Loop Approval — an automation pauses at a hitl gate before a consequential action runs.

Apps — orchestration & UIs

• Self-Documenting Workflow — an automation renders its own topology into a diagram.
• Internal Dashboard — view + sql + board + automation for an operations console.

Intelligence — labs that hear, think, speak

• Voice Assistant — the lab compound: ears transcribe, the lab reasons, the mouth speaks.
• Branded Voice Content — brand + prompt + lab + mouth for on-brand copy spoken in a consistent voice.

Tools — browsers & platform surfaces

• Authenticated Browser Scrape — a cookie-jar bonds to a chromeless browser to read behind a login.

Data — storage & retrieval

• Knowledge Graph from Documents — document + entity + organizations + graph lift relationships out of prose.
• Event-Sourced Audit Log — queue + timeseries + document for an append-only, time-keyed record.
• Support Assistant — document + vector + triformer for a searchable knowledge base.

Frontend — what users see

• API-to-SPA Dashboard — http + queue + sql feeding a custom spa.
• 3D Product Viewer — a three-d (Bevy→WASM) viewer backed by a files asset store.

IO — the outside world

• Realtime Slack RAG Assistant — a slack trigger → vector retrieval → lab answer.
• Scheduled Report Pipeline — schedule → sql/timeseries → document → email/slack.
• Scheduled Data Sync — schedule → http fetch → sql upsert on a timer.
• Multichannel Inbox — slack/discord/teams/email fan-in to one board.
• Realtime Collaborative Canvas — a websocket pushes live edits to a shared diagram + graph.

Connectivity — wiring elements together

• Wire Fan-In — multiple io triggers → queue → rate-limit → lab, carried by wire.

Modifiers — policy as data

• ICP Lead Qualification — an icp rule set filters leads, matched by a sales-board.

How to read a recipe

Each recipe states the problem it solves, the elements involved (linked to their /docs/chemistry/:category/:type page), a step-by-step build grounded in real operations, and an honest “what this shows” framing. Nothing in a recipe claims a capability an element does not actually have — if a step names an operation, that operation exists on that element.