Automated network discovery & sensing
Device discovery is not built yet. The design is for Scout to scan your subnets,
detect active hosts, and infer device types, so the twin can be populated without
manual entry, on a schedule or on demand after a provisioning event.
When to use
Intended for day-one onboarding and post-change verification, once it exists.
Architecture → Vendor data translation & migration
Bulk import of a DCIM bundle works today through the operator CLI. The Polyglot
agent, which would automate import and translate exports from other DDI tools
such as Infoblox, BlueCat, and phpIPAM, is in development.
When to use
Bootstrapping a twin from an existing export. Today, use the operator CLI for
DCIM bundles.
CLI reference → Auto drift detection
Drift detection is being built and is not wired into the running service. The
design is for Truth Seeker to compare the state recorded in your twin against
what Scout observes on the live network, and flag divergence. It depends on
Scout, which is planned.
When to use
Intended for environments where unauthorized or undocumented changes are a
compliance or operational risk, once it is available.
Architecture → What-if preflight check (not an agent)
A what-if preflight check ships today as ordinary code on a tenant route. It is
the one capability in this catalogue that works now, and it is not an agent.
Wiring it into an agent that gates changes automatically is in development.
When to use
Before a planned change to DNS zones, DHCP scopes, or IP allocations, to see
the effect before you commit it.
API reference → Auto-planning for network changes
The design is for The Architect to take stated intent, such as "I need a /24 for
the new data center pod, routable from the management VLAN", and propose an
allocation plan: subnets, VLAN IDs, DNS zones, DHCP scope boundaries, within your
existing topology and policy constraints.
When to use
Intended for new site buildouts and greenfield addressing work, once it exists.
Architecture → Full closed-loop automation
Not wired into the running service. The design is for The Hands to stage a
planned change and The Closer to apply it across DNS, DHCP, and IPAM, with an
audit trail and a way to roll back.
When to use
Intended for environments where human-in-the-loop execution is the bottleneck,
once it is available.
Architecture → DNS / DHCP telemetry & anomaly detection
The design is for The Signal to watch DNS query volume spikes, DHCP pool
exhaustion rates, and rogue DHCP server behaviour. IPAM shows you static subnets.
The Signal would watch the dynamic DDI traffic moving through them.
When to use
Intended for where dynamic traffic patterns, not static records, are what
actually breaks.
Architecture → DCIM physical layout planning
The design is for Rack Master to take a physical hardware manifest and propose
patch panel wiring, rack unit placement, and power phase balancing in the visual
canvas.
When to use
On demand when provisioning new rack space, in place of manual drag-and-drop
DCIM planning.
Architecture → Compliance & zero-trust governance
The design is for The Audit to scan the topology graph for orphan IP records,
unallocated active ports, expired TLS certificates on DNS endpoints, and
dual-homed devices violating isolation boundaries.
When to use
Intended as a scheduled audit or a pre-compliance check, once it exists. It
would not make you compliant with any framework by itself.
Architecture →