▶️ Watch the video In Part 13, we deployed the observability stack — OTEL Collector polling SNMP, VictoriaMetrics storing metrics, Loki aggregating syslog, Grafana rendering dashboards. NetClaw ca...
▶️ Watch the video In Parts 1 through 6, I built an observability pipeline on my home network: OpenTelemetry Collector polling SNMP, VictoriaMetrics storing time-series, Loki aggregating syslog,...
▶️ Watch the video I have a demo. One prompt, one conversation, and the agent builds a complete network lab — 20 routers and switches, source of truth, generated configurations, compliance monitor...
▶️ Watch the video Nautobot is a source of truth. It knows what devices you have, what interfaces they have, what VLANs are assigned, what IP addresses are allocated. But it doesn’t know what your...
I didn’t know what spec-driven development was three weeks ago. I’d never written a spec.md before writing code. I’d never asked an API “what fields do you actually have?” before designing an integ...
Three months ago, Convergence was a straightforward idea: build a network observability stack for a home lab. OTEL Collector pulls SNMP from two Cisco 3850 switches and a pfSense firewall. Victoria...
Phase 7 gave us a team of AI agents that could monitor a home network better than any dashboard. Five specialists — NOC officer, network engineer, security expert, NAS engineer, interface reconcile...
When we started the Convergence platform back in January, the goal was simple: stop guessing about what was happening on our home network and start knowing. Two Cisco switches, a pfSense firewall, ...
Three things happened after Part 5b. A bug surfaced that meant every Discord-approved pfSense action was silently missing from the audit trail — GAIT was recording the scheduler’s decision side but...
This is the second half of the Phase 5 writeup. Part 5a covered the agent’s core, the polling loop, IP filtering, Claude’s action proposal, the rate limiter, and repeat offender tracking. This part...