Reference
Glossary
Plain definitions of the terms used in Novie Control and in these docs, in alphabetical order.
The terms used in Novie Control and in these docs, in alphabetical order.
Allocation: Moving funds from a parent node in the organisation tree to a child department or workload.
Application Key: The API key that belongs to a Run workload. Whoever holds it spends from that workload. One active key per Run workload; it can be rotated or revoked.
Approval: A review step required by policy, for example before a new workload starts. Pending items appear in Approvals.
Assistant: The in-product AI that answers questions about your organisation and authorised prompt records, always linking to its evidence.
Audit log: The tamper-evident record of who changed what, including every money movement, policy publication and prompt read.
Build workload: A workload for people building with AI. Members spend through their personal Novie Keys.
Catalogue: The organisation's list of enabled models and their prices. Only catalogue models can be called.
Daemon: The Novie desktop app that governs and reports usage of AI coding tools on employee computers.
Default model: The model a model group uses when a request does not name one.
Department (also business unit or node): A level in the organisation tree that holds funds, members and policies.
Device pairing: Linking a computer running the daemon to your Novie account and organisation.
Effective policy: The combined result of every policy from the organisation root down to a target, after inheritance.
Fail-open: Daemon behaviour when Novie is temporarily unreachable: local AI tools keep working and a warning is shown.
Fallback: Running a request on another model when the first model's provider fails before a response starts.
Insights: AI-generated analysis of usage, shown with its evidence and scope.
MCP (Model Context Protocol): An open protocol that lets AI tools call external tools.
MCP client: An AI tool that connects to an MCP server, such as Claude, Codex or VS Code. Novie's MCP gateway exposes Novie Control as MCP tools.
Model group: A named set of models for a purpose, with a default and fallback order.
Novie Key: A personal API key. It charges the Build workload its owner has selected, or the one named in the X-Novie-Workload-Id header.
Organisation: Your company in Novie. The root of the organisation tree.
Owner: The person accountable for a workload's spend.
Policy: A set of rules (action, conditions, effect) attached to the organisation, a department or a workload.
Policy centre: The place in Novie Control to create, test, draft in natural language, and publish policies.
Prompt reporting: Policy-controlled collection of prompt content for review and analysis.
Provider: A model vendor connected to Novie, such as OpenAI, Anthropic or DeepSeek.
Reservation: Funds set aside when a model call starts and settled to the actual cost when it ends.
Rollover: Whether a workload keeps its unspent balance when a scheduled top-up runs.
Run workload: A workload for a running application. It needs a budget and spends through its Application Key.
Scheduled top-up: An automatic daily, weekly or monthly transfer into a workload, governed by policy.
Settlement: Recording the actual cost of a request against its reservation.
Single-top-up limit: The largest amount policy allows one top-up to transfer.
Total-balance cap: The highest balance a workload may reach after a top-up.
Workload: The unit of governance in Novie: a project, product, agent or initiative that uses AI, with an owner, members, a budget and policies.