Equation 9 · Claude Code, From First Principles: The Agentic Loop, Permissions, and What Actually Executes
What does this equation mean?
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.
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
Symbol c_t+1
+1 is the next indexed value computed from the current indexed quantity and the update terms shown on the right.
Symbol c_t
is an input to the expression that computes the quantity on the left.
Symbol a_t
is an input to the expression that computes the quantity on the left.
=
The expressions on both sides represent the same quantity under the stated assumptions.
See an illustrated explanation →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.
How to interpret it
Read it with the definitions, units, and assumptions supplied by the article.
What the article says around this equation
Claude Code executes — subject to a permission check described in the next section — against the real filesystem, shell, or network, producing an observation : a diff applied, a command’s stdout and exit code, a search result. That observation is appended to the context for the next step: . The loop repeats until emits a stop rather than a tool call. Nothing in this is exotic; it is the standard shape of a tool-using agent. What matters for this article is what each symbol is standing in for in a real, shipped product: is not a hypothetical action but a call to a real interpreter with real side effects on a real machine, is not simulated feedback but…
Read the full surrounding passage
Claude Code executes — subject to a permission check described in the next section — against the real filesystem, shell, or network, producing an observation : a diff applied, a command’s stdout and exit code, a search result. That observation is appended to the context for the next step: . The loop repeats until emits a stop rather than a tool call. Nothing in this is exotic; it is the standard shape of a tool-using agent. What matters for this article is what each symbol is standing in for in a real, shipped product: is not a hypothetical action but a call to a real interpreter with real side effects on a real machine, is not simulated feedback but the actual return value of that call, and the boundary between “the model decided” and “the harness allowed” is enforced by software, not by the model’s own restraint.
Sources cited in the article section
- [2] How Claude Code works ↗
- [11] Dive into Claude Code: The Design Space of Today's and Future AI Agent Systems ↗
These citations give research context. Read each source to check which claims it supports.