Glossary¶

Short names used across the operator manual, the lab canvas, and plan / reconcile.

Word	Meaning
topology.yml	The lab you want: nodes, networks, links, and which startup config each node boots. A full example is A first lab.
n_1	Stable node key in that file. The hostname (R1) is only a label and can be duplicated.
net_1	Stable network key. The canvas label (LAN) is not the key.
configset	Which startup-config library a node boots. The library itself is configsets.
Plan	A preview of what would change. It does not write the lab.
Reconcile	Apply that preview. to_eve changes EVE to match the file. from_eve writes a new file from the saved EVE lab definition.
confirm	The second reconcile, sent only when a person chooses to stop nodes. Omitted confirm does not stop nodes.
plan identity	The id of the plan you just read. Confirm must send that same id. A mismatch stops nothing.
pending stop	Reconcile finished the safe work and is waiting. Nodes that still need a stop are still running.
requires stop	A change that is possible only after those exact nodes stop.
StopNode	The stop of one of those nodes. It runs only after confirm and a matching plan identity.
obligations	The ordered steps the agent will run for one change. The client does not invent them.
live applicable	Safe to apply while the node keeps running.
unsupported	Cannot be done in place. The whole plan writes nothing to EVE until the file changes.
Status	Lightweight poll: which nodes are running, and the live link quality.
Inspect	Structural snapshot: nodes and interface names. Not the frequent poll, and not the file you want.
LOAD	Attach to a lab EVE already owns. You can operate it. You do not deploy or reconcile its design.

Operator path: A first lab. Plan detail: Plan / reconcile. Agents in the editor: AI / MCP.