- Admission
- Pinning a tool server before ODIN starts it: a hash of its launch command and of its source files (or its binary), and every tool classed read, write or blocked.
- Agent framework
- The library that runs the agent loop, tools and subagents (for example the Claude Agent SDK, the OpenAI Agents SDK or LangGraph). Guardrails sit outside it, in the orchestrator and the tool servers.
- Approval card
- A pending tool call shown to an approver. Bound to the exact input by a SHA-256 digest, single use, expiring, re-checked against policy when approved.
- Approver
- Admins and members of the approver groups. Approving is separate from driving a chat.
- Audit log
- Append-only, hash-chained, fsynced per record; secret-looking keys redacted before writing.
- Blast radius
- What a failure or a change would break, newly allow or move, and who is affected; computed by the twin over regression flows.
- Budget
- Per-origin caps: tool calls per agent run and per message, tokens per message and per chat, currency per chat.
- Cache read
- Input the model provider served from its prompt cache: billed at a fraction of input; counted separately and left out of token budgets.
- Change gate
- The per-turn decision whether the person's message asks for a change. Without a grant, write-class tools are refused.
- Change grant
- The record of that decision: how, by whom, why. Never carried to the next turn.
- Change record
- A file in your infrastructure repository: id, title, risk, reason, targets, playbook, variables, verification, rollback. Never a secret.
- Change runner
- An automation job that runs a record's playbook in check mode (merge-request branch) or for real (default branch), as the pipeline's identity.
- Capability change
- A new or edited playbook or role, proposed and reviewed on its own before any change record uses it.
- Carry-over
- The hand-over summary that starts a fresh chat when the old one's context grew large.
- Default role names
- ODIN-Admins, ODIN-Operators, ODIN-Viewers and ODIN-Approvers map directory groups to roles and approval rights; example access-profile groups such as ODIN-NetOps and ODIN-Auditors grant tool access. Map them to your directory's groups.
- Delegation
- ODIN's call to a specialist; in the foreground, with related hand-offs appended.
- Digest
- sha256(canonical({session, approvalId, tool, input})): what an approval must echo.
- Digital twin
- A graph model of the network's live state (topology, routes, policy, addresses) used for path tracing, blast radius and what-if, paired with an emulation lab for rehearsals.
- Emulation lab
- A lab running real device images (for example Cisco CML, GNS3, EVE-NG or containerlab) where the pipeline rehearses a change before production.
- Golden flow
- A flow with a known answer and the rule that decides it; a regression test the twin runs in CI and after every change.
- Hand-off
- A specialist's final report, kept per chat and attached as data to the next related delegation.
- IaC change path
- Propose in Git → validate and what-if in CI → check in the automation platform → merge card → merge at the checked head → run → verify.
- Merge card
- The approval card the orchestrator raises itself after a check passes at a known merge-request head.
- Model gateway
- One endpoint in front of hosted and self-hosted models: routing by tier, budgets, logging, data-residency rules, one credential per environment.
- ODIN
- O.D.I.N.: Observe, Detect, Investigate, Normalize. What the agent does with an infrastructure signal: observe it, detect what matters, investigate with evidence, and normalize: propose the change that returns the system to its intended state (applied by the pipeline, never by the agent).
- Operator policy
- The prompt layer carrying your organisation's standing rules and preferences; next to it, identity (how ODIN works) and environment (the operations brief).
- Origin
- Where a chat came from: people, a schedule (job) or a trigger (alert). Picks the budget.
- Profile
- Tool access per directory group: which tool servers, read or read and write.
- Roster
- The set of specialists: one definition per specialist. A specialist loads only when one of its tool servers is admitted.
- Run window
- A short window after the merge approval during which the run of that change needs no further card.
- Scope
- What a specialist may touch: its own tool servers, its access level, its own skills; enforced on every call.
- Specialist
- A subagent with its own model tier, tool servers and access.
- Speech service
- Optional speech to text and text to speech next to the orchestrator, for hands-free status.
- Tier
- A capability class (small, standard, large) that the model gateway maps to a concrete model per environment.
- Vault
- Where every credential lives (for example HashiCorp Vault / OpenBao, a cloud secret manager or CyberArk). Pipelines fetch short-lived credentials from it; agents never do.
- Warm agent
- A chat's agent process kept between turns; closed after an idle period, resumed on the next message.
- What-if
- Applying a change to a copy of the twin and tracing the regression flows before and after: would break, would newly allow, path changed, unchanged.