Lemon Goals
Definition
A Lemon Goal states the measured result a saved Harness should reach and the directions permitted to get there. Its accepted target identities, conditions, units and original instructions explain later candidate work.
Fields, states, or lifecycle rules
- A criterion refers to an exact benchmark metric, Policy, Rubric or Case scope.
- Conditions can express absolute thresholds, increases, decreases or preservation where supported by that metric.
- Resource criteria keep their actual units, such as latency, tokens or cost.
- Starting measurements are recorded when available; an absent measurement is shown as unmeasured.
- The Goal and its Session are created together.
- Original accepted instructions and earlier results remain attributable.
Define numerical criteria
Choose the criterion and a supported condition. Read the unit before entering the target: a score percentage, a count and a latency value have different meanings.
An absolute target states a threshold. A relative target states a change from the relevant starting measurement. Preserve the exact relationship rather than substituting a rounded display value. Percentage reduction from a measured zero cannot be interpreted as a positive reduction.
Choose constraints and an improvement direction that match the authorized scope. The available direction options can restrict work to prompts, model choice, a model family or configuration. They do not select a fixed implementation strategy for the agent.
Starting point
Select the saved Harness Version whose behavior should change. Inspect existing comparable measurements when present. An initial evaluation is not a universal creation prerequisite; the current target and admission rules determine what remains to be measured.
Missing data does not become a zero score, inferred baseline or invented success claim. The Session keeps starting evaluation and candidate evaluation distinct.
Traceability
Users edit or submit the current Goal through its supported controls. Accepted settings and instructions are captured automatically for interpretation and replay. Users do not need to name, publish or manage a separate prompt/configuration version.
Read Goal, Results and Evolution together when deciding whether a candidate satisfied the requested outcome. A completed Session and an achieved Goal are different statements.