Aglet

Verify runtime configuration matches the reviewed release

Verification should prove that the runtime now uses the intended configuration and that the original behavior is covered. A new digest alone does not show every worker, region, or scheduled process has loaded it.

Check whether the outcome improved

  1. Compare safe identities

    Match reviewed revision, deployment context, runtime-loaded revision or digest, environment, and service. Record unavailable participants and whether they can retain old configuration beyond the current request.

  2. Observe the original path

    Check the request, job, data condition, or cohort implicated in triage for errors, successful completion, latency, retries, and downstream effects. Compare with the drifted and known-good observations.

  3. Cover delayed participants

    Wait through worker, cache, queue, or scheduled-task boundaries relevant to the drift. Apply the review rule and leave a follow-up when any participant remains outside the observed reload window.

What to carry forward

Verification should state aligned, behavior recovered, partially covered, or inconclusive with safe identity evidence. Close only when runtime participants and delayed paths are included; never use secret values to strengthen the conclusion. Recheck the redacted identity after the correction and exercise the path that exposed drift, including a fresh process or request when reload timing could matter.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow