Classroom / endpoints
The instructional starting point. Workstations provide access to approved resources without granting infrastructure authority.
Infrastructure Explorer · Phase 2
Start with the trust zone, then move into racks, public-safe components, services, dependencies, and the continuity controls behind them.
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.
The instructional starting point. Workstations provide access to approved resources without granting infrastructure authority.
Instructional network infrastructure plus the protected aggregation core that connects the classroom to SOTE.
Explore Rack 1 →View relationships →Production switching, services, GLPI, DHCP, DNS, future NetBox, and other operational capabilities.
Explore Rack 2 →View relationships →Controlled cyber-range infrastructure with tightly governed infrastructure access and bounded target access.
Explore Rack 3 →View relationships →Live from the infrastructure record
This view is generated from data/infrastructure.json. Phase 2 tracks all ten Definition of Operational controls instead of the original six-indicator prototype.
The structured record could not be loaded. Direct rack pages remain available above.
Public-safe component model
These component records expose purpose, role ownership, and high-level dependencies without publishing management addresses, credentials, protected configuration, or attack-enabling topology detail.
Current build priority
The current critical path is establishing reliable classroom access through Mission Control and Rack 1 into Rack 2, then launching foundational services.
Recommission and document the aggregation pathway without placing the backbone under normal classroom control.
Networking 2 students can reach and configure designated Cisco equipment within explicit mission scope.
Extend the validated pathway into production switching and the initial production subnet.
DHCP, DNS, GLPI, and later additional production services become reachable from authorized classroom systems.
These are functional areas, not numbered trust zones.
Service desk, ticketing, classroom guided learning, and knowledge workflows.
Open Help Desk →Hardware intake, testing, troubleshooting, evidence capture, and deployment readiness.
Staging, crash-cart work, server preparation, hardware testing, and experimental builds.
Explore work area →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.