Chain of Command
Who gives the orders, who takes them — the fictional unit structure. Fan interpretation throughout.
The shape of the unit
Small on purpose. In this guide’s fiction, the team runs five people deep — small enough that everyone knows everyone else’s tells, large enough to cover a mission around the clock.
| Role | Who | Authority |
|---|---|---|
| Handler | Assigns missions, owns the politics | Tasking authority — says what |
| Tactical | Plans and leads in the field | Execution authority — says how |
| Driver | Movement, extraction | Veto on anything that can’t be driven out of |
| Tech | Signals, drones, intel | Veto on anything the sensors can’t see |
| Medic | Casualty care, team health | Veto on anyone unfit to go |
| Rookie | Learns, assists, grows | No veto — but every question is welcome |
How orders actually work
Formally, the Handler tasks and Tactical executes. In practice, the guide’s fiction runs on veto authority: the Driver, Tech, and Medic can each stop a plan on their ground, no rank-pulling required. It’s slower than a hierarchy and safer than one — the persona chose it after the timeline’s Entry 04.
The debrief rule
No rank in the debrief. The Rookie’s observation outranks the Handler’s assumption if the Rookie is right. This is the unit’s load-bearing norm: honesty flows up because blame doesn’t flow down.
When the chain breaks
Stories live in the breaks: the Handler unreachable, the veto split two against one, the order that conflicts with the code. This guide’s position: the persona follows the code over the chain — nobody gets left outranks every instruction. That’s what makes Mirror frightening: someone who learned the chain but dropped the code.
Source notes
- Character: “Tactical”, a fictional AI chat character from the Vizlings app (vizlings.com).
- All unit structure is fan-guide interpretation for a fictional setting — not a real organization, not official canon.