Teammately Docs
Docs menu

reference

Goal Contracts

Bind an Improvement Session to exact targets, measurable objectives, constraints, and permitted intervention scope.

Goal Contracts

Definition

A Goal Contract is the authority and measurement boundary for one Improvement Session. It turns a natural-language intent into canonical targets, prioritized objectives, protected constraints, and evaluable bindings.

Fields, states, or lifecycle rules

Contract contents

The contract identifies exact target IDs and records intent. Objectives carry priorities. Constraints are hard or soft. Measurement bindings name whether evidence should improve, preserve, or reduce a canonical Case, Policy, Rubric, metric, or other admitted reference. Intervention constraints state what work may change. Unresolved items remain explicit until the contract can be confirmed safely.

Every requested outcome needs an observable binding. “Make answers better” is not measurable; “improve the selected grounding Rubric while preserving the selected uncertainty Cases” is. A hard constraint disqualifies a candidate when violated. A soft constraint records a tradeoff that still requires review.

Revisions and confirmation

Goal Contract revisions can be proposed, confirmed, superseded, or rejected. Keep superseded and rejected revisions as history so candidate activity can be explained against the contract that authorized it. Do not silently edit the meaning of a session after work has begun.

Evolve locks the Goal Contract after the first epoch begins. If new evidence reveals a fundamentally different goal, stop or complete the current session and create an explicit new boundary rather than retrofitting prior epochs.

Confirmation checklist

  • Target Harness, Harness Version, Benchmark Version, and starting Run resolve to exact identities.
  • Each objective has a direction and canonical measurement binding.
  • Non-regression behavior is represented by preserve bindings or constraints.
  • Hard and soft constraints are distinguishable.
  • Intervention scope permits the intended code, prompt, retrieval, or configuration work.
  • No unresolved item makes evaluation or authorization ambiguous.

Related task pages

Task / ImproveStart an Improvement SessionStart from benchmark evidence, prepare a measurable Goal Contract, and choose bounded Work or Evolve behavior.Task / ImproveWork and EvolveChoose bounded implementation work or multi-branch evolutionary search with explicit epoch and provider authorization.

Source confidence

Code-backed: the active session contract and commands define canonical targets, objectives, constraints, measurement bindings, intervention scope, revision states, confirmation, and Evolve locking.

Found something unclear?

Report outdated, unsupported, or confusing docs so we can fix the source page.

Report a docs issue

Continue learning

Related docs

Improve Improve Coordinate durable Improvement Sessions from pinned benchmark evidence through Goal Contracts, candidates, evaluations, trajectories, and frontiers. Improve Start an Improvement Session Start from benchmark evidence, prepare a measurable Goal Contract, and choose bounded Work or Evolve behavior. Improve Candidates and the Current Frontier Interpret candidate stages, canonical receipts, constraints, retained Candidate Systems, and the current frontier.
AI context