---
id: operating.task-index
title: Task index
summary: Route correctness work to the current project foundation, benchmark workspace, evaluation, or improvement surface.
kind: concept
product_area: operating_manual
status: stable
updated: 2026-09-07
canonical: /docs/operating-manual/task-index
---

# Task index

Use this index when you know the work that must happen but need the current product surface. First decide whether the object is a reusable project foundation or belongs to one benchmark workspace.

## Decision checkpoint

| Need | Open | Task |
| --- | --- | --- |
| Give agents stable project understanding | Agent Setup | [Maintain Project Context](/docs/agent-setup/project-context) |
| Connect and verify project knowledge | Agent Setup → Reference Materials | [Use Reference Materials](/docs/agent-setup/reference-materials) |
| Define case input and material shape | Project Settings → Input Schema | [Configure Project Input Schema](/docs/project-settings/input-schema) |
| Govern policies and rubrics | Correctness Governance | [Build policies and rubrics](/docs/operating-manual/build-policies-and-rubrics) |
| Create or inspect reusable cases | Assets → Cases | [Import and prepare cases](/docs/operating-manual/import-and-prepare-cases) |
| Edit a candidate implementation | Assets → Harnesses | [Harnesses](/docs/assets/harnesses) |
| Define reusable coverage structure | Coverage Facets | [Coverage Engineering](/docs/coverage-engineering) |
| Select benchmark cases and snapshots | Benchmark Datasets | [Benchmark Datasets](/docs/benchmark-datasets) |
| Find and close coverage gaps | Coverage Management | [Plan benchmark coverage](/docs/coverage-engineering/plan-benchmark-coverage) |
| Ask a specialist for judgment | Expert Contributions | [Request an Expert Contribution](/docs/expert-contributions/request-contribution) |
| Evaluate a saved candidate | Benchmark Evaluations | [Run a Benchmark Evaluation](/docs/benchmark-evaluations/run-evaluation) |
| Diagnose candidate behavior | Dashboard, List, Compare, or Arena | [Inspect evaluation results](/docs/benchmark-evaluations/inspect-results) |
| Coordinate a justified candidate change | Improve | [Start an Improvement Session](/docs/improve/start-improvement-session) |

## Route by scope

Project foundations are reusable across benchmarks. Project Context, Reference Materials, policies, rubrics, Coverage Facets, Cases, Harnesses, and Project Input Schema belong at project scope. Changing one can affect future work in several benchmarks.

Benchmark work is deliberately scoped. Dataset selection and snapshots, Coverage Management, Expert Contributions, Benchmark Evaluations, and Improvement Sessions belong to the selected benchmark or benchmark version. Confirm the benchmark selector before making changes or interpreting evidence.

## Route by evidence problem

If an evaluation fails, do not assume the Harness is responsible. An unclear Case belongs in Assets or case preparation. Missing behavior belongs in Coverage Management. Ambiguous correctness belongs in an Expert Contribution or Correctness Governance. A changed snapshot, setting, mapping, or metadata value belongs in evaluation diagnosis. Use Improve only when candidate work is justified by pinned evidence.

If agents lack source authority, update Reference Materials or Project Context before asking experts or generating more cases. If experts see the wrong fields or interaction, update Review Screen or the scoped Contribution rather than changing benchmark correctness.

{% example-demo title="Route a grounding regression" %}
A Run regresses on conflicting-source cases. The operator opens List and confirms that the cases, rubric, and settings are valid. Because the candidate selects a superseded document, the work belongs in Improve. If the expert could not determine which source controls, the same evidence would instead route to an Expert Contribution and Correctness Governance.
{% /example-demo %}

## Related workflows

{% related-card-grid title="Related workflows" %}
- [Product quickstart](/docs/quickstart)
- [First correctness loop](/docs/operating-manual/first-correctness-loop)
- [Operating Teammately end to end](/docs/getting-oriented/operating-teammately-end-to-end)
{% /related-card-grid %}

## Related reference pages

{% related-card-grid title="Related reference pages" %}
- [Product map](/docs/getting-oriented/product-map)
- [Key objects and relationships](/docs/getting-oriented/key-objects-and-relationships)
- [Reference library](/docs/reference)
{% /related-card-grid %}

## Source confidence

Code-backed: the task routing follows current project and benchmark navigation and the active owning routes for each workflow.