# Expert Contributions
Generated: 2026-11-11T10:29:50.616Z
Source build: local
Canonical docs: https://teammately.ai/docs
---
id: expert-contributions.overview
title: Expert Contributions
summary: Coordinate benchmark-scoped expert work, attributable judgment, governed artifacts, and the decisions that move correctness forward.
kind: concept
product_area: expert_contributions
status: stable
updated: 2026-11-06
canonical: /docs/expert-contributions
---
# Expert Contributions
Expert Contributions is the benchmark-scoped workspace for requesting, conducting, and materializing specialist work. It coordinates the expert, objective, selected context, task sequence, checkpoints, attributable responses, and contributed artifacts needed to move a benchmark forward.
## Definition
The administrator workspace contains **Contributions**, **Contributed Artifacts** and **Logs & Status**. The workspace entry opens Contributions. **Request Contribution** opens the composer for a new contribution. The expert follows a contribution-specific experience that can contain form, chat, interview, and case-review tasks, along with checkpoints and completion states.
A Contribution is the unit of requested expert effort. It replaces broad workflow configuration with a bounded statement of what this benchmark needs from this expert now. The work can result in contributed policies, rubrics, cases, or coverage observations without flattening all expert activity into one generic approval record.
## Decision checkpoint
| Need | Contribution element | Result to inspect |
| --- | --- | --- |
| Resolve a specific benchmark question | Contribution statement and scoped objectives | The expert can explain the requested decision |
| Ground work in concrete behavior | Selected or designated cases | Case-level responses remain attributable |
| Supply supporting knowledge | Attachments and scoped statements | The expert sees the relevant source boundary |
| Choose the right interaction | Form, chat, interview, or case review task | Task output matches the kind of judgment needed |
| Confirm consequential learning | Checkpoint | Accepted, revised, or unresolved state is explicit |
| Reuse the result | Contributed Artifacts | Policies, rubrics, cases, and coverage observations retain provenance |
## Lifecycle and status
The durable Contribution statuses are `PREPARING_DIRECTION`, `AWAITING_DIRECTION_ALIGNMENT`, `MATERIALIZING_TASKS`, `READY`, `IN_PROGRESS`, `COMPLETED`, and `CANCELLED`. The interface presents these as planning direction, waiting for alignment, preparing tasks, ready, active, completed, or cancelled. The exact task sequence can vary by Contribution.
Realtime updates and durable transitions help the administrator and expert see current progress without inventing completion. A waiting state, checkpoint, or finalization step should be shown as such. Completing the expert experience does not imply that every proposed artifact has been accepted into its project-level owner.
## Responses and findings
Logs & Status exposes operational and engagement records. Contributed Artifacts organizes materialized or contributed cases, policies, rubrics, and new coverage observations. Correctness Governance, Assets, or Coverage Design owns the resulting project or benchmark artifact after materialization.
This model improves return on expert effort. Agents prepare focused work from project context, indexed material, benchmark cases, and unresolved questions. The expert supplies the authority; the result can be reused across standards, coverage, evaluation, and improvement.
{% example-demo title="Resolve source authority" %}
A benchmark contains cases where an operational runbook conflicts with a newer policy page. The operator requests a Contribution from the policy owner, selects the conflicting cases, attaches both sources, and uses case review plus a checkpoint. The expert establishes which source controls, contributes a scoped policy and rubric, and records one coverage observation for an unrepresented exception.
{% /example-demo %}
## Related workflows
{% related-card-grid title="Related workflows" %}
- [Request an Expert Contribution](/docs/expert-contributions/request-contribution)
- [Complete an Expert Contribution](/docs/expert-contributions/complete-contribution)
- [Build policies and rubrics](/docs/operating-manual/build-policies-and-rubrics)
{% /related-card-grid %}
## Related reference pages
{% related-card-grid title="Related reference pages" %}
- [Contributed Artifacts](/docs/expert-contributions/contributed-artifacts)
- [Contribution Lifecycle and Status](/docs/expert-contributions/lifecycle-and-status)
- [Logs & Status](/docs/expert-contributions/logs-and-status)
- [Agent Setup](/docs/agent-setup)
- [Human Approval Boundaries](/docs/governance/human-approval-boundaries)
{% /related-card-grid %}
---
id: expert-contributions.complete
title: Complete an Expert Contribution
summary: Explain your judgment, review Lemon’s interpretation, and complete the assigned contribution through discussion and focused review.
kind: task
product_area: expert_contributions
status: stable
updated: 2026-11-06
canonical: /docs/expert-contributions/complete-contribution
---
# Complete an Expert Contribution
Your expertise helps the team understand what good behavior requires and why. Read the assignment, examine the prepared material, and explain the condition, exception, or tradeoff behind your judgment.
Lemon can follow up on your answers and bring proposed interpretations back for review.
## Prerequisites
- Your authenticated Contribution link and assigned work.
- The Case, reference material, or question you are being asked to examine.
- Microphone permission for a voice interview.
## Steps
1. Open the Contribution and read its objective and assignment context.
2. Examine the Case, outputs, or question presented. Follow the relevant documents and attachments when they affect your decision.
3. Use the review, comparison, form, conversation, or interview controls to explain your judgment.
4. Point out a missing condition or uncertainty when it changes the answer.
5. Review proposed policies, applicability, and rubrics. Use their decision controls to accept, reject, or correct the interpretation.
6. Continue through the assigned work and its final review. Read the completion message for the Contribution.
## Work through a conversation or a focused review
In a conversational Contribution, Lemon brings questions and prepared activities into the discussion. Open the presented review or interview when it helps examine the distinction. You can return to completed activities and earlier messages for context.
Focused reviews let you inspect a Case, curate an answer, compare alternatives, or assess a recorded trajectory. Explain why the choice matters so the team can apply your reasoning beyond that example.
## Review the proposed standard
Read the exact wording and the Cases to which it applies. Correct an omitted exception or a scope that changes your meaning. Discussion develops the interpretation; the artifact’s approval or rejection control records your decision on that proposal.
Final policy review brings the resulting interpretation back to you before the Contribution moves through its remaining rubric and completion work.
## Continue smoothly through the assignment
Next and Skip move to prepared work while saved answers are delivered in the background. If delivery needs attention, retain your answer and follow the displayed recovery guidance.
Finalization preserves submitted work while the Contribution settles its remaining decisions. The completion message identifies when the assignment is finished.
## Object and state changes
Your responses, rationale, and artifact decisions stay attached to the Contribution and the content reviewed. Accepted findings can inform policies, rubrics, Cases, and coverage through their owning workflows.
## Success criteria
- Your reasoning and important qualifications are clear.
- Proposed standards preserve your intent and applicability.
- Explicit artifact decisions reflect the wording you reviewed.
- The Contribution reaches its completion state.
## Common failure modes
- Choosing an answer without explaining the condition behind it.
- Accepting wording that omits a consequential exception.
- Using conversational agreement in place of the proposal’s decision control.
- Re-entering a different answer while an earlier submission is being saved.
{% example-demo title="Qualify an exception" %}
Lemon proposes that expired agreements should always be ignored. You explain that an older agreement can remain controlling when the current contract incorporates it. Review the revised policy and its applicable Cases, then record your decision on the corrected interpretation.
{% /example-demo %}
## Related reference pages
{% related-card-grid title="Understand your contribution" %}
- [Expert UI](/docs/integrations/reviewer-workspace)
- [Contributed Artifacts](/docs/expert-contributions/contributed-artifacts)
- [Contribution Lifecycle and Status](/docs/expert-contributions/lifecycle-and-status)
{% /related-card-grid %}
## Related troubleshooting pages
{% related-card-grid title="Resume your work" %}
- [Expert Contribution Problems](/docs/troubleshooting/expert-contributions)
- [Permissions](/docs/troubleshooting/permissions)
{% /related-card-grid %}
---
id: expert-contributions.artifacts
title: Contributed Artifacts
summary: Inspect Policy and Rubric contributions and coverage observations while retaining expert provenance and separate adoption decisions.
kind: reference
product_area: expert_contributions
status: stable
updated: 2026-10-30
canonical: /docs/expert-contributions/contributed-artifacts
---
# Contributed Artifacts
## Definition
Contributed Artifacts presents specialist outputs in **By Policy**, **By Rubric** and **Observations** views. Use it to inspect attributable material and its relationship to the Contribution that produced it.
## Fields, states, or lifecycle rules
- Policy and Rubric records preserve the expert context and artifact decision.
- Coverage observations describe input situations that need attention.
- Contribution completion and artifact approval are separate.
- An observation's confirmation is distinct from applying a dataset change.
- Original task, source and checkpoint relationships remain attributable.
- Current artifact ownership stays with Correctness Governance, Assets or Coverage Design.
## Read an artifact
Begin with its actual content and lifecycle state. Follow the Contribution and relevant responses to understand what was asked and what the expert decided.
A draft proposal, retained candidate and approved standard have different meanings. Comments and interviews can inform a decision without establishing approval of every related object.
Keep a changed applicability boundary distinguishable from an unchanged policy statement. Similar wording does not establish that two artifacts cover the same situation.
## Act on observations
Effective expert-confirmed input-coverage observations and attributable new Input Cases can reach Coverage Design Inbox after the source settles. Inbox owns the later generate/add/remove/no-change/decline decision.
Generating a Case does not adopt it automatically. Likewise, a report can become Resolved through a declined or withdrawn item without changing the dataset.
## Preserve historical interpretation
A current Policy or Rubric can evolve after a Contribution. Existing Benchmark Versions and Runs retain the standard and population they accepted. Correct current material through its owning workflow rather than rewriting an earlier expert answer or completed Run.
Use provenance to explain the decision, not to infer authority from activity volume or a completed status alone.
## Related task pages
{% related-card-grid title="Related task pages" %}
- [Contribution Lifecycle and Status](/docs/expert-contributions/lifecycle-and-status)
- [Policies and Rubrics](/docs/correctness-governance/policies-and-rubrics)
- [Input Coverage Inbox](/docs/coverage-design/inbox)
{% /related-card-grid %}
---
id: expert-contributions.lifecycle
title: Contribution Lifecycle and Status
summary: Read Contribution progress, assigned activities, artifact decisions, and completion.
kind: reference
product_area: expert_contributions
status: stable
updated: 2026-11-06
canonical: /docs/expert-contributions/lifecycle-and-status
---
# Contribution Lifecycle and Status
## Definition
Contribution status, task status, expert-runtime state, and checkpoint state describe different layers. Read them together before diagnosing delay or declaring completion.
## Fields, states, or lifecycle rules
### Contribution status
| Status | Meaning |
| --- | --- |
| `PREPARING_DIRECTION` | Teammately is planning the direction and requested work |
| `AWAITING_DIRECTION_ALIGNMENT` | An administrator decision or alignment is required |
| `MATERIALIZING_TASKS` | The confirmed plan is becoming executable expert activities |
| `READY` | Work is prepared and available to the expert |
| `IN_PROGRESS` | At least part of the expert work is active |
| `COMPLETED` | Required expert work and finalization reached the durable terminal state |
| `CANCELLED` | Further work was stopped while preserving the record |
Planned activities can be Case Review, Form, Chat, or Interview. An individual review task can be preparing, blocked, ready, in progress, completed, skipped, or superseded. A superseded task remains provenance for what changed; it should not be counted as current outstanding work.
### Runtime and checkpoints
The expert runtime moves through preparing, ready, active, final checkpoint, completed, or exhausted. `EXHAUSTED` means the current executable path has no further work; it is not a synonym for a successfully completed Contribution.
A checkpoint moves from preparing to ready to reconciled. Its requirements may be pending, retryable, materialized, terminal-empty, or failed. Checkpoints can consolidate requirements, capture Policy meaning, prepare or record an Interview, or materialize Rubric meaning. A ready checkpoint still needs the expert's reconciliation.
### Diagnosing state
If the Contribution is `IN_PROGRESS` but the expert sees no action, inspect the current task, runtime, and checkpoint. A blocked task may be waiting for required context; a final checkpoint may need confirmation; an exhausted runtime may require administrator follow-up. Use Logs & Status for recorded timing and engagement rather than relying on a stale open browser view.
> Completion boundary
>
> `COMPLETED` makes responses and findings available for downstream governance. It does not automatically approve a Policy or Rubric, select a Case into a benchmark, or apply a coverage observation.
## Related task pages
{% related-card-grid title="Related task pages" %}
- [Request an Expert Contribution](/docs/expert-contributions/request-contribution)
- [Complete an Expert Contribution](/docs/expert-contributions/complete-contribution)
{% /related-card-grid %}
---
id: expert-contributions.logs-status
title: Logs & Status
summary: Inspect Output Reviews, Policies, Rubrics, Interviews, and Expert Engagement within the selected Benchmark.
kind: reference
product_area: expert_contributions
status: stable
updated: 2026-10-30
canonical: /docs/expert-contributions/logs-and-status
---
# Logs & Status
## Definition
Logs & Status is the Benchmark-scoped operational view for Expert Contributions. Its current sections are **Output Reviews**, **Policies**, **Rubrics**, **Interviews** and **Expert Engagement**.
## Fields, states, or lifecycle rules
- Every section retains the selected Benchmark scope.
- A review, interview, policy decision and engagement record have separate identities.
- Filtering and sorting change the view rather than the source decision.
- Available transcripts and response details follow current permission.
- Task activity, artifact approval and final completion remain different outcomes.
## Choose a record
Use Output Reviews to inspect response judgments and their originating work. Policies and Rubrics show the corresponding specialist review records. Interviews identifies sessions and their available transcript or result context. Expert Engagement describes participation rather than approval quality.
Read a visible count against its population and state. A large number of interactions does not establish that an artifact was accepted, and a completed interview does not establish that its proposed Policy was approved.
## Trace delayed results
Follow the exact Contribution and task before treating a waiting state as an ownership failure. Locally staged answers, server recording, artifact materialization and checkpoint reconciliation can settle separately.
Use the current session details when diagnosing editing ownership. Descriptions of a browser, device or approximate location are context for the admitted session; they do not grant authority or establish that another device's drafts are safe to discard.
## Keep scope intact
A log view is not a substitute for the artifact's current state. Open the owning Policy, Rubric or Contribution to inspect its decision. Use Coverage Design Inbox for adoption of an input-coverage observation.
Do not rewrite expert attribution, infer decisions from commentary or mark unrelated work complete to clear an operational count.
## Related task pages
{% related-card-grid title="Related task pages" %}
- [Contribution Lifecycle and Status](/docs/expert-contributions/lifecycle-and-status)
- [Contributed Artifacts](/docs/expert-contributions/contributed-artifacts)
- [Complete an Expert Contribution](/docs/expert-contributions/complete-contribution)
{% /related-card-grid %}
---
id: expert-contributions.request
title: Request an Expert Contribution
summary: Write a focused request, choose an expert, attach relevant project context, and inspect the prepared plan before requesting review.
kind: task
product_area: expert_contributions
status: stable
updated: 2026-11-06
canonical: /docs/expert-contributions/request-contribution
---
# Request an Expert Contribution
Use the Contribution composer to explain what specialist judgment the Benchmark needs. The request blueprint supplies context; the prepared plan makes the resulting work inspectable.
## Prerequisites
- A selected Project and Benchmark.
- An eligible expert.
- A concrete objective or unresolved question.
- Relevant Cases or source context when the question depends on them.
## Steps
1. Open **Expert Contributions → Contributions** and create a request.
2. Write the objective or mission in the request blueprint.
3. Type **@** to attach relevant context or **/** to choose available skills. Use attachments to identify the intended objects rather than relying on similar titles.
4. Choose the expert and inspect the displayed recommendations or activity where useful.
5. Attach the Cases, standards and review assets needed to explain the judgment.
6. Submit the request for planning.
7. Inspect the prepared direction, scope and activities before **Request expert review**.
8. Follow attributable responses, decisions and completion through the Contribution.
## Context and review assets
The composer can include Policies, Rubrics, Dimensions and ontology values, Topics and Topic Groups, Scenarios, Benchmark Cases, Comparison Directions, a Review Screen and Fieldloop Threads.
Choose one Review Screen. Comparison Directions guide alternatives; review-component selections express the kinds of work the planner can prepare. They do not approve the resulting content or force one conversational sequence.
Include Cases when they make the question concrete. A direct expert inquiry can begin with the relevant project context, reference material, and a clear learning objective.
## Object and state changes
Creation records the request, selected expert and contextual scope. Planning prepares the direction and activities; alignment authorizes the intended work. Assignment, visible task progress, artifact decisions and final Contribution completion remain separate.
Already accepted or completed work is not silently replaced by a later planning or settings edit.
## Success criteria
- The expert's requested judgment is clear.
- Attached objects and source context match that judgment.
- The prepared plan stays within the request.
- Review presentation and response alternatives have the intended scope.
## Common failure modes
- Writing a broad mission that leaves the learning objective unclear.
- Treating a comparison asset as an approved standard.
- Attaching more than one Review Screen.
- Using a persistent instruction for a one-time question.
- Assuming task completion approves every contributed artifact.
## Related reference pages
{% related-card-grid title="Related reference pages" %}
- [Complete an Expert Contribution](/docs/expert-contributions/complete-contribution)
- [Contributed Artifacts](/docs/expert-contributions/contributed-artifacts)
- [Review Screens](/docs/assets/review-screens)
- [Comparison Directions](/docs/assets/comparison-directions)
{% /related-card-grid %}
## Related troubleshooting pages
{% related-card-grid title="Related troubleshooting pages" %}
- [Expert Contribution problems](/docs/troubleshooting/expert-contributions)
- [Permissions troubleshooting](/docs/troubleshooting/permissions)
{% /related-card-grid %}
---
id: concepts.correctness-elicitation
title: Lemon Elicit
summary: Uncover the reasoning, preferences, and exceptions behind expert judgments and develop them into reviewed standards.
kind: concept
product_area: correctness_elicitation
status: stable
updated: 2026-11-06
canonical: /docs/concepts/correctness-elicitation
---
# Lemon Elicit
An expert’s choice often raises the next useful question. Which condition changed the decision? Was it a requirement or a preference? Would the same judgment apply in another operating context?
Lemon Elicit prepares and adapts Contributions to explore those distinctions. Experts contribute their reasoning while Lemon organizes the context, questions, and interpretation.
## Definition
Elicitation can take the form of output curation, pairwise or listwise comparison, trajectory review, a form, chat, or a voice interview. The learning objective gives the work its purpose.
Lemon develops findings into proposed policies, rubrics, and coverage. Experts inspect whether those proposals preserve their intent. An unresolved qualification gives the team a focused reason to continue the inquiry.
## Decision checkpoint
| What the team needs to understand | Useful contribution | What to examine |
| --- | --- | --- |
| What makes an answer acceptable | Curation | The answer, correction, and rationale |
| Why one approach is preferable | Pairwise or listwise comparison | The tradeoff and the condition that changes it |
| Whether the path was acceptable | Trajectory review | Recorded reasoning summaries, tool use, and actions |
| Knowledge beyond the prepared example | Form, chat, or interview | Explanation, exceptions, and follow-up questions |
| Whether a proposed standard preserves intent | Policy or rubric review | Wording, applicability, and the explicit decision |
## Prepare the context
Project Context supplies the Project Agent Brief. Reference Materials provides indexed project knowledge. The Contribution selects its objective, experts, Cases, contextual attachments, and permitted work. Review Screens shape presentation; Comparison Directions guide alternatives.
An expert should be able to see why the question matters and which information supports it. Ask for a focused distinction the team can put to use.
## Review the interpretation
A specialist’s explanation may reveal a missing condition, an exception, or a responsibility shared across teams. Inspect the proposed policy and its applicability alongside the Cases that make the distinction concrete.
Use the presented approval controls to accept or reject the exact standard. Discussion lets the expert qualify meaning; the explicit decision records whether the proposed artifact should move forward.
## Carry the finding into development
Accepted criteria guide benchmark assessment. Coverage observations identify situations the team should represent. Lemon Weave constructs material around those distinctions, while Trialground and Harness improvement use the resulting benchmark to investigate behavior.
{% example-demo title="When a substitute is acceptable" %}
A merchant prefers one alternative because it preserves a customer’s required use. A follow-up reveals that the preference changes when an accessory is unavailable. Lemon Elicit develops the qualification into proposed criteria and a coverage observation. The expert reviews both before the team uses them to guide recommendation development.
{% /example-demo %}
## Related workflows
{% related-card-grid title="Work with your experts" %}
- [Request an Expert Contribution](/docs/expert-contributions/request-contribution)
- [Complete an Expert Contribution](/docs/expert-contributions/complete-contribution)
- [Contributed Artifacts](/docs/expert-contributions/contributed-artifacts)
{% /related-card-grid %}
## Related reference pages
{% related-card-grid title="Express the resulting standard" %}
- [Rubrics and Policies](/docs/correctness-governance/policies-and-rubrics)
- [Comparison Directions](/docs/assets/comparison-directions)
- [Review Screens](/docs/assets/review-screens)
{% /related-card-grid %}