Open-source report-resolution workflows
Safest Resolve keeps each accepted report with its evidence, owner, decision, application action, messages, and appeal. Your team defines the route and the points where a person must decide.
Apache-2.0 licensed. Runs in your Cloudflare account.
The report workflow
Every step adds to the report that started the work, so an operator can see what happened and why.
Store reports from your product, a public form, or the server API, then return a tracking reference.
Run the published routing rules, assign a queue, and record why the report went there.
Collect the evidence the policy asks for, assign human review where required, and record the decision.
Wait for the application to confirm the action, send the right updates, and keep any appeal with the original report.
Inside Safest Resolve
Open a report to review its evidence and policy, or move to routing, the read-only assistant, and team access from the same workspace.
Customer-owned deployment
The installer creates the runtime, storage, queues, workflow engine, and operating controls in your account.
Your application keeps its own data. Safest Resolve requests named fields through signed, versioned connections when a workflow needs them.
The setup plan names every resource before deployment.
Workflow safeguards
Safest Resolve returns a tracking reference only after the report has been stored.
Sensitive, uncertain, contested, and consequential decisions require an authorized reviewer.
An appeal adds a separate human review without rewriting the decision that came before it.
Use cases and implementation
See complete report workflows, deployment steps, and the product integration from intake to action.
Start with one report
Tell us where the report enters your product, what evidence a reviewer needs, who decides, and what the product should do next. We will use that real path for the first conversation.
