Revenue operations

Fan-out · branch and join · scheduled

Every lead is scored on its own event, so a batch of twelve is twelve independent pieces of work that the engine gathers back into one answer. Above the bar the lead goes to an AE with a fifteen-minute SLA; below it, to lifecycle marketing. Both paths write a record.

The nightly sweep asks three questions of the pipeline at once — untouched, no next step, past its close date — and merges the three answers with an all join, which fires once wherever the branches happened to land.

How the graphs run

1. One event per lead

   Score, route, record, gather — none of it in a loop you wrote.

2. Three filters running concurrently

   Merged by a join whose state lives in the database.

3. A Monday-morning review

   It publishes four panels and a written commentary.

4. A commentary node with an error branch

   The page is built even when the model is not reachable.

On the canvas

flow:forEach · flow:collect · flow:merge · views:* · ai:prompt

It ships with the product

This project ships with DjiniousWorkflow. One command seeds it, another runs every graph in it, and the captures here came out of those runs.

Where a graph leans on a fixture rather than a live system, it reads the fixture where your deployment would read a database — swap the node at the top and the rest of the graph does not change. The engine work — the fan-out, the gather, the approval, the publish — is the product’s own.