Concept · Canonical Metric

Leverage in AI operator evaluation.

Leverage measures how much context an AI operator reuses and builds relative to new input. It is one of five canonical derived metrics in the MO§ES™ evaluation framework and is computed entirely from content-free token telemetry.

DERIVED DEVELOPMENTAL VALIDATION REQUIRED
Definition

The formula.

Leverage is the ratio of reused and newly built context to fresh input tokens. It captures how efficiently an operator converts new input into working context.

Leverage = (R + W) / I

Where:

  • R = Cache Read (reused context tokens)
  • W = Cache Write (new context built tokens)
  • I = Input (fresh tokens sent to the model)

A higher leverage value means the operator is getting more mileage out of context they have already established — either by reusing prior context (R) or by building new structured context (W) — relative to the fresh input they inject (I). A lower leverage value means the operator is feeding more raw input without building or reusing a context base.

Interpretation

What leverage tells you.

Leverage is not a productivity score. It is a structural signal that describes how an operator manages the context window across an AI session.

High Leverage

The operator reuses and builds context efficiently relative to new input. This may indicate effective session management, context window utilization, or multi-turn workflows where prior context compounds. It does not by itself prove better outcomes.

Low Leverage

The operator sends more fresh input relative to reused or built context. This may indicate single-turn patterns, fresh-start habits, or workflows that do not benefit from context accumulation. It is not inherently negative — some tasks are inherently input-heavy.

Leverage is most informative when read alongside the other four canonical metrics. An operator with high leverage but low yield may be building context without converting it to productive output. An operator with high leverage and high yield may be efficiently converting context investment into results. The metric gains meaning through combination, not in isolation.

How MO§ES™ Uses It

Leverage in the evaluation pipeline.

MO§ES™ computes leverage from canonical telemetry across every observed session for each operator. The metric enters the pipeline at three stages.

Measurement

Computed per session from INPUT, CACHE READ, and CACHE WRITE token counts. No prompt content required.

Benchmarking

Operators are ranked by leverage within their cohort. Percentile bands show where each operator falls relative to peers in the same workflow and model conditions.

Composite Score

Leverage contributes 30% of the AI Operator Development Index, the 0–100 composite score that summarizes overall operator behavior.

In the synthetic demo cohort of 50 operators across 1,668 observations, leverage values form a broad distribution. The top quartile shows materially higher context reuse and construction relative to input, while the bottom quartile tends toward input-heavy patterns. These are structural observations, not performance verdicts.

Governance Caveats

What leverage does not tell you.

Leverage is a derived metric labeled DEVELOPMENTAL. It is a structural signal whose relationship to actual performance outcomes is still being tested.

  • Not a productivity score. High leverage does not mean the operator is more productive. It means they manage context differently.
  • Not a quality measure. Leverage says nothing about the quality, correctness, or usefulness of the output produced.
  • Not an employee ranking. DEVELOPMENTAL labels mean results route workflows, not people. No adverse employment actions are permitted from pilot data.
  • Task-dependent. Some workflows are inherently input-heavy. Comparing leverage across different task types without controlling for task can produce misleading rankings.
  • Validation required. The relationship between leverage and validated business outcomes has not been independently established. Correlations are labeled ASSOCIATION, never CAUSATION.

Every leverage measurement carries provenance: source telemetry window, operator cohort, evidence label (DERIVED), decision-use label (DEVELOPMENTAL), and synthetic-data flag where applicable.

Related Concepts

Read alongside.

Productive output share of total token flow. O / (I + O + R + W).

Ratio of new context built to context reused. W / R.

The 0–100 AI Operator Development Index. Leverage contributes 30%.

Read the Methodology Request a Pilot