Mount Shasta Ranch · live network edge
The whole ranch network, run by NoETL playbooks
Every minute one NoETL execution discovers the UniFi network, keeps a graph in ehgraph, detects issues with plain SQL and asks Claude to troubleshoot. Each unit of work claims a slot, runs, and exits. No daemons, no microservices, no agent server.
Topology · ehgraph
Discovered, not drawn
Gateway, switch, access points and every connected device, read back from the ehgraph topology database after each cycle. Tap a node for details.
Feed · deterministic detection
Findings, not alerts noise
Ten versioned SQL rules run over a named time window in DuckDB. The same window always gives the same findings, so every result can be replayed and audited. The LLM is never on this path.
Troubleshoot · kind: agent
An AI agent whose tools are playbooks
For each new finding, a Claude agent step investigates with six read-only tools: graph neighbors, uplink path, events, RF stats, findings and ping. Each tool is an ordinary NoETL playbook, so every call the model makes is its own recorded execution.
Under the hood · atomic executions
One minute of the edge
Each bar is one NoETL cycle execution, and each segment is a unit (a sub-playbook) that claimed a slot, did its work, and released it. The rest of the minute, nothing runs except the ehgraph database.
What the playbooks replace
collect/unifi.yaml, collect/edge_probes.yaml0normalize/normalize.yaml (DuckDB SQL)0graph/upsert_topology.yaml → ehgraph0detect/detect.yaml (10 versioned rules)0troubleshoot/analyze.yaml (kind: agent)0tools/*.yaml (6 playbooks)0publish/publish.yaml → this read-only site0Tour · how NoETL works