MISSION CONTROL

Lance novas versões sem substituir production às cegas.

Mantenha a baseline estável, encaminhe uma quota controlada ao candidate e aumente apenas com evidência real.

SimulationStart canaryCollect evidencePromote or rollback
CESSY / MISSION CONTROL
Cessy Mission Control production operations interface
Start canary5%Candidate traffic
Collect evidence15%Candidate traffic
Increase traffic30%Candidate traffic
Evidence state50%Candidate traffic
Promote or rollback100%Candidate traffic
SAFE RELEASE GUIDE

NEXT SAFE ACTION

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

WHAT THE PERCENTAGE MEANS

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.

EVIDENCE GUARDRAILS

No blind traffic increases.

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

Evidence state

No blind traffic increases.

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

Collect evidencePromote or rollbackActivity & Documents
Cessy Mission Control telemetry
PRODUCTION EVIDENCEBASELINE / CANDIDATE / ROLLBACK
MISSION CONTROL

No blind traffic increases.

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

Review the developer flow