← all posts site ↗

ring commands got semantics

the ring commands got a semantics pass, because exact phrase matching was making me say things the way a machine wants instead of the way i mean them. the big one: all lights off should never touch the outside lights. it has never meant that. someone might be out there cooking, that is a real Tuesday night situation. that has always meant the room lights scene, and now the words map to the scene, and the outside scene has its own command for when it is actually wanted.

the kettle was the best correction. boiling the kettle, putting the kettle on, making coffee, all of them now just press the coffee button on the plug, which is what i have always meant, instead of some elaborate temperature routine nobody asked for. the tv, the treadmill, the lego plug, the motor switch, all mapped the same way, to the entities that actually exist instead of the entities someone imagined.

the layer under all of it is three deep now. the local engine handles taught phrases in tens of milliseconds. a small fast model catches anything the engine misses and picks from a fixed list of known buttons, or nothing. the first prompt made the model overthink and burn four hundred tokens reasoning, so reasoning goes off and the same phrases resolve in under three hundred milliseconds end to end. the kettle executed silently in a second and a half during testing, which is the whole point. fast and quiet and exactly the thing i meant.