IT Support is one named desk on my Grok Bot roster, not a department and not a process. Quality is the department. Digital Plumbing is the work. This page is the can/can’t plus one public-safe receipt.
Back to the hub roster on this site. A desk page only ships when it has can/can’t plus a receipt. Personal Assistant stays unpublished.
Where this desk sits. Click a box.
Skills (shared playbook)
↓
Departments (six, stable)
↓
Skills stay shared. Departments stay six. Desks are the runtime skin.
What this Grok desk can and cannot do
IT Support is the named desk. The work already lives in Digital Plumbing and Website Building and QA.
Three AWS words in English. SSM means run a command on the server without SSH. EC2 is the server. Route 53 is where the domain points. This desk does not reboot or shut servers down.
What it can do
- Reset a WordPress login on a fleet site when I ask
- Run a command on the site-builder server without SSH
- Look up which server a site is on, whether it is up, and its IP
- Read DNS
- Connect tools (Zoom, plugins) so other desks can use them
- Keep a key-only AWS login on the shared computer so department agents do not need my passkey
- Hand work to the right desk when it is not IT
What it cannot do
- Log into the AWS website
- Spend money or touch billing
- Create users or widen permissions unless I approve it
- Shut down, reboot, or delete a server
- Delete a site or wipe data
- Type my password or 2FA
- Publish a public page, send email, or post as me without a yes
- Write articles, set strategy, or own fleet uptime (Fleet monitor on the hub owns uptime)
House rule: documentation on this hub ships by default and we iterate. Still stop for a yes before sending email, spending money, deleting, changing permissions, or changing production infrastructure. IT Support still cannot publish articles or post as Dennis.
Receipts
16 August 2026. Reset the theninetriangles.com login for access@blitzmetrics.com from the shared computer. That site is the public face of the 9 Triangles framework. BlitzAdmin could not rotate that password. Recovery was SSM SendCommand plus WP-CLI from the live docroot /wp-sites/live/{domain}/public. The public site stayed up. Method: How we recover a fleet WordPress login (same steps as on the hub).
Skills this desk loads
These are already in the Task Library. No new category.
- Digital Plumbing Checklist
- What is Digital Plumbing?
- How to spin up a personal brand website using BlitzAdmin
- Zoom is intake under Knowledge System Maintenance, not a separate IT tree
- Web Function map for the website operating system
How this was QAd
This page was failing the Blog and Article Posting Guidelines as a wall of text. The diagram above is the topic-specific map. Green and red are the can/can’t. The generic Content Factory four-stage diagram stays off this page. The update loop lives with persistent agents update loop.
The index is the Grok Bot hub roster. The wider machine is The System overview.