Ecosystem

🚧 Under construction.

The protocol is deliberately small — a contract about what state is and how it is hashed. The pieces that actually watch a system, store its history, compare snapshots, and raise alerts are independent implementations built on it, each its own project.

A preview

A reference front-end — Ledvar view — is being built. Here’s an early look; it’s a work in progress and the visual form may still change.

Drift on a machine — what changed, node by node, with a risk read.

Fleet conformance — every machine scored against a shared ideal.

Multi-origin compare — the same collector across machines, divergences first.

What’s coming

This section grows as each piece is published:

• Collectors — observe some state and produce a snapshot. (planned)
• Gateway / store — receive snapshots and keep history append-only. (planned)
• Policy & alerting — turn drift into decisions. (planned)
• Front-end — read the history and show what moved. (planned)

Want to build one? Anything with state worth watching can feed the protocol. Start from the modeling guide and prove your collector against the conformance vectors.