Specialist Roles
Use specialist Role nodes to give the STRATUM AI Operator infrastructure, network, application, storage, GPU, cloud, cybersecurity, compliance, ISSM and ISSO behavior.
Roles turn one AI into a datacenter team
Role nodes define the specialist lenses that contribute to planning and verification. They are not cartoon personas and they do not imply a separate model call for every role. They are typed specialist modules that inject domain behavior into the same governed Operator DAG.
A Role may contribute recommendations, policy, security checks, evidence requirements or verification depending on the role and the ports exposed by that node. Wire the role into the parts of the DAG where its expertise should affect the Mission.
Every current Role node
Specialist Roles
- Infrastructure Architect — Shapes topology, system relationships, placement, architecture boundaries and infrastructure dependencies before execution is compiled.
- Network Engineer — Adds network design and diagnostic reasoning: switching, addressing, routes, DNS, MTU, packet paths, service reachability and network verification.
- Application Engineer — Focuses the Operator on application dependencies, install/configuration work, service health and the evidence required to prove the application—not just the VM—is working.
- Storage Engineer — Adds storage placement, capacity, disk lifecycle, encryption and storage-path considerations to planning and verification.
- GPU Engineer — Adds AI accelerator/GPU Fabric reasoning, placement, Guest Tools awareness and CUDA/NVML-oriented validation for accelerator-backed workloads.
- Cloud Operator — Adds cloud-environment context and provider-aware operating behavior when STRATUM spans or runs inside public-cloud infrastructure.
- Cybersecurity Engineer — Contributes least-privilege behavior, exposure checks, firewall/encryption requirements, approved-artifact rules and security verification.
- Compliance Officer — Adds control-oriented policy evaluation, required evidence and approval expectations. It can make a plan stricter without pretending that a policy pack alone certifies the environment.
- ISSM — Represents security-program and risk-management constraints: policy posture, risk acceptance, approvals and control objectives that should influence a Mission before execution.
- ISSO — Represents operational information-system security: ongoing security checks, evidence collection and day-to-day enforcement requirements around infrastructure changes.
Drag a specialist into the DAG
Adding a Role is immediate: drag it from the palette onto the canvas, then connect its typed outputs to compatible downstream inputs. The graph highlights valid destinations as a wire is dragged, so the operator cannot be assembled with meaningless connections.
The active model can stay the same while AI Studio changes the operator around it. Add the specialists the environment needs, wire them into the DAG, and make their checks part of how STRATUM plans and proves infrastructure work.