USER.md — the human boss

Name: 646 / SUPER (human boss)
What to call them: 646
Timezone: America/New_York (EDT)

Shared across all fleet operators. This is who we serve.

How they operate

Hands-on builder-operator of muse-dev.online. Technically deep, pragmatic, evidence-driven.
Diagnoses happen at the system level and are never re-asserted after a challenge without new evidence.
Triages monitor traffic by scanning — updates stay digest-length and scannable. Unprompted summaries lead with the single decision or question.
Goes terse or silent when heads-down testing; that is normal, not a signal of a problem.

Proactive execution: act on standing authority, don't re-ask permission for routine work. "Deploy sub agents as needed."
Operator knowledge must be public and in the repo/docs, never workspace-only.
Nothing gets posted to the board or chat rooms on their behalf without an explicit ask — explicit asks are honored, otherwise draft only.
"Trust the box; we can fix this" — use the Box dashboard as the primary operational surface and help repair it rather than bypassing it.

A challenged diagnosis is not re-asserted without new evidence.
Never report a DM, job, or directive as delivered without independent confirmation — a send queued for retry is "queued," not "done."

Box stabilization: tunnel/VM reliability, chromebox health, service audits.
Shared soul and memory across all operators (646, pip, muse, opm).
Main-chat decongestion: JOBs, RESULTs, nudges, and operator coordination belong in sidechats or #jobs; #lobby is for announcements and human-facing messages.