> ## Documentation Index
> Fetch the complete documentation index at: https://oximy.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Build an AI operating model

> Turn AI discovery, employee work, and model routing into a repeatable company process.

An AI operating model defines how the company sees AI activity, decides what to
support, gives people a standard place to work, and chooses which models handle
requests. Oximy supplies the map and control points; the company remains
responsible for its decisions.

## 1. Establish the baseline

Start with Visibility. Connect official sources and deploy the collection paths
needed to identify tools, accounts, people, models, activity, and spend.

Do not begin with enforcement. First determine source coverage, freshness,
identity quality, and which apparent gaps are collection gaps.

## 2. Assign decision owners

Define who owns:

* tool review and access;
* subscription and seat decisions;
* model and provider policy;
* employee AI-workspace standards;
* privacy, retention, and incident review; and
* endpoint and integration operations.

Use Oximy roles and access scope to reflect those responsibilities without
granting every reviewer company-wide administration.

## 3. Choose company defaults

Decide which tools and workflows the company will fund, what should be
standardized, and where exceptions are acceptable. Use Sidekick as the
company-controlled place for shared AI work when the goal is to move beyond
isolated personal conversations.

## 4. Control model selection

Use Relay to establish a traffic baseline, compare routing decisions, evaluate
candidate models, and move appropriate traffic to automatic routing. Keep
fallback, budget, and provider ownership explicit.

## 5. Run the review loop

<Steps>
  <Step title="Observe">
    Review adoption, activity, spend, tool posture, Sidekick work, and Relay
    traffic on a regular cadence.
  </Step>

  <Step title="Investigate">
    Move from aggregates to source, identity, workflow, and cost evidence.
  </Step>

  <Step title="Decide">
    Record the tool, access, routing, funding, or standardization decision in
    the surface that owns it.
  </Step>

  <Step title="Act">
    Carry out external provisioning, procurement, provider, identity, or
    endpoint changes in the system that owns them.
  </Step>

  <Step title="Measure">
    Confirm that adoption, spend, quality, latency, and risk changed as
    intended.
  </Step>
</Steps>

<Warning>
  Oximy evidence should support a company decision, not replace one. Validate
  source coverage and organizational context before making an individual or
  tool-level judgment.
</Warning>