Meet Lattice

Family Dog — Message Bus

"Fetches messages between everyone. Always knows where things are."

What Lattice does

Golden retriever, glowing messages in his mouth, tail always wagging. Lattice is the family's nervous system — the message bus that connects every member to every other member. Subject-based routing, last value cache, prefix matching. He never drops a message and always remembers the most recent state of everything. The oldest member of the family. Came from the uncle's world first.

Subject-Based Routing

Messages are addressed by subject, not destination. Publish to a topic, and every subscriber who cares about that topic gets it. Clean decoupling between senders and receivers.

Last Value Cache

Lattice remembers the most recent value for every subject. New subscribers get the current state immediately — no waiting for the next publish cycle.

Prefix Matching

Subscribe to "sensor.*" and get every sensor topic. Subscribe to "sensor.temperature.*" for just temperature readings. Hierarchical, flexible, zero configuration.

Sensor Routing

Max publishes temperature readings. Mona subscribes for health monitoring. Vera subscribes for knowledge queries. Same message, three consumers, no coordination required.

Query Dispatch

When Chip receives a user question, Lattice routes it to Vera. When Vera needs fresh data, Lattice asks Norm. Request-reply patterns built on publish-subscribe.

Health Monitoring

Every heartbeat, every status update, every error report flows through Lattice. Mona watches these topics to keep the family healthy.

How the family uses Lattice

Real message flows in a running Kevin household. Every line is a subject that Lattice routes.

sensor.temp.kitchen — Max publishes, Mona monitors
health.*.heartbeat — everyone publishes, Mona aggregates
query.vera.ask — Chip dispatches user questions
norm.nightly.report — Norm's morning summary
walt.task.assign — Walt dispatches work items
alert.mona.threshold — Mona raises alarms