MISSION CONTROL

Déployez une nouvelle version sans remplacer la production à l’aveugle.

Gardez la baseline stable, routez une part contrôlée vers le candidate et n’augmentez l’exposition qu’avec de vraies preuves.

Mission Control canary rollout illustration

Simulation

Start canary

Collect evidence

Increase traffic

Promote or rollback

SAFE RELEASE GUIDE

Traffic is routing, not a test counter.

At 5%, eligible production requests remain mostly on the stable baseline while a small share is routed to the candidate. Increasing traffic changes that future routing share; it does not generate documents by itself.

Production baseline · v3

Baseline and candidate stay explicit

Staging candidate · v4

Traffic increases only with evidence

Promote / Rollback

Rollback remains a first-class action

Cessy document workflow from authoring to production

EVIDENCE GUARDRAILS

No blind traffic increases.

The rollout can require minimum candidate samples and healthy runtime metrics before the next exposure step becomes available.

template_version=v4 · environment=production · rollout=canary_42 · status=success · render_ms=1184

AUDIT + TRAÇABILITÉ

Telemetry should answer which version rendered a document, under which rollout, how long it took and whether it succeeded.

A staged version only receives production samples when eligible document requests are routed to it.

Review the developer flow

TWO SAFETY PATHS

Increasing traffic does not generate documents; production usage creates the evidence used for rollout decisions.

Keep traffic at 5% until the minimum healthy sample threshold is reached.