I turn opaque networks into something you can query, plan around, and build against.

Build the crawl engine once in Go, expose it across a narrow C ABI, and let a C++/Qt application and a headless CLI be two front ends over the same core — so discovery is a library, not a feature of one binary. SSH and SNMP collect side by side, with OIDs already validated against Junos, IOS and EOS. The map JSON schema is treated as a contract, because other tools consume it; the viewer is a separate, loosely coupled executable, and export and merge are first-class.

Split it. The terminal became a widget first and an application second, so the emulator is a reusable component rather than a feature of one binary. The application on top does one job: tabbed SSH, telnet and serial sessions that know their connection state, a session tree, an encrypted credential vault, and per-session logging — the same build on Linux, macOS and Windows. Mapping and capture moved into their own applications that share the map schema instead of the process.

A desktop archive in the CatTools tradition, read-only by design so it can be pointed at a network nobody has vouched for yet. It pulls configs and show output, keeps every version, and diffs what changed. ARP and MAC tables are parsed into searchable records by a template-scoring engine ported to Go — the output selects the template, not the engineer. Inventory comes straight from a mapping crawl, so the map feeds the archive with no retyping.

Make any CLI output a first-class record. Define a template and it's collected, parsed, versioned, and semantically diffed — a peer dropping to Idle, not a timer ticking. Every parse is scored on records, fields, population and consistency, so the platform tells you whether its own data is even true, with a template lab for fixing the ones that aren't. All of it API-addressable, so it becomes the source of truth other automation reads.