Nothing here has been installed in an occupied home.
Companies at this stage usually describe what they intend to build in the present tense and hope nobody checks.
Independent review outcome: a credible research prototype, not a product implementation. We think that is the correct grade.
The prototype issues a confirmation token, and possession of that token is enough to authorise the request again. The confirm step does not persist an approved state, which means the human-approval boundary we claim is not actually enforced.
The required lifecycle is issued → approved → consumed, with an authenticated approver, action hash, expiry, and an approval ceremony outside the requesting agent’s own channel.
Both the simulated gateway and device update the replay window before verifying the message authentication tag. A forged packet with a high counter can therefore suppress legitimate traffic even though it fails authentication — a denial of service on someone’s lights, without a key.
Cheap rejection of obviously old frames is fine. Unauthenticated input must never irreversibly mutate receive state.
Reconciliation reports and physical overrides both arrive with command ID zero, so a state correction can be mistaken for someone pressing a switch. Command ID overloading is being replaced with an explicit origin enumeration: local input, remote command, reconciliation, boot recovery, safety action.
Gates, not dates.
Foundation — three P0 defects fixed, reproducible build from a clean clone. Current.
Low-voltage proof — protocol on development boards, with latency, reconnect and coexistence measured on safety-extra-low-voltage loads.
Test pour — one cast element with conduit, box and draw-wire surviving demoulding.
Engineering prototype — one switchboard architecture, reviewed by a qualified electrical specialist before schematic freeze.
Instrumented pilots — devices running multi-day in real properties with traceable outcomes.
First building — one completed, occupied structure using the element and the system.
Repeatability — element library and configurator, and a project delivered by someone other than the founder.
Designing the full product family in parallel. Ordering production tooling. Marketing predictive fault detection we cannot yet demonstrate. Freezing the proprietary protocol before measurement. Letting agents take consequential actions. Treating the simulator as RF or thermal evidence. Owning a precast plant. International expansion.
Every item is a good idea that would slow the only thing that matters right now, which is getting one system working in one building.