Operations

What SOTE is working on now.

Operational work remains canonical in the SOTE Framework repository. ProfessorSneaker presents the work in a form that is easier to discover and follow.

Critical path

Mission Control → Rack 1 → Rack 2 → DHCP/DNS → GLPI → November services

Current infrastructure execution takes priority over optional discovery work. The goal is to establish a stable instructional pathway and production-services foundation before expanding the active mission portfolio.

…Loading missions

Mission and service work

Mission portfolio

Mission Board

Browse the current portfolio by Active, Approved / Queued, Discovery, Future / Backlog, and Blocked.

Open mission board →Operator work

Operator workspace

Queues, knowledge, missions, and contribution tools for SOTE Operations.

Open workspace →Service activity

Ticket queue

Review current ticket-designated work in the published operational snapshot.

Open queue →Knowledge

Operational knowledge

Search procedures and validated guidance produced through SOTE work.

Search knowledge →

Portfolio discipline

Not every good idea becomes active work.

Active

Current execution

Work consuming operator time and tied to current milestones.

Approved / Queued

Authorized next work

Approved missions waiting for prerequisites, capacity, or scheduled execution.

Discovery

Investigate first

Work intended to determine whether a full implementation mission should exist.

Future / Backlog

Preserve the idea

Strategically useful work that does not currently deserve execution capacity.

Blocked

Named dependency

Work that cannot proceed until an identified prerequisite or approval is resolved.