Start with the information that matters.
The demonstration record has three fields: a working title, a priority between one and five, and a flag indicating whether review is needed. These fields are intentionally small. They are enough to show a real decision without burying the logic in a complex data model.
The record preview updates as you edit. A title is required before a local test or save, because an unnamed result is difficult to interpret. The priority labels provide context, but the stored value remains a number.
Three rules, one clear question.
- Review flag: choose the review branch when the record is marked as needing review. Otherwise choose the ready branch.
- Priority threshold: choose review when priority is equal to or above the selected threshold. Equality is included.
- Always review: every record takes the review branch, regardless of its flag or priority.
The priority threshold control appears only when the priority rule is selected. The reason beside the canvas states the exact comparison or condition that selected the branch.
priority = 4 threshold = 4 4 ≥ 4 → Priority review
Try the route before the handoff.
Run local test evaluates the current record with the selected rule. The output contains the record title, the human-readable route name, the reason, and a localOnly flag. The selected output node gives a short visual response when motion is allowed.
Changing any input clears the previous test output. This avoids presenting an old result as if it belonged to the new configuration. The highlighted branch and explanation continue to update immediately.
Keep the configuration portable.
Save route stores the configuration in this browser’s local storage. Opening the studio without a recipe query restores a valid saved route. Opening a specific recipe starts from that recipe instead, so experimenting with a new example is predictable.
Copy JSON reveals a read-only text area and attempts to copy the same configuration to the clipboard. If clipboard access is unavailable, the text remains selected and can be copied manually. Storage and clipboard failures produce visible feedback instead of a silent success claim.
A deliberate local boundary.
Relay is a fictional workflow product. No external integrations, messages, files, or accounts are connected. A review branch is a local result, not a notification sent to a person. A ready branch does not publish content or move a document.
The two scenario stories are original examples, not customer testimonials or business results. The pricing calculator is an illustrative model with no payment or checkout. The site is complete as a local demonstration, with its limits made clear at the point of use.
Open the studio