Network Ops: Night Shift
Work through six incidents by probing network paths and repairing switch ports, host gateways and router entries. Compare the same probe before and after a repair to earn a field patch.

The builder
- Name
- N8
- First spec project?
- Not recorded
- Began at
- NAF AC6
How it was built
- Model
- gpt-6.2-astra+ unknown
- Harness
- Codex
- Spec method
- GitHub Spec Kit 1.4.1
- Spec artifacts
- .specify/memory/constitution.md, specs/001-network-ops-night-shift/spec.md, specs/001-network-ops-night-shift/plan.md, specs/001-network-ops-night-shift/tasks.md, specs/001-network-ops-night-shift/research.md, specs/001-network-ops-night-shift/data-model.md, specs/001-network-ops-night-shift/quickstart.md, specs/001-network-ops-night-shift/contracts/ui-and-evaluator.md, specs/001-network-ops-night-shift/checklists/requirements.md
- Tasks
- 30 in 6 loops
Build environment
- MCP servers
- None recorded
- Sources & RAG
- Requirements for IP Version 4 Routers (rfc1812, 5.2.4.3) https://www.rfc-editor.org/rfc/rfc1812.html#section-5.2.4.3
- Requirements for Internet Hosts (rfc1122, 3.3.1.1–3.3.1.2) https://www.rfc-editor.org/rfc/rfc1122.html#section-3.3.1.1
- Internet Control Message Protocol (rfc792, Echo or Echo Reply Message) https://www.rfc-editor.org/rfc/rfc792.html
- Cisco Layer 2 Interfaces (vlan, Trunk and Access Ports and VLAN Traffic) https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/interfaces/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_Interfaces_Configuration_Guide_7x/configuring_layer_2_interfaces.html
- MDN: Using modules on the web (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules/Modules_on_the_web)
- W3C WAI-ARIA 1.2: Live Region Attributes (https://www.w3.org/TR/wai-aria-1.2/#attrs_liveregions)
- StarterKit/CONSTITUTION.md
- StarterKit/SPEC.md
- StarterKit/PLAN.md
- StarterKit/README.md
- .specify/memory/constitution.md
- specs/001-network-ops-night-shift/spec.md
- specs/001-network-ops-night-shift/plan.md
- specs/001-network-ops-night-shift/tasks.md
- specs/001-network-ops-night-shift/research.md
- specs/001-network-ops-night-shift/data-model.md
- specs/001-network-ops-night-shift/quickstart.md
- specs/001-network-ops-night-shift/contracts/ui-and-evaluator.md
- specs/001-network-ops-night-shift/checklists/requirements.md
- README.md
- tests/verification.md
- tests/fixtures/expected-cases.md
- .specify/init-options.json
- .specify/templates/constitution-template.md
- .specify/templates/spec-template.md
- .specify/templates/plan-template.md
- .specify/templates/tasks-template.md
- .agents/skills/speckit-constitution/SKILL.md
- .agents/skills/speckit-specify/SKILL.md
- .agents/skills/speckit-clarify/SKILL.md
- .agents/skills/speckit-plan/SKILL.md
- .agents/skills/speckit-tasks/SKILL.md
- .agents/skills/speckit-analyze/SKILL.md
- .agents/skills/speckit-implement/SKILL.md
- Skills
- speckit-constitution
- speckit-specify
- speckit-clarify
- speckit-plan
- speckit-tasks
- speckit-analyze
- speckit-implement
- Other tools
- PowerShell
- Git
- Python 3 http.server
- Microsoft Edge (headless)
- Browser test runner
- Codex web search
- Codex shell and patch tools
- Codex research sub-agent
- JavaScript isolate
- AI assets
- Codex-authored canvas pixel art, CSS switch rack and pixel field patches
Runtime: how to play
- Type
- static-web · HTML, CSS, JavaScript ES modules, Canvas 2D, JSON
- Start
- python -m http.server 8000 --bind 127.0.0.1
- Then open
- http://127.0.0.1:8000/
- Install needed
- No
- Internet needed
- No
- API key needed
- No
- AI at runtime
- No
- Tested on
- Microsoft Edge (headless on Windows)
- Saves
- In memory for one page session. Reload or confirmed restart clears progress.
- Accessibility
- Native controls, visible focus, text equivalents and reduced-motion styles are implemented. Manual keyboard-only, screen-reader and narrow-window playthroughs remain unverified.
Verification
- Tests
- 35 passing · Start the local server and open /tests/ and /tests/night-watch.html in a browser.
- Facts from
- Requirements for IP Version 4 Routers (rfc1812, 5.2.4.3) https://www.rfc-editor.org/rfc/rfc1812.html#section-5.2.4.3, Requirements for Internet Hosts (rfc1122, 3.3.1.1–3.3.1.2) https://www.rfc-editor.org/rfc/rfc1122.html#section-3.3.1.1, Internet Control Message Protocol (rfc792, Echo or Echo Reply Message) https://www.rfc-editor.org/rfc/rfc792.html, Cisco Layer 2 Interfaces (vlan, Trunk and Access Ports and VLAN Traffic) https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/interfaces/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_Interfaces_Configuration_Guide_7x/configuring_layer_2_interfaces.html
- Known limits
- Six authored incidents across three levels in a stable IPv4 snapshot with one modeled root cause per incident.
- Probes simulate authored path outcomes. No live devices, dynamic routing, NAT, wireless, intermittent loss or convergence.
- Human timing and independent review of all explanations remain unverified. The design target is 5-10 minutes.
- License
- unknown
Who it is for.
Night Shift puts you on call for a small outpost from midnight to dawn. Follow a workstation cable into an eight-port rack, inspect the link light and compare its VLAN with the work order. Send a ping before and after the repair to see whether service returns. The game is aimed at learners who already recognize an IPv4 address, a switch port and a default gateway.
THE BUILD STORYHow it was made.
The workshop starter kit supplied the constitution, first playable specification and plan. The team adopted the constitution in Spec Kit, wrote the feature specification and clarified how a learner could skip a broken incident while keeping the session incomplete. Planning produced the research notes, data model, interface contract and quickstart. The six task phases followed. Cross-artifact analysis was reported in the conversation. The research helper's exact model ID and the earlier implementation model ID are unknown. The later session reported the model listed above. No MCP server calls were recorded during the build.
The first prototype played like a console quiz. The creator asked for a pixel survival game, which led to an outpost that lights up as the player repairs devices. Device settings, packet probes and an inspectable switch rack followed. Early sandboxed browser runs failed during graphics initialization. Headless Edge later ran against a local Python HTTP server and completed the six-site playthrough. On 2026-11-17, Arcade verification served the game from the repository root on port 8000 and reran both pages in headless Edge. The playthrough reached daybreak and all 35 browser checks passed. The game code tested was committed in Git as 5c87bc5.
ADVICEFor the next builder.
- Write down the expected repair and a plausible wrong repair before writing the evaluator.
- Build one playable scene early enough for the creator to judge whether it feels like the intended game.
- Exercise the real controls from a fresh browser session and record which checks still need a human.
Built a game of your own?
Fill in the ARCADE template with your build agent and send me your GitHub URL.
Add your game →