ClawGuard Crash-Safety Triage — intake

Tell us what to test

This collects only what delivery needs: the workflow, the one side-effect path, the boundary you suspect, and how to reproduce the failure. The 48-hour delivery window starts once this is complete and received.

Before you paste anything

Do not send production credentials, API keys, tokens, or real customer data. Export or describe the workflow with a redacted or synthetic payload — the crash boundary is what matters, not real secrets.

Contact Your name Email This is how delivery will reach you — sent to fulfillment as your contact handle. Company optional

The workflow What kind of workflow is it? What are you giving us? Paste it here, or a link to it Redact or synthesize any real secrets and customer data first.

The side effect and boundary What kind of side effect is it? Describe the one side-effect path we should test E.g. "webhook node calls our billing API's /charge endpoint." Which boundary do you suspect? Best guess is fine. This triage only tests one of these five boundaries, so if you're genuinely not sure, pick the closest one and explain the uncertainty below — that's useful triage input too. How do you reproduce the failure today (if you can)? Steps, timing, or "we can't reproduce it reliably yet" is a valid answer. Anything else we should know? optional

I confirm the material above has no production credentials, API keys, or real customer data.

Your submission (JSON)