Play the campaignNetwork Change Roulette
Lowering the high stakes with every win.
Full campaign duel
One hundred tickets cover 60 firewall, 20 routing, 10 proxy and 10 PAC changes. The default sequence mixes families while tickets remain available in each family. Players may select unfinished tickets by topic. Each shift comprises up to three decisions, one free check per ticket, two reserve checks and one confidence chip. Selecting a ticket explicitly starts a new budget.
Player decisions
Read the service intent and the bot’s claim. Probe either branch, read the configuration delta, or rehearse rollback. Additional investigations spend reserve checks. Commit to approve, hold or roll back with any amount of evidence. Only then reveal scores and both resulting network states.
Decision rubric
Rollback is preferred when a required service loses access and the baseline restores required connectivity. Approve when both branches meet intent and recovery fits service tolerance. Otherwise hold. This is the game’s educational rubric. A hold retains pilot state while pausing expansion. Rollback restores baseline access, which may conflict with retirement intent.
Scoring and learning
Each decision earns up to one service continuity point, one access-policy point, two decision points and one evidence point. The confidence chip adds three for the preferred action or subtracts three otherwise. The bot’s recommendation uses its modeled forecast. It receives no evidence bonus for claims without a displayed investigation record. The player can inspect the proposed and baseline configuration, and observations use those same snapshots.
NAF intent appears in the ticket. The executor’s change appears in the configuration. Collectors produce branch observations. Orchestration carries out the decision. Observability compares each result against intent. The interface provides presentation.
Progress and validation
Campaign decisions, scores, current investigations and shift resources save in browser storage. Storage failure is reported visibly. The duel campaign has its own progress record. Existing earlier campaign records remain available in the earlier campaign page. Each topic has been exercised through the browser, including refresh during a PAC investigation and after a firewall decision. All 100 scenario snapshots and both configuration previews are validated programmatically.
Earlier campaign · NAF reference architecture