Evaluation cells and budget accounting [ftip-00GE]
✍️sourceAGENTDRAFTED
Evaluation cells and budget accounting [ftip-00GE]
✍️sourceAGENTDRAFTED
Definition 1. Evaluation cell [ftip-00GF]AGENTDRAFTED
Definition 1. Evaluation cell [ftip-00GF]AGENTDRAFTED
An evaluation cell is \(C=(M,\mathsf Q,\mathsf I,b,\Lambda ,v)\), where \(M\) is an artifact, \(\mathsf Q\) a task law, \(\mathsf I\) an inference protocol, \(b\) a budget, \(\Lambda \) a seed kernel, and \(v\) an evaluator version. A cell comparison may differ in named coordinates only.
Lemma 2. Additive evaluation cost [ftip-00GG]AGENTDRAFTED
Lemma 2. Additive evaluation cost [ftip-00GG]AGENTDRAFTED
For a finite evaluation plan with disjoint stages of costs \(c_1,\ldots ,c_k\in \mathbb R_{\geq 0}\), total cost is \(c=\sum _{i=1}^k c_i\). Appending a stage increases cost by its declared amount and cannot preserve a budget \(B\) unless the remaining slack covers it.
Proof.
Proof.
The statement is the associativity and monotonicity of finite sums.
Theorem 3. Budget-preserving matched comparison [ftip-00GH]AGENTDRAFTED
Theorem 3. Budget-preserving matched comparison [ftip-00GH]AGENTDRAFTED
Let two evaluation plans use the same declared stages except for a substitution whose cost is at most the replaced stage cost. If their common prefix cost is \(c_0\) and both suffix costs fit \(B-c_0\), then both cells in Definition 1 are admissible under budget \(B\).
Proof.
Proof.
Apply Lemma 2 to the common prefix and each suffix. The assumed inequalities give total cost at most \(B\) in each plan.
Example 4. Cost-balanced evaluation cells [ftip-00GI]AGENTDRAFTED
Example 4. Cost-balanced evaluation cells [ftip-00GI]AGENTDRAFTED
A paired run can spend \(B=100\) units as 40 units of inference, 20 of evaluator calls, and 40 of audit. Replacing 10 inference units by 10 audit units preserves the budget, but changes the cell and must not be described as the same inference protocol.
Remark 5. Execution and evaluator confounds [ftip-00GJ]AGENTDRAFTED
Remark 5. Execution and evaluator confounds [ftip-00GJ]AGENTDRAFTED
A score change can arise from the artifact, prompt law, inference budget, parser, evaluator version, or execution failure. A matched-cell report names these coordinates before interpreting a paired gain.