Why a Network Source of Truth is the foundation of automation

Every network automation program eventually runs into the same wall — not a technology limit, but a data one. Automation is only ever as good as the data it acts on, and in most networks that data is scattered, stale, and contradictory. Fix that first, and everything above it gets easier. Skip it, and you simply automate the chaos faster.

Ask three engineers where the "truth" about a given network lives and you'll often get three answers: a spreadsheet, the running config on the device, and someone's memory. Each is partly right and partly out of date. When automation reaches into that environment to make changes at scale, those small inconsistencies stop being harmless — they become outages.

A Network Source of Truth (NSoT) is the fix. It is the single, authoritative record of what the network is and what it is supposed to be — and it is the foundation the rest of an automation strategy is built on.

What a source of truth actually is

An NSoT is not documentation, and it is not a monitoring tool. It is a structured, queryable model of the network's intended state: sites, devices, interfaces, IP addresses, circuits, VLANs, services, and — crucially — the relationships between them. It answers questions like "what should be connected to this port," "which prefixes belong to this site," and "what services depend on this device" with data, not tribal knowledge.

The most useful way to think about it is two states side by side:

• Intended state — what the network is designed to be. This is the authoritative record humans and automation both work against.
• Actual state — what discovery and telemetry report is really out there, right now.

The gap between the two is drift — and continuously detecting and reconciling that gap is one of the highest-value things an NSoT enables.

Why it has to come first

Look at everything a mature automation practice does, and notice how much of it depends on trusted data:

• Provisioning and orchestration generate configuration from the intended state. Wrong data in, wrong config out — at machine speed.
• Compliance and golden-config only mean something if there's an authoritative definition of "correct" to compare against.
• Observability and assurance need topology and relationships to turn raw alerts into meaningful, correlated incidents.
• AIOps is only as smart as the context it's given; without a source of truth, its correlation is guesswork.

Each of these reads from — and ideally writes back to — the same source of truth. Build them on scattered data and every layer inherits the same fragility. Build them on a solid NSoT and improvements compound: better data makes every automation above it more reliable.

What good looks like

A source of truth earns its name when it has a few properties:

1. One coherent data model. A shared schema for sites, devices, addresses, circuits and services — not a dozen overlapping spreadsheets.
2. API-first access. Every other system reads and writes through a stable API, so the SoT becomes the hub, not another silo.
3. Reconciliation with reality. Discovery continuously compares intended vs. actual and flags drift, so the data stays trustworthy.
4. Clear ownership and lifecycle. Data is created, changed and retired through governed processes — the SoT is maintained, not just populated once.

How we approach it at TAMAKUN

We treat the source of truth as the first deliverable, not an afterthought. In practice that means starting with the data model and the domains where automation will deliver value fastest, standing up a NetBox-class source of truth as the authoritative record, reconciling it against discovery so intended and actual state stay aligned, and exposing everything through an API that provisioning, observability and AIOps all build on.

It is deliberately unglamorous work. But it is the difference between an automation program that scales and one that quietly stalls the first time the data lets it down. Get the foundation right, and everything you build above it gets to stand on solid ground.