Engineering lens demos/eng-10-release-evidence.html Fictional data ← all artifacts
Release evidence · CHG-88412

Release evidence: order-gateway 2026.06.1

change record CHG-88412 · Project Lighthouse · generated 10 Jun 2026, 20:05

ABC Corp is a fictional company. Every name, number and date is invented. This is a reference artifact generated with an LLM coding agent; the brief that produces it is at the bottom of this page.

Change ID
CHG-88412
Release
order-gateway 2026.06.1
Environment
PROD
Change class
Normal · medium risk
Deployed by
J. Lindqvist (release engineer)
Deployed
10 Jun 2026, 19:00–19:47 CEST
CAB reference
CAB-2026-W24-07
Result
Deployed · no rollback

Release decision

Accountable owner: P. Mehta (head of engineering) · authorised at CAB-2026-W24-07. Release engineer: J. Lindqvist.

Risk acceptance: Normal/medium-risk change. Three MED-risk commits carry idempotency, retry-queue persistence and currency-rounding changes; all gated behind a default-off rollout flag with a 9-minute tested rollback and no schema migration. Residual risk accepted on that basis.

Change inventory · 10 commits in scope

CommitSummaryTicketRisk
a3f81c2Add idempotency key check to order-create endpointLH-4312MED
9b04e7dMigrate retry queue from in-memory to persisted storeLH-4318MED
c71d950Bump connection-pool ceiling for peak batch windowsLH-4325LOW
e28aa14Fix rounding drift in multi-currency order totalsLH-4297MED
5fd3b6eStructured logging for rejected order payloadsLH-4330LOW
12c9f08Remove deprecated v1 order-status endpoint (dark since April)LH-4188LOW
b8e0271Tighten input validation on customer-reference fieldLH-4334LOW
76aa9c3New health probe covering downstream pricing-service linkLH-4341LOW
04de58bConfig: stage rollout flag for the new retry queue (default off)LH-4318LOW
f93c1adUpdate generated API docs and changelog for 2026.06.1LH-4350LOW

Test evidence · all suites green on release candidate f93c1ad

Unit tests 1,482 passed · 0 failed · 11.2s

Representative cases (5 of 1,482):

  • OrderTotalsTest.multiCurrencyRounding_halfEvenAcrossLines
  • IdempotencyKeyTest.duplicateKeyWithinWindow_returnsOriginalResult
  • RetryQueueTest.persistedEntrySurvivesRestart
  • CustomerRefValidatorTest.rejectsControlCharacters
  • HealthProbeTest.pricingLinkDown_reportsDegradedNotDead
Integration tests 214 passed · 0 failed · 4m 38s

Representative cases (4 of 214):

  • OrderFlowIT.createOrder_endToEnd_withPricingServiceStub
  • RetryQueueIT.brokerOutage_ordersReplayedInOrderAfterRecovery
  • StatusEndpointIT.v1Removed_returns410WithMigrationHint
  • RolloutFlagIT.retryQueueFlagOff_legacyPathStillServes
Performance p95 within budget · 30-min soak, 2× peak load
p95 latency, before (2026.05.2): 184 ms avg
184 ms
p95 latency, after (2026.06.1): 171 ms avg
171 ms

Verdict: p95 improved 184 ms → 171 ms (−7%) at 2× peak load; no error-rate change. PASS.

  • PerfSoak.orderCreate_2xPeak_30min_p95UnderBudget
  • PerfSoak.retryQueuePersisted_noThroughputRegression

Approvals · completed record

Rollback plan · verified in staging 09 Jun

  1. Freeze inbound traffic at the gateway load balancer (drain mode, keep in-flight orders). ~2 min
  2. Set rollout flag retry_queue_persisted=off to fall back to the legacy queue path. ~1 min
  3. Redeploy previous release 2026.05.2 from the immutable artifact registry. ~6 min
  4. Replay any orders parked in the persisted retry store through the legacy path; verify counts match. ~4 min
  5. Unfreeze traffic, confirm health probes green for 10 minutes, notify CAB and close the record as rolled back. ~12 min

Estimated total rollback time: ~25 minutes. No schema migrations in this release, so database rollback is not required.

Deployment timeline · 10 Jun 2026 (CEST)

How this was made: the brief, how to reproduce it, and an honesty note

The brief

Assemble a single-file HTML release evidence report for change
CHG-88412 (order-gateway 2026.06.1): the commits in scope with ticket
references and risk class, test results by suite with expandable
detail, the approval checklist with names and dates, the rollback
plan, and the deployment timeline. It must print cleanly and open
with no tooling, because someone may need to read it in two years.

How to reproduce

Paste the brief into any capable LLM: GPT, Claude, Gemini, Grok, DeepSeek, or the assistant your company provides. Iterate a few rounds on layout and content until it reads well. Save the final answer as a .html file and open it in any browser. Expect similar output, not identical: every model has its own taste, and that is fine.

Honesty note

This reference artifact was built with Claude Code, an LLM coding agent, over several iterations. Treat it as the bar to aim for, not as a guaranteed first answer. All data on this page is fictional.

Next artifact Dependency risk report →
vishalshah.app