Inside the release decision
See what it takes to trust a critical workflow.
Six workflow evaluations. Each follows a specific failure through the system, the checks that would expose it, and the evidence a release owner needs to make a decision.
These guides present evaluation methods rather than reports of completed customer engagements.
Start with the question you face.
6 evaluations · English editions
When a payment times out, can checkout safely retry?
Follow one payment through a missing response, a retry, and reconciliation. See the evidence a release owner needs before the change reaches more stores.
The acceptance criterion
One intended capture for the agreed amount, connected to a defined order resolution.
Does an approved client workflow stay approved when its inputs change?
An approval belongs to the work that was reviewed. Follow an amended client calculation to see whether the final delivery still honors that decision.
The acceptance criterion
A material amendment follows the agreed fresh review rule before delivery.
A certificate is revoked. What does the relying party see?
The authority has changed the certificate’s status. Follow the response through publication, caching, and the consuming application to see which decision the evidence supports.
The acceptance criterion
The application recognizes stale evidence and follows the configured disposition instead of treating it as current status.
Reuse the acceptance method. Keep each client's evidence separate.
A shared test can pass while the client workflow fails. Follow one interface change through its acceptance conditions, execution boundary and delivery handoff.
The acceptance criterion
The acceptance check follows the request to its final state and records the rejection. A receipt acknowledgment cannot produce a passing workflow result.
After the plant connection returns, is the order still in the right state?
Connectivity can recover before the business state does. Follow a held manufacturing order through delayed messages and repeated delivery to see what a release review should establish.
The acceptance criterion
The newer authoritative hold remains effective until an authorized quality decision removes it. Late arrival does not make the older release event current.
A detection update should not change who can see the event.
A rule can detect the right activity while its event reaches the wrong tenant. Trace both detection and ownership through one shared processing change before approving the release.
The acceptance criterion
The record retains Tenant A ownership through processing. Missing context follows the agreed rejection rule, and Tenant B receives no protected content.
From the evaluation to your system
Bring the workflow you need to trust.
A Reliability Sprint puts one critical system under scrutiny. Agree the scope, exercise the relevant failure paths, and leave with evidence, reproduction steps, and prioritized recommendations.
Paid and scoped to one system. Scope and price agreed first. Seven days is typical, with timing confirmed during scoping.
