Skip to main content

Set up

Workloads

A workload is a project, product or agent that uses AI. Every budget, key and report in Novie Control attaches to one.

A workload is anything that uses AI and should be accountable for it: an internal tool, a product feature, an agent, a team's coding assistant usage.

Build and Run

Every workload has a class.

RunBuild
ForAn application that is running: a product feature, service or production agent.People building things with AI.
Spends throughOne Application Key that belongs to the workload.Each member's personal Novie Key.
Who can spendAnyone holding the Application Key.Members only, while the workload is their selected workload.
BudgetRequired, above zero.Optional: a Build workload can be governance-only, with no budget.
Key expiryAt fiscal year end, or never.Not applicable.

A Run workload holds at most one active Application Key. Rotating it replaces the secret and keeps its settings; revoking it stops all spending through it.

What a workload has

  • Owner: the person accountable for its spend. Owners are marked on cards and detail pages.
  • Members: people who work on it. On a Build workload, members spend with their own Novie Keys.
  • Funding node: the department its budget comes from.
  • Budget: set aside from the department when the workload is created.
  • Optional metadata such as a repository or live URL.
  • Spend classification (Capex or Opex), which locks once the workload has spent money.

Approval

When a workload is created, policy decides whether it is approved automatically or needs a reviewer. Requests that need review appear in Approvals, with a link to the workload so the reviewer can see the context. Approving moves no money (the budget was already reserved); declining returns it to the department.

Lifecycle

Active workloads can call models. Paused, stopped or unfunded workloads are rejected at the gateway before any provider is called. If the department funding a workload is retired, the workload stops.