Concept · Canonical Metric

Construction in AI operator evaluation.

Construction measures the ratio of new context an AI operator builds to context they reuse. It captures whether an operator is primarily creating fresh structured context or relying on context they have already established. It is one of five canonical derived metrics in the MO§ES™ evaluation framework.

DERIVED DEVELOPMENTAL VALIDATION REQUIRED
Definition

The formula.

Construction is the ratio of Cache Write tokens to Cache Read tokens. It measures how much new context the operator builds relative to how much existing context they reuse.

Construction = W / R

Where:

  • W = Cache Write (new context built tokens)
  • R = Cache Read (reused context tokens)

A construction value above 1.0 means the operator is building more new context than they are reusing. A value below 1.0 means they are reusing more than they build. A value near 1.0 means the operator is roughly balanced between construction and reuse. The metric is unitless and comparable across sessions of different sizes.

Interpretation

What construction tells you.

Construction is the context-building lens. It describes whether an operator's sessions are dominated by creating new structured context or by leveraging context that already exists.

High Construction

The operator builds more new context than they reuse. This may indicate original work — establishing new context windows, creating fresh structured prompts, or operating in workflows that require frequent context setup. It can also indicate a failure to leverage existing context efficiently.

Low Construction

The operator reuses more context than they build. This may indicate effective context management — carrying forward established context, building on prior sessions, or operating in workflows with stable context requirements. It can also indicate over-reliance on stale context.

Construction is not a quality signal in either direction. High construction is not inherently better than low construction, or vice versa. The metric's value lies in what it reveals about operating style and how it combines with the other canonical metrics. An operator with high construction and high yield is efficiently building new context and converting it to output. An operator with high construction and low yield may be building context that does not convert to productive generation.

How MO§ES™ Uses It

Construction in the evaluation pipeline.

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

Measurement

Computed per session from CACHE WRITE and CACHE READ token counts. No prompt content required — only token counts.

Benchmarking

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

Composite Score

Construction contributes 20% of the AI Operator Development Index, the 0–100 composite score. It is weighted equally with Token SNR.

In the synthetic demo cohort of 50 operators across 1,668 observations, construction values vary widely by workflow type. Operators in code generation workflows tend toward higher construction, while operators in analysis and review workflows tend toward higher reuse. These patterns are structural observations from synthetic data, not validated findings about which style produces better outcomes.

Governance Caveats

What construction does not tell you.

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

  • Not a quality measure. High or low construction says nothing about the quality, correctness, or usefulness of the context built or reused.
  • Not a productivity score. Construction measures context-building behavior, not work output or business value.
  • Not directional. Neither high nor low construction is inherently better. The metric is descriptive, not evaluative.
  • Not an employee ranking. DEVELOPMENTAL labels mean results route workflows, not people. No adverse employment actions are permitted from pilot data.
  • Validation required. The relationship between construction and validated business outcomes has not been independently established. Correlations are labeled ASSOCIATION, never CAUSATION.

Every construction 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.

How much context the operator reuses and builds relative to new input. (R + W) / I.

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

The 0–100 AI Operator Development Index. Construction contributes 20%.

Read the Methodology Request a Pilot