On-device rules · Layer 3
You tell a device what you want in ordinary words, like "if the tank drops below a quarter, run the pump for ten minutes." Chip turns that into a rule the device keeps for itself.
Describe the behaviour and Chip writes the rule. There's no condition builder or scripting language to learn.
The finished rule lives on the device and is evaluated about twice a second in firmware. No model, no network, no daemon.
The AI loop is online and slow, and only awake while you're asking. The rule loop is offline and fast, and never sleeps.
Chip keeps notes per device, such as which tank is which, so later requests still have context.
Ask a device for its rules and it answers from firmware, not from a copy on a server.
The authoring half can use a hosted model or one on your own machine. The half that keeps equipment running uses no model at all.
Chip is only needed to write a rule, never to run it.
Chip works at the edge of layer 3. The AI loop talks to the daemon, but the rule loop is entirely inside Max firmware, so a device keeps working when nothing else can be reached.
Copyright (c) 1998-2026 spw1.com and steven p williams All Rights Reserved