Lemon Goal
Lemon Goal improves a saved Harness toward a benchmark objective through candidate experiments in Teammately. A useful change has an identifiable implementation, an explicit Goal and actual results.
Definition
Open Harness improvement → Lemon Goal to define the measured outcome, starting Harness and permitted changes. Lemon Goal investigates failures, develops candidates and tests them through Trialground.
Harness improvement also contains External Agents, a separate workflow that supplies a scoped task and pinned benchmark context for your coding agent in your own repository. Both workflows preserve the selected Benchmark Version and criteria.
Decision checkpoint
| Situation | Choose | Inspect |
|---|---|---|
| A saved Harness should meet numerical targets | Lemon Goal | Accepted criteria, candidate Versions and evaluations |
| Application code should change in your repository | External Agents | Pinned task context and actual before/after behavior |
| A result exposes an unclear rule | Expert Contribution | Specialist judgment and artifact decisions |
| Important input situations are missing | Coverage Design | Requirements and explicit Case adoption |
Learn from actual results
Inspect the full planned population before deciding a candidate is stronger. A focused success can guide another direction without replacing the complete comparison required by the Goal.
A candidate can gain on one criterion and regress another. Retained results and the Session's Evolution history should make that tradeoff explainable. A new Version is not automatically the best candidate.
Preserve the goal and the work
Lemon Goal records original instructions, targets and the starting candidate. Its conversation and Goal, Results, Evolution and Harnesses panels connect requested work to returned artifacts and measurements. A completed Session means the agent concluded; the reported outcome explains whether the Goal was achieved.
External Agents relies on the coding agent to inspect actual customer code, implement within the permitted scope and submit supported results. Setup or retrieval alone does not complete that task.
Return new questions upstream
Candidate work may expose a mistaken Case, unresolved applicability or an unrepresented input condition. Route those questions to the owning governance, expert or coverage workflow. Do not hide a broken standard by changing the candidate until it passes an ambiguous test.
Return the finding to the relevant expert, governance, or coverage workflow so your team can decide how it should affect the benchmark.