Example decision

CI passed. Dulvarn still said CONDITIONAL GO.

A concrete release scenario: payment retry logic changed, checks were green, but QA coverage did not match the impact. Dulvarn surfaces the gap before production.

Request beta accessView audit packages
Release decisionCONDITIONAL GO
Risk score
68 / 100
Why this release needs attention
  • Payment retry logic changed without matching regression coverage.
  • CI is green, but impacted tests do not cover the changed path.
  • Rollback plan is not linked to this release.
Recommended QA scope
  • Run payment retry regression.
  • Verify failed-payment recovery.
  • Check checkout telemetry after deploy.
Decision

Ship only after targeted QA validation.

Representative example · not live customer data

Walkthrough

What happened in this release

Dulvarn connects PR changes, CI signals and QA context into one reviewable decision — with humans in control.

  1. Step 01

    PR changes checkout and payment retry logic

    A pull request refactors coupon stacking and idempotent payment retries in the checkout service.

  2. Step 02

    CI passes

    All required checks are green. The pipeline shows no failing jobs or blocked merges.

  3. Step 03

    Dulvarn still flags risk

    Impacted tests do not cover the changed payment retry path. Rollback context is missing from the release record.

  4. Step 04

    Output is CONDITIONAL GO

    Dulvarn recommends targeted QA before ship — not a block, but not a blind GO either.

  5. Step 05

    Human makes the final call

    QA validates the recommended scope. Engineering ships only after targeted validation — with an auditable decision.