2026-10-31: The Name the NIC Kept

The speaker kept its name.

It had been filed under a television. The card in the catalog said Apple TV. The cloth on the shelf said Sonos, and the NIC agreed. DHCP and Bonjour had been saying the room the whole time. The enrollment did not.

A name that contradicts the manufacturer used to stop the namer. The screen stayed enrolled, which is right, because a person decides who leaves a curfew. The label stayed wrong, which is not. The next pass could paint the television name back onto the speaker. A private address that a console called “iPhone” is a different case. Nobody can prove that card from the vendor, so it waits for a person.

The NIC breaks the tie

Columbo still names only from what the device advertises and from the vendor on the NIC. A user-agent is still a lead. A private address with no manufacturer is still unnamed.

When the enrollment uses an Apple word and the vendor is known and is not Apple, the hold is recorded and the rename continues. The screen keeps the address. The firewall, and the canon beside it, take the name the device can actually be. Identity from DHCP or Bonjour wins when it is not another Apple word the same NIC cannot wear. Otherwise the name is the vendor and the tail of the address.

An Apple NIC that disagrees with its class is still a hold. The vendor did not catch a lie. A person still removes that enrollment.

Home Assistant names that share no token with the firewall name are printed and not written. A generic canon entry such as a bare “iPad” is not a gap. A lead is not a gap.

The tick that fails closed

The ten-minute job already applied names, groups, quarantine, and presence. It did not ask whether the label stuck. It does now. After a clean apply it audits. A pending rename is a gap. A canon entry that still equals the enrollment lie is a gap. One retry follows. If the gap remains, the tick exits 1. A verified write that does not read back also exits 1.

The screen engine no longer paints a vendor-proven lie onto the firewall, and it will not enroll a device because the live label is exactly a screen’s name.

What EETISMAD looks like here

Gate	Evidence
Everything E2E Tested	Columbo naming 69 passed. Phonebook identity 17 passed. Self-class 14 passed. The screen suite passed 1005, skipped 5, and expected 1 failure. None of them dial a host
in Sanctum-docs	This note, its sidebar entry, and the Columbo row on engineering discipline
Merged	sanctum-config 504ec5d, sanctum-screen-time fdb52b7
And Deployed	The naming tick 20261031-124321 reported zero gaps. The screen engine is fdb52b7c59ff

The operator who finds a speaker wearing a television’s name should not have to notice. The next tick does.

The bar is engineering discipline. A lead that stayed a lead is the cousin of this rule in The Lead That Stayed a Lead.

A card the NIC cannot be does not get to stay the name.