Network Change RouletteLowering the high stakes with every win.

How to play

You’re the engineer reviewing a network change. Your goal is to predict who will lose access, judge the rollout risk, and use evidence to defend your call.

  1. Lock the acceptance checks. Translate the requested outcome into permit or revoke for each branch.
  2. Read the ticket. Compare each branch’s current path with its required access. A retired lab losing access can be a successful change.
  3. Make your forecast. Select the branches that will lose HTTPS access, or choose “Neither branch.” Rate the risk using rehearsal coverage, recovery time, and service tolerance.
  4. Spin and check your work. Run the collector at each branch and interpret the observations to unlock your forecast result. Try a rollback and see which branches meet the original requirements. On the fifth ticket, choose whether to approve, stage, or hold the rollout.

Learn the Network Automation Forum (NAF) framework

The ticket records Intent. When you spin, Orchestration sequences the rehearsal. The Executor applies the simulated change and the Collector probes each branch. Observability compares those results with intent. The game screen is the Presentation layer where you inspect the evidence and make your call.

Each independent first forecast is worth up to 100 points. Exact branch impact earns 60 and the correct risk rating earns 40. You can inspect the configuration freely. Using a hint or worked solution makes that ticket unscored practice.

Read the prototype specification

Ticket library

Restart this session?

This clears your saved campaign points, forecasts and help history. Export your evidence first to keep a copy.