Before you can read the parent note, you need to meet each piece of notation as a friend, not a stranger. We build them one at a time, each on top of the last. Nothing appears before it is defined.
Let's start with the simplest picture: a robot facing a world.
Look at the figure. The blue box is the agent. The navy cloud is the environment. The yellow arrow going out is an action; the green arrow coming back is an observation (what the agent now sees) plus a reward (a score for that step). This loop repeats.
Why the topic needs this: every metric on the parent page is really counting something inside this loop — how many loops (steps), whether the final loop reached the goal, whether any loop broke a rule.
Related idea in the vault: Tool Use in Language Models and Reinforcement Learning Basics both live inside exactly this loop.
The parent writes things like r1,r2,…,rT and ∑i=1n. Before those make sense, you need the idea of a subscript — and you need to know what the letter r stands for.
Picture a row of numbered lockers. r1 is the reward in locker 1, r2 the reward in locker 2. The letter t or i is a placeholder for "some locker number" — when we write rt we mean "whichever step we're currently pointing at."
Why the topic needs this: an agent's journey is a list of steps. Subscripts let us name step 1, step 2, ... step T without inventing a new letter each time.
The figure shows one trajectory as a chain of dots. Each dot is a step; the yellow number under it is the reward rt collected at that step. Success or failure is decided by the whole chain.
The parent writes P(success)=∏i=1nP(success at step i). Two symbols hide here. (Here n is just the number of steps — the same count we called T in §3; the parent happens to write n in this one formula.)
Why multiply, not add? Because to reach step 3 you must survive step 1 and step 2 and step 3. "And" of independent chances is a product. That is why chances compound: each new step is another factor below 1, dragging the total down.
The red curve shows overall success collapsing as the number of steps grows, even though each step is a healthy 90%. Read it as: long journeys are fragile.
Why the topic needs this: one trajectory's score Ri is noisy luck. Running N episodes and averaging gives the agent's typical performance. This is the backbone of A/B Testing and every benchmark table.
Picture flipping a bent coin. The real bias p is hidden inside the coin. After 100 flips you only have p^, your measured fraction k/n. The hat is a humble symbol: it admits "this is a guess."
The figure shows two agents' measured success rates as dots with error bars (the ± range). When the bars overlap, you cannot claim one agent beats the other — the difference might be luck. This is why the parent insists n≥100 episodes: more episodes shrink SE, shrinking the bars until they separate.
The parent writes R=∑t=1Tγt−1rt (note this sums over stepst within one episode, using lowercase rt from §2).
Why an exponent, and why this tool? Each extra step adds one more layer of uncertainty. Multiplying by γonce per step means the doubt compounds — exactly the same "and-of-chances" logic as the product in §4, but now applied to value instead of survival. An exponent is the natural tool for "same shrink, repeated every step."
Many parent metrics are just one count divided by another — a ratio answers "what fraction?"
How to read any ratio: the bottom is "how many chances there were," the top is "how many went the way we wanted." All four land between 0 and 1, so they're directly comparable. Precision/recall detail: Human Evaluation Protocols.