Chip, device rules in plain words

On-device rules · Layer 3

"Say it once. It keeps doing it."

What Chip does

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.

Say it in plain words

Describe the behaviour and Chip writes the rule. There's no condition builder or scripting language to learn.

Then it runs without Chip

The finished rule lives on the device and is evaluated about twice a second in firmware. No model, no network, no daemon.

Two loops, on purpose

The AI loop is online and slow, and only awake while you're asking. The rule loop is offline and fast, and never sleeps.

Each device remembers

Chip keeps notes per device, such as which tank is which, so later requests still have context.

See what's really running

Ask a device for its rules and it answers from firmware, not from a copy on a server.

Your choice of model

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.

How it works

Chip is only needed to write a rule, never to run it.

  1. You describe the behaviour you want in chat.
  2. Chip, using the model you choose, turns it into a rule and sends it to the device.
  3. The device's firmware evaluates the rule about twice a second, offline.
  4. You can ask the device for its rules at any time.

Where it fits in the four layers

1 Infrastructure & roles Vera, Grant, the bus, the device registry
2 Data pipeline & state Flo, DynaRAG, the carousel
3 Reasoning & inference Rick, Annie, Max, Hank
4 UI & collaboration Marco, Noted, Norm, the graph

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.