Deadfront is two halves over one shared definition: a training twin where an electrician practices a procedure, and a hands-free field app that walks them through the identical procedure in front of the real equipment.
No sign-in. Both open straight into the working prototype.
dead·front (adj.) — construction in which no live parts are exposed to the person operating the equipment. A barrier between the worker and the hazard. That is the whole intent: stand between the person and the mistake, without getting in the way of the work.
Identify the asset, get its procedure, and have it read aloud and advanced by voice — with gates that will not let you skip. Runs on a phone, a tablet, or Quest 3 passthrough.
Operate a system, run a scored exercise, or practice a procedure against the twin — where the model proves each gate it can on its own. A data-driven engine that scales from a two-button drill to a live digital twin.
Every procedure — its steps, its gates, its wording — lives in one shared file both halves read. Author and validate it in the twin; execute the exact same thing in the field. Adding a facility is authoring content, not editing an app.
A heads-up panel plus voice — deliberately not AR pinned to live gear, which is unreliable today and unsafe when misregistered. It also means no world-tracking, so the same code runs on iPhone, Android, and Quest.
One generic engine runs any system definition. A small exercise and a full digital twin are the same schema filled in to different depths. Adding a simulator is adding a module — nothing else changes.
The app guides the procedure; it never asserts an energy state. It will tell you to verify absence of voltage by the approved method. It will never tell you the gear is dead — and it has no mechanism to. A build check enforces this in the wording itself.
Both halves are live. Pick where you are.