MaruCheck
Get started
After release

Production feedback

Bring a production failure back to the proof loop without uploading source or letting telemetry silently rewrite product intent.

The trust boundary

  1. Your producer sends structured exception metadata with a stable event ID.
  2. MaruCheck binds it to the project token and an exact commit when available.
  3. Repeated fingerprints aggregate; exact delivery replays do not inflate counts.
  4. A reviewer confirms the root cause and links a real regression test.
  5. Only then does the failure become active QA Memory.

Send one event

Use the one-time project token from the connection flow. The idempotency header must exactly match the event ID in the JSON body.

Terminal
curl --fail-with-body https://marucheck.dev/api/v1/production-events \
  -H "Authorization: Bearer $MARUCHECK_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: evt-prod-0001" \
  --data-binary @production-event.json

Review before memory

Open the production-feedback queue in the dashboard. Approval requires a confirmed root cause, Vitest or Playwright adapter, stable regression ID, and project-relative test path. Rejecting the proposal creates no memory and no test link.

Delivery rules

  • New event IDs return 201.
  • An identical retry returns 200 and preserves the occurrence count.
  • Reusing an event ID with altered content returns 409.
  • A project token may send at most 60 events per minute.
  • Production aggregates are retained for 90 days.