Equation 10 · The Economics of Codex: Tokens, Sandboxes, Review Time, and Software Throughput

What does this equation mean?

CAC=\frac{ C_{\mathrm{licenses}}+C_{\mathrm{usage}}+C_{\mathrm{runtime}} +C_{\mathrm{human}}+C_{\mathrm{rework}}+C_{\mathrm{incidents}} }{N_{\mathrm{accepted,quality-adjusted}}}.

Read the formula alongside the article passage below. Each part has a deeper page with its role in the equation, the supporting passage and nearby citations.

Start withC_licenses+C_usage+C_runtime +C_human+C_rework+C_incidents

Divide byN_accepted,quality-adjusted

This relates toCAC

How to read the two sides of this formula. Follow the article passage for the meaning of each quantity.

This equation states an equality: the expressions on both sides have the same value under the article’s assumptions. Read the equation part by part below; each part has a contextual explanation and a link to its mathematical background.

Read it piece by piece

C

Symbol C

C occurs above the fraction bar. The numerator is divided by the entire denominator below it.

Understand this part →

A

Symbol A

A is part of the quantity the equation computes from the expression on the right.

Understand this part →

C_{\mathrm{licenses}}

Symbol C_licenses

$C_l$ icenses occurs above the fraction bar. The numerator is divided by the entire denominator below it.

Understand this part →

C_{\mathrm{usage}}

Symbol C_usage

$C_u$ sage occurs above the fraction bar. The numerator is divided by the entire denominator below it.

Understand this part →

C_{\mathrm{runtime}}

Symbol C_runtime

$C_r$ untime occurs above the fraction bar. The numerator is divided by the entire denominator below it.

Understand this part →

C_{\mathrm{human}}

Symbol C_human

$C_h$ uman occurs above the fraction bar. The numerator is divided by the entire denominator below it.

Understand this part →

C_{\mathrm{rework}}

Symbol C_rework

$C_r$ ework occurs above the fraction bar. The numerator is divided by the entire denominator below it.

Understand this part →

C_{\mathrm{incidents}}

Symbol C_incidents

$C_i$ ncidents occurs above the fraction bar. The numerator is divided by the entire denominator below it.

Understand this part →

N_{\mathrm{accepted,quality-adjusted}}

Symbol N_accepted,quality-adjusted

$N_a$ ccepted,quality-adjusted occurs below the fraction bar. The quantity above the bar is divided by this expression; zero is excluded as a denominator.

Understand this part →

=

=

The expressions on both sides represent the same quantity under the stated assumptions.

Understand this part →

See an illustrated explanation →

fraction

fraction

Divide the expression above the line by the one below it.

Understand this part →

See an illustrated explanation →

addition

addition

Add the term after the plus sign to the term or group before it.

Understand this part →

subtraction

subtraction

Subtract the following term or group from the preceding one. A leading minus marks a negative quantity.

Understand this part →

subscript

subscript

The lower label selects a particular version, component, or indexed member of the quantity. For example, x₀ and xₜ can be values at different positions.

Understand this part →

C_{\mathrm{licenses}}+C_{\mathrm{usage}}+C_{\mathrm{runtime}} +C_{\mathrm{human}}+C_{\mathrm{rework}}+C_{\mathrm{incidents}}

Numerator: C_licenses+C_usage+C_runtime +C_human+C_rework+C_incidents

The complete quantity above the fraction bar.

Understand this part →

How to interpret it

With a fixed numerator, increasing a nonzero denominator reduces the fraction. Read it with the definitions, units, and assumptions supplied by the article.

What the article says around this equation

A practical organization can report cost per accepted change , $CAC=\frac{ C_{\mathrm{licenses}}+C_{\mathrm{usage}}+C_{\mathrm{runtime}} +C_{\mathrm{human}}+C_{\mathrm{rework}}+C_{\mathrm{incidents}} }{N_{\mathrm{accepted,quality-adjusted}}}$ . The metric should be sliced by task class. Documentation and test scaffolding, unfamiliar-repository bugs, migrations, UI work, security patches, and architecture decisions have different verification costs. A global mean can hide that agents create value in one class and consume it in another.

Read the equation in its article →

For background, read the article’s source list.

Return to The Economics of Codex: Tokens, Sandboxes, Review Time, and Software Throughput

See this formula across 1 published context →

Browse the mathematical compendium →