Suggest a Tool, Node or Workflow

🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.

What are you suggesting?

Please choose what you're suggesting.

Working title

Please give it a short name.

Regulation, standard, or domain (optional)

What framework or spec does it map to? Helps us place it in the right cluster.

What goes in? (optional)

The input a user would bring. If it's a file (xlsx, XML, JSON), say so.

What should come out? (optional)

Describe it

Please describe your suggestion.

Email for follow-up (optional)

Only if you want us to reply. Leave blank to suggest anonymously.

This opens your mail client with the suggestion pre-filled. Nothing is sent from your browser.
Or email us directly: [email protected]

✓

Suggestion ready to send

Your mail client should have opened with the details filled in. Hit send and it's on its way. Thank you.

Before you suggest

Check it isn't already built. Browse all tools or the workflow catalog first. If something close exists but falls short, tell us where it stops.

What makes a strong suggestion

🔧 Tool

One job, done in the browser, no server. Name the calculation or check and the code list it needs. Example: CSDR penalty rate lookup.

🔗 Node

A single deterministic step: same input always gives the same output. Give the inputs, the rule, and the output. It becomes a verifiable, hashable compute node.

⛓️ Workflow (chain)

Several nodes in order that produce one signed artifact at the end. Example: validate → score risk → export mandate. Tell us the steps and the final deliverable.

📥 Round-trip data

Have an xlsx or a state file you want read in, transformed, and handed back changed? Say what the file is and what edit you expect. We're actively looking at bidirectional import.

Direct email

Prefer to just write it out? Reach us directly.

[email protected]