{"query":"Product map","corpusVersion":"local","generatedAt":"2026-09-13T04:32:31.546Z","results":[{"blockId":"orientation.product-map#product-map","pageId":"orientation.product-map","title":"Product map","pageTitle":"Product map","url":"https://teammately.ai/docs/getting-oriented/product-map.md","humanUrl":"https://teammately.ai/docs/getting-oriented/product-map#product-map","markdownUrl":"https://teammately.ai/docs/getting-oriented/product-map.md","sectionId":"product-map","kind":"concept","productArea":"introduction","score":980.9508094490109,"reasons":["search_match","title_match","display_title_match","term_match"],"markdown":"# Product map\n\nTeammately separates reusable project foundations from benchmark-scoped work. The Main UI uses the selected project and benchmark to route operators to the right scope. Experts receive a focused Expert contribution UI. Admin Console owns organization-level controls, while AI-assisted background work prepares and coordinates bounded tasks.\n\n> Surface routing\n>\n> Before changing an artifact, identify its scope. Project foundations can affect several benchmarks; dataset selection, Contributions, Evaluations, and Improvement Sessions belong to a selected benchmark or benchmark version."},{"blockId":"orientation.product-map#how-selection-affects-navigation","pageId":"orientation.product-map","title":"How selection affects navigation","pageTitle":"Product map","url":"https://teammately.ai/docs/getting-oriented/product-map.md","humanUrl":"https://teammately.ai/docs/getting-oriented/product-map#how-selection-affects-navigation","markdownUrl":"https://teammately.ai/docs/getting-oriented/product-map.md","sectionId":"how-selection-affects-navigation","kind":"concept","productArea":"introduction","score":324.618204552383,"reasons":["search_match","page_title_match","term_match"],"markdown":"## How selection affects navigation\n\nProject surfaces require a project. Benchmark surfaces also require a benchmark, and Evaluations or Improve may resolve the current benchmark version. If a destination is unavailable, confirm the current selectors before assuming that the feature or data is missing.\n\nProject folders and search help users move across a larger workspace, but they do not change artifact ownership. Search results and creation actions should preserve the selected project or benchmark scope.\n\n{% surface-map title=\"Teammately product surfaces\" %}\n{% /surface-map %}\n\n{% example-demo title=\"Route a new rubric need\" %}\nAn evaluation exposes inconsistent handling of expired agreements. The operator uses the benchmark workspace to request an Expert Contribution with the failed cases. The expert works in the focused contribution UI. The resulting rubric is reconciled in Correctness Governance at project scope, then included in a later benchmark version and evaluation.\n{% /example-demo %}"},{"blockId":"orientation.product-map#related-reference-pages","pageId":"orientation.product-map","title":"Related reference pages","pageTitle":"Product map","url":"https://teammately.ai/docs/getting-oriented/product-map.md","humanUrl":"https://teammately.ai/docs/getting-oriented/product-map#related-reference-pages","markdownUrl":"https://teammately.ai/docs/getting-oriented/product-map.md","sectionId":"related-reference-pages","kind":"concept","productArea":"introduction","score":314.1487224698692,"reasons":["search_match","page_title_match","term_match"],"markdown":"## Related reference pages\n\n{% related-card-grid title=\"Related reference pages\" %}\n- [Key objects and relationships](/docs/getting-oriented/key-objects-and-relationships)\n- [User roles](/docs/getting-oriented/user-roles)\n- [Product boundaries](/docs/introduction/product-boundaries)\n{% /related-card-grid %}"},{"blockId":"orientation.product-map#related-workflows","pageId":"orientation.product-map","title":"Related workflows","pageTitle":"Product map","url":"https://teammately.ai/docs/getting-oriented/product-map.md","humanUrl":"https://teammately.ai/docs/getting-oriented/product-map#related-workflows","markdownUrl":"https://teammately.ai/docs/getting-oriented/product-map.md","sectionId":"related-workflows","kind":"concept","productArea":"introduction","score":312.6224878794594,"reasons":["search_match","page_title_match","term_match"],"markdown":"## Related workflows\n\n{% related-card-grid title=\"Related workflows\" %}\n- [Task index](/docs/operating-manual/task-index)\n- [Operating Teammately end to end](/docs/getting-oriented/operating-teammately-end-to-end)\n- [Product quickstart](/docs/quickstart)\n{% /related-card-grid %}"},{"blockId":"coverage.overview#coverage-map-and-benchmark-evidence","pageId":"coverage.overview","title":"Coverage map and benchmark evidence","pageTitle":"Coverage Engineering","url":"https://teammately.ai/docs/coverage-engineering.md","humanUrl":"https://teammately.ai/docs/coverage-engineering#coverage-map-and-benchmark-evidence","markdownUrl":"https://teammately.ai/docs/coverage-engineering.md","sectionId":"coverage-map-and-benchmark-evidence","kind":"concept","productArea":"coverage_engineering","score":310.16425394276024,"reasons":["search_match","term_match"],"markdown":"## Coverage map and benchmark evidence\n\nA coverage map should identify meaningful combinations rather than isolated tags. A source-freshness Dimension may be well populated overall while the combination of superseded source, high customer impact, and exception request remains absent. Coverage Stories make those combinations operational; Case Foundry and expert contribution requests can then target them.\n\nRepresentation is evidence about the dataset, not proof that the benchmark is complete. A large or balanced count can still omit a critical boundary. Product teams should use specialist judgment to decide which gaps materially affect trust."},{"blockId":"intro.correctness-infrastructure#product-realization","pageId":"intro.correctness-infrastructure","title":"Product realization","pageTitle":"What is correctness infrastructure?","url":"https://teammately.ai/docs/introduction/correctness-infrastructure.md","humanUrl":"https://teammately.ai/docs/introduction/correctness-infrastructure#product-realization","markdownUrl":"https://teammately.ai/docs/introduction/correctness-infrastructure.md","sectionId":"product-realization","kind":"concept","productArea":"introduction","score":307.8558381129514,"reasons":["search_match","term_match"],"markdown":"## Product realization\n\nThe project foundation holds reusable context and assets. Correctness Governance owns policies and rubrics. Coverage Facets owns Dimensions, Project Topics, and Case Construction Patterns. Assets owns cases, harnesses, and other project-level resources, including reusable Comparison Directions and Review Screens. Agent Setup gives agents reusable project understanding through Project Context and Reference Materials. Expert Contributions configure scoped agent behavior and select the presentation and variation assets needed for the work.\n\nA benchmark workspace then creates a scoped operational loop. Benchmark Datasets defines the case set and snapshots. Coverage Management exposes represented and missing behavior. Expert Contributions requests governed human work. Benchmark Evaluations produces versioned evidence. Improve starts from that evidence and coordinates candidate exploration.\n\n{% layer-map title=\"Five capabilities of correctness infrastructure\" %}\n{% /layer-map %}\n\n{% example-demo title=\"Policy exception handling\" %}\nA support assistant must answer exception requests. Coverage Engineering identifies exception type, customer state, and source freshness as important facets. Correctness Elicitation records the expert rule for when an exception can be stated or must be escalated. Weave prepares ordinary, conflicting-source, and boundary cases. Trialground shows that a candidate handles ordinary cases but invents approval on ambiguous ones. Coevolve tests a harness change and keeps the resulting candidate tied to the exact failed cases and rubric evidence.\n{% /example-demo %}"},{"blockId":"orientation.product-map#definition","pageId":"orientation.product-map","title":"Definition","pageTitle":"Product map","url":"https://teammately.ai/docs/getting-oriented/product-map.md","humanUrl":"https://teammately.ai/docs/getting-oriented/product-map#definition","markdownUrl":"https://teammately.ai/docs/getting-oriented/product-map.md","sectionId":"definition","kind":"concept","productArea":"introduction","score":304.4963531561636,"reasons":["search_match","page_title_match","term_match"],"markdown":"## Definition\n\nThe **Main UI** begins at Project Home and groups project-level work into Correctness Governance, Coverage Facets, Assets, Agent Setup, and Project Settings. After a benchmark is selected, its workspace exposes Benchmark Overview, Benchmark Datasets, Coverage Management, Expert Contributions, Benchmark Evaluations, and Improve.\n\nThe **Expert contribution UI** presents one Contribution and its form, chat, interview, case-review, checkpoint, waiting, and completion states. The expert does not need the full project navigation to supply attributable judgment.\n\nThe **Admin Console** contains organization administration such as members, groups, roles, domain controls, integrations, and other code-backed administrative surfaces. Public docs keep detailed security, billing, retention, and compliance claims outside the boundary unless separately verified.\n\n**AI-assisted background work** can index reference material, prepare contributions, suggest coverage or standards, construct cases, run evaluations, and coordinate candidate exploration. Its outputs retain the authority of the owning artifact and workflow."},{"blockId":"orientation.product-map#decision-checkpoint","pageId":"orientation.product-map","title":"Decision checkpoint","pageTitle":"Product map","url":"https://teammately.ai/docs/getting-oriented/product-map.md","humanUrl":"https://teammately.ai/docs/getting-oriented/product-map#decision-checkpoint","markdownUrl":"https://teammately.ai/docs/getting-oriented/product-map.md","sectionId":"decision-checkpoint","kind":"concept","productArea":"introduction","score":304.4963531561636,"reasons":["search_match","page_title_match","term_match"],"markdown":"## Decision checkpoint\n\n| Work | Scope | Surface |\n| --- | --- | --- |\n| Project purpose and knowledge | Project | Agent Setup |\n| Policies and rubrics | Project | Correctness Governance |\n| Dimensions, Topics, and construction patterns | Project | Coverage Facets |\n| Reusable Cases and Harnesses | Project | Assets |\n| Input architecture | Project | Project Settings |\n| Benchmark-level run fields | Benchmark | Benchmark Evaluations |\n| Selected Cases, representation, and snapshots | Benchmark | Benchmark Datasets |\n| Coverage setup, Stories, Case Review, and Foundry | Benchmark | Coverage Management |\n| Specialist requests and contributed artifacts | Benchmark | Expert Contributions |\n| Runs, results, Compare, and Arena | Benchmark version | Benchmark Evaluations |\n| Goal Contracts, candidates, and frontier | Benchmark version | Improve |"}]}