External testing preview. Not an official public CCAC website.

Infrastructure Explorer · Phase 2

Explore the systems SOTE is built on.

Start with the trust zone, then move into racks, public-safe components, services, dependencies, and the continuity controls behind them.

Trust zones

These numbered zones are authority boundaries. Named areas such as Rocket's Engineering Bay and Ace Help Desk remain work areas inside the larger SOTE environment.

Zone 0

Classroom / endpoints

The instructional starting point. Workstations provide access to approved resources without granting infrastructure authority.

Live from the infrastructure record

Rack and continuity dashboard

This view is generated from data/infrastructure.json. Phase 2 tracks all ten Definition of Operational controls instead of the original six-indicator prototype.

Loading infrastructure record…

Public-safe component model

What is actually carrying the environment?

These component records expose purpose, role ownership, and high-level dependencies without publishing management addresses, credentials, protected configuration, or attack-enabling topology detail.

Loading component records…

Current build priority

Mission Control → Rack 1 → Rack 2

The current critical path is establishing reliable classroom access through Mission Control and Rack 1 into Rack 2, then launching foundational services.

1

Mission Control aggregation

Recommission and document the aggregation pathway without placing the backbone under normal classroom control.

2

Rack 1 instructional access

Networking 2 students can reach and configure designated Cisco equipment within explicit mission scope.

3

Rack 2 production path

Extend the validated pathway into production switching and the initial production subnet.

4

Foundational services

DHCP, DNS, GLPI, and later additional production services become reachable from authorized classroom systems.

Other SOTE work areas

These are functional areas, not numbered trust zones.

Ace Help Desk

Service desk, ticketing, classroom guided learning, and knowledge workflows.

Open Help Desk →

Server Validation

Hardware intake, testing, troubleshooting, evidence capture, and deployment readiness.

Rocket's Engineering Bay

Staging, crash-cart work, server preparation, hardware testing, and experimental builds.

Explore work area →

How this view is built

The current public-safe projection lives in data/infrastructure.json. GitHub is supplying the pre-NetBox structured view. When NetBox becomes operational, physical and logical state should move to a sanitized read-only NetBox projection while ProfessorSneaker keeps the same discovery experience.