🖥️ Fleet Identity Tracking
How HER (the AI administrator) knows exactly which of 13 identical Dell laptops she is talking to — and why this prevents chaos.
The Problem: 13 identical machines, cloned from the same disk image, with the same hostname, same SSH keys, and same machine ID. Without identity tracking, they all look like the same machine to the network.
🧬 The Identity Crisis
When you clone a hard drive and copy it to 12 more machines, every copy is perfectly identical at first:
| Attribute | Clone 1 (Dell02) | Clone 2 (Dell03) | Clone 3 (Dell04) |
|---|
| Hostname | dell01 | dell01 | dell01 |
| SSH Host Keys | Same | Same | Same |
| Machine ID | Same | Same | Same |
| Tailscale Identity | Same | Same | Same |
| IP Address | DHCP random | DHCP random | DHCP random |
What goes wrong: Tailscale sees 3 machines with the same identity and gets confused. SSH warns about "host key changed" on every connection. Network logs show 13 machines with the same name. You can't tell which machine a student is having trouble on.
🛡️ The HER Identity Protocol
Every time HER (the AI administrator) connects to any school machine, she runs a two-step identity check:
1
Read the hostname
hostname
Expected: Dell01, Dell02, ... Dell12
2
Read the identity marker
cat /var/lib/her-agent/identity.json
This JSON file contains the machine's unique fingerprint.
Example Identity Marker — Dell01 (Golden Master)
{
"hostname": "Dell01",
"mac": "22:23:7a:d0:2d:aa",
"role": "school-workstation",
"fleet_id": "Dell01",
"clone_date": "2026-06-04T07:34:56+08:00",
"managed_by": "HER",
"status": "golden-master"
}
Example Identity Marker — Dell07 (Clone)
{
"hostname": "Dell07",
"mac": "22:23:7a:d0:2d:bb",
"role": "school-workstation",
"fleet_id": "Dell07",
"clone_date": "2026-06-04T07:34:56+08:00",
"managed_by": "HER",
"status": "clone"
}
⚙️ How Identity Is Born (The Post-Clone Script)
When a new machine boots for the first time after cloning, it runs post-clone.sh. This script gives the machine its unique identity:
📦
Clone Disk
Image Written
→
🔌
First Boot
→
📡
Read MAC Address
22:23:7a:d0:2d:aa
→
🏷️
Generate Hostname
Dell01 → Dell07
→
🔑
Regenerate SSH Keys
Unique per machine
→
🆔
Create Identity Marker
/var/lib/her-agent/
What Changes vs. What Stays the Same
| Attribute | Golden Master (Dell01) | Clone (Dell02-12) |
|---|
| All installed software | Identical | Identical |
| User accounts | Identical | Identical |
| Desktop wallpaper/settings | Identical | Identical |
| Hostname | Dell01 | Dell02, Dell03, ... |
| MAC Address | 22:23:7a:d0:2d:aa | Unique per NIC |
| SSH Host Keys | Original keys | Regenerated |
| Machine ID | Original | Regenerated on boot |
| Tailscale Keys | Dell01's keys | Must re-authenticate |
| Identity Marker | Dell01 golden-master | Unique per clone |
🔍 Why This Matters (The Scenarios)
Scenario 1: The Student Can't Log In
Without identity tracking: "Some laptop isn't working." Which one? Where is it?
With identity tracking: HER connects, reads identity.json, sees it's Dell07 in Room 304. Tailscale IP is 100.102.84.87. Problem diagnosed in 10 seconds.
Scenario 2: Deploying a Software Update
Without identity tracking: Push update to all 13 machines. One fails but you can't tell which because they all have the same name in the logs.
With identity tracking: HER targets Dell09 specifically, reads its identity marker, and knows exactly which machine needs attention.
Scenario 3: The "Ghost" Machine
Without identity tracking: Two clones both think they are Dell01. They fight over the same Tailscale IP. Network traffic goes to the wrong machine randomly.
With identity tracking: Post-clone script ensures each machine has a unique identity before it ever joins the network.
🤖 The HER Fleet Dashboard (Concept)
What HER sees when she checks the fleet:
$ ssh fleet-status
┌─────────┬─────────────────┬──────────────┬─────────┐
│ Machine │ Tailscale IP │ Status │ Uptime │
├─────────┼─────────────────┼──────────────┼─────────┤
│ Dell01 │ 100.102.84.80 │ 🟢 Online │ 3d 4h │
│ Dell02 │ 100.102.84.81 │ 🟢 Online │ 2d 1h │
│ Dell03 │ 100.102.84.82 │ 🟢 Online │ 2d 1h │
│ Dell04 │ 100.102.84.83 │ 🟡 Rebooting │ 0m 12s │
│ Dell05 │ 100.102.84.84 │ 🟢 Online │ 1d 18h │
│ Dell06 │ 100.102.84.85 │ 🔴 Offline │ — │
│ Dell07 │ 100.102.84.86 │ 🟢 Online │ 5h 22m │
│ Dell08 │ 100.102.84.87 │ 🟢 Online │ 2d 1h │
│ Dell09 │ 100.102.84.88 │ 🟢 Online │ 2d 1h │
│ Dell10 │ 100.102.84.89 │ 🟢 Online │ 2d 1h │
│ Dell11 │ 100.102.84.90 │ 🟢 Online │ 2d 1h │
│ Dell12 │ 100.102.84.91 │ 🟢 Online │ 2d 1h │
└─────────┴─────────────────┴──────────────┴─────────┘
Each machine is uniquely identifiable, remotely reachable, and its status known instantly.
🧠 The Philosophy
"If you can't name a thing, you can't reason about it. If you can't reason about it, you can't manage it."
Identity tracking is not just a technical detail — it's the foundation of fleet management. 13 machines that all look the same to the network are 13 problems waiting to happen. 13 machines with unique identities are a fleet you can teach with, demo with, and rely on.
📁 Files That Make This Work
| File | Location | Purpose |
|---|
identity.json | /var/lib/her-agent/identity.json | Machine's unique fingerprint |
post-clone.sh | .scripts/post-clone.sh | Generates identity after cloning |
fleet-bootstrap.sh | .scripts/fleet-bootstrap.sh | Verifies identity, adds HER's SSH key |
fleet-clone.sh | .scripts/fleet-clone.sh | Deploys golden master to all machines |
dell-fleet | ~/.ssh/config.d/dell-fleet | SSH shortcuts for all 13 machines |
🚀 What's Next
After cloning is complete:
- Every machine will have a unique hostname and identity marker
- HER can SSH into any machine by name (
ssh Dell07)
- The fleet dashboard will show real-time status of all 13 machines
- Software updates can be pushed to specific machines or the entire fleet
- Usage analytics can track which machines are most/least active
Want to see it in action? After the fleet is cloned, HER will demonstrate live: connecting to Dell07, reading its identity marker, deploying a software update, and checking its status — all from the living room.