Give your record a shape.
A title, a priority, and a review flag are enough to make a meaningful decision. Keep the inputs focused on what the route actually needs.
A visual way to turn incoming records into thoughtful review paths and clear handoffs. Start small. See exactly what happens.
Interactive concept. No account or external connections required.
Does this need another look, or is it ready to move? Start with a recipe and make the rule your own.
Collect the working title and review flag, then route the draft to an editor when another look is needed. A cleared draft moves to the ready branch.
Open this recipeRelay makes a small workflow tangible. Inspect the input, choose the rule, and test the outcome before anything moves beyond your browser.
Read the working guideA title, a priority, and a review flag are enough to make a meaningful decision. Keep the inputs focused on what the route actually needs.
Use a review flag, an explicit priority threshold, or a required review. The active branch explains itself in plain language.
A local test shows the record, selected route, and reason together. Save the configuration or copy its JSON to keep the thinking portable.
{
"record": "Autumn studio notes",
"route": "Editorial review",
"reason": "The record needs review.",
"localOnly": true
}No. Relay is a local workflow demonstration. Testing a route only evaluates a record and shows its branch. It does not send messages, move files, or connect to external services.
Edit the title, priority, review flag, rule type, and priority threshold. The canvas and reason update immediately, and a local test gives you a concrete output record.
A saved configuration stays in this browser’s local storage. You can also copy the route as JSON. No credentials or external account information are requested.
No. The pricing page is an illustrative usage model for this fictional product. Its calculator shows how a base allowance and additional operations can be explained. There is no checkout or payment.