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

# Customer optimization overrides

> How to customize optimization choices with force-quantization, skip-technique, budget, latency, and quality controls.

## What you can override

RunInfra lets advanced users narrow the optimization search without changing the pipeline itself.

| Field                      | Type         | Effect                                                                                                 |
| -------------------------- | ------------ | ------------------------------------------------------------------------------------------------------ |
| `forceQuant`               | string       | Prefer a specific quantization mode when the selected model and runtime allow it.                      |
| `skipTechniques`           | string array | Skip techniques such as quantization, speculation, compile, expert-parallel, or disaggregated serving. |
| `maxBudgetUsd`             | number       | Set a spend ceiling for the optimization session.                                                      |
| `targetLatencyMs`          | number       | Override the latency target used by the optimizer.                                                     |
| `qualityRegressionCeiling` | number       | Tighten or relax the maximum accepted quality regression.                                              |
| `hardBans`                 | array        | Add tenant-policy bans that RunInfra must respect.                                                     |

## Safety rules

Overrides can narrow the search, but they cannot force an unsafe or incompatible deployment.

* Hard bans still apply even when a user forces a technique.
* If a skip list would remove every candidate, RunInfra restores a safe baseline instead of running an empty search.
* Budget ceilings are checked before promoting an optimized version.
* Quality gates still run before a candidate can replace the baseline.
* Plan gates still apply. Overrides do not unlock features outside the account plan.

## Examples

### Disable quantization for an embedding model

```ts theme={"dark"}
constraints.customerOverrides = {
  skipTechniques: ["quant"],
};
```

RunInfra keeps baseline and non-quantized embedding variants in the search.

### Prefer GPTQ INT4 for an LLM

```ts theme={"dark"}
constraints.customerOverrides = {
  forceQuant: "gptq_int4",
};
```

RunInfra uses the requested method only if the selected LLM and runtime support it.

### Ban FP8 for a tenant

```ts theme={"dark"}
constraints.customerOverrides = {
  hardBans: [
    { technique: "fp8_dynamic", modality: "llm", reason: "tenant policy" },
  ],
};
```

Any candidate that violates the policy is excluded from the run.

### Cap optimization spend

```ts theme={"dark"}
constraints.customerOverrides = {
  maxBudgetUsd: 5.0,
};
```

RunInfra treats this as a session spend ceiling, not a monthly traffic budget.

## Audit trail

Override decisions appear in the optimization reasoning shown to the user and are preserved with the optimization record so teams can review why a candidate was included, skipped, or rejected.