Establish what is happening
Name the baseline
Record the reviewed configuration revision, environment, service, release, and time it was expected to apply. Use safe identifiers or redacted digests and never copy credentials or sensitive values into the brief.
Capture observed drift
List the setting, runtime source, observed revision or classification, and first known difference. Note whether the difference is confirmed, inferred from behavior, or not independently checked.
Bound the affected path
Describe services, cohorts, jobs, and environments that may have loaded the drifted setting. Separate a reporting mismatch from evidence that runtime behavior actually changed.
What to carry forward
Triage should state baseline, observed configuration identity, affected boundary, and safe evidence limits. Escalate when drift reaches a customer path or makes release verification unreliable; keep secret content out of all follow-up records. Capture a redacted configuration identity and its source, then state whether the difference affects routing, limits, feature behavior, or only diagnostic presentation.
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