---
id: intro.correctness-infrastructure
title: AI Alignment Infrastructure
summary: Connect expert judgment, explicit standards, coverage, and experiments into an enduring capability for improving enterprise AI.
kind: concept
product_area: introduction
status: stable
updated: 2026-11-06
canonical: /docs/introduction/correctness-infrastructure
---

# AI Alignment Infrastructure

Your enterprise’s expertise lives in the way people do their work. A specialist recognizes a missing constraint. A reviewer explains why two similar situations require different decisions. A team knows which tradeoffs it accepts and who can settle a disagreement.

AI Alignment Infrastructure carries that knowledge into development and keeps it useful as systems and requirements change.

## Definition

Teammately connects the work of experts, product owners, and engineers:

- **Lemon Elicit** prepares contributions and follows the reasoning behind expert decisions.
- **Rubrics and Policies** express requirements, applicability, and how judgments combine.
- **Coverage Engineering** defines which situations the benchmark should represent.
- **Lemon Weave** constructs Cases, supporting material, and targeted training examples.
- **Trialground** executes saved Harnesses and assesses recorded behavior.
- **Lemon Code and Lemon Goal** develop and investigate candidate implementations.

These capabilities reinforce one another. A surprising trial can reveal an omitted condition. A specialist’s qualification can change the rubric and the Cases needed to exercise it.

## Decision checkpoint

| Question | Begin with | Useful result |
| --- | --- | --- |
| Which distinction changes the expert’s decision? | Expert Contributions | A reason, condition, or exception |
| How should the system be assessed? | Correctness Governance | Applicable rubrics and Regime treatment |
| Which situations should be represented? | Coverage Design | Stories, tuples, and intended proportions |
| What did the candidate actually do? | Trialground | Responses, captured trajectories, and judgments |
| What should development investigate? | Lemon Code, Lemon Goal, or Weights training | A candidate intervention and a way to assess it |

## Make expertise reusable

A single expert answer can inform more than one example. Preserving its reasoning lets a team apply the distinction across Cases, investigate exceptions, and return with a focused question when a later result challenges the standard.

The Project Agent Brief and Reference Materials supply shared context. Contributions retain the specialist’s judgment. Policies and rubrics express accepted standards. Benchmarks make the situations and criteria explicit. Experiments show how a candidate behaves under those conditions.

## Keep the development decision connected

A benchmark score is useful when the team can trace it to the conditions tested and the criteria applied. Inspect which requirements improved, which regressed, and whether the Case population supports the intended conclusion.

Engineers can use that finding to change retrieval, instructions, tools, or orchestration, or to prepare material for weights training. Experts can clarify a requirement when the result exposes an unresolved judgment.

{% example-demo title="A recommendation that fits the business" %}
A merchant explains why a relevant product is a poor substitute when a required accessory is unavailable. Lemon Elicit develops the qualification into a proposed criterion. Coverage Design represents availability and substitution conditions. Trialground compares recommendation Harnesses, and the engineer can see whether a change respects the merchant’s distinction across those Cases.
{% /example-demo %}

## Related workflows

{% related-card-grid title="Put the connection to work" %}
- [Product Quickstart](/docs/quickstart)
- [Working with Lemon](/docs/concepts/lemon)
- [The Teammately Correctness Lifecycle](/docs/introduction/correctness-lifecycle)
{% /related-card-grid %}

## Related reference pages

{% related-card-grid title="Find the right scope" %}
- [Product Map](/docs/getting-oriented/product-map)
- [Object Model](/docs/object-model)
- [Product Responsibilities](/docs/introduction/product-boundaries)
{% /related-card-grid %}
