{"query":"Boundary Cases","corpusVersion":"local","generatedAt":"2026-09-13T04:36:50.991Z","results":[{"blockId":"coverage.boundary-cases#boundary-cases","pageId":"coverage.boundary-cases","title":"Boundary Cases","pageTitle":"Boundary Cases","url":"https://teammately.ai/docs/coverage-engineering/boundary-cases.md","humanUrl":"https://teammately.ai/docs/coverage-engineering/boundary-cases#boundary-cases","markdownUrl":"https://teammately.ai/docs/coverage-engineering/boundary-cases.md","sectionId":"boundary-cases","kind":"concept","productArea":"coverage_engineering","score":955.513679676354,"reasons":["search_match","title_match","display_title_match","term_match"],"markdown":"# Boundary Cases"},{"blockId":"playbooks.enterprise-assistant-review#contribution-boundary","pageId":"playbooks.enterprise-assistant-review","title":"Contribution boundary","pageTitle":"Running Expert Contributions for an Enterprise Assistant","url":"https://teammately.ai/docs/playbooks/running-expert-contributions-enterprise-assistant.md","humanUrl":"https://teammately.ai/docs/playbooks/running-expert-contributions-enterprise-assistant#contribution-boundary","markdownUrl":"https://teammately.ai/docs/playbooks/running-expert-contributions-enterprise-assistant.md","sectionId":"contribution-boundary","kind":"recipe","productArea":"playbooks","score":323.32284534619976,"reasons":["search_match","term_match"],"markdown":"## Contribution boundary\n\nUse this when a named specialist must resolve a bounded correctness question that prepared Cases and source context cannot answer automatically. Do not use a Contribution as a general request to “review the assistant.”"},{"blockId":"concepts.workspaces-projects#boundary-check","pageId":"concepts.workspaces-projects","title":"Boundary check","pageTitle":"Workspaces and projects","url":"https://teammately.ai/docs/concepts/workspaces-projects.md","humanUrl":"https://teammately.ai/docs/concepts/workspaces-projects#boundary-check","markdownUrl":"https://teammately.ai/docs/concepts/workspaces-projects.md","sectionId":"boundary-check","kind":"concept","productArea":"object_model","score":323.24807999110095,"reasons":["search_match","term_match"],"markdown":"## Boundary check\n\nWhen a user cannot reach an object, confirm the Workspace, Project ID, Project membership, and object-specific assignment separately. When an artifact appears reusable across Projects, verify its source context, owner, and correctness boundary before recreating it. Shared organizational membership is never evidence that two Projects use the same Cases, standards, or Benchmark Versions.\n\n{% example-demo title=\"Same policy shape, different projects\" %}\nOne Workspace contains a billing-assistant Project and a security-assistant Project. The teams may use similar Rubric-writing practices, but their Project Agent Briefs, Cases, Policies, Harnesses, reviewers, and Benchmark evidence remain project-scoped. A user who can administer the billing Project is not assumed to have the same access in the security Project.\n{% /example-demo %}"},{"blockId":"coverage.boundary-cases#definition","pageId":"coverage.boundary-cases","title":"Definition","pageTitle":"Boundary Cases","url":"https://teammately.ai/docs/coverage-engineering/boundary-cases.md","humanUrl":"https://teammately.ai/docs/coverage-engineering/boundary-cases#definition","markdownUrl":"https://teammately.ai/docs/coverage-engineering/boundary-cases.md","sectionId":"definition","kind":"concept","productArea":"coverage_engineering","score":322.45465095123575,"reasons":["search_match","page_title_match","term_match"],"markdown":"## Definition\n\nA Boundary Case sits near a meaningful change in expected behavior: a Policy exception, an applicability edge, conflicting source authority, missing information, an escalation threshold, or another condition where a small contextual change should alter the correct output or action.\n\nBoundary Cases are not simply unusual examples. They are deliberate tests of a named distinction in the benchmark's coverage and correctness model."},{"blockId":"coverage.boundary-cases#why-it-matters","pageId":"coverage.boundary-cases","title":"Why it matters","pageTitle":"Boundary Cases","url":"https://teammately.ai/docs/coverage-engineering/boundary-cases.md","humanUrl":"https://teammately.ai/docs/coverage-engineering/boundary-cases#why-it-matters","markdownUrl":"https://teammately.ai/docs/coverage-engineering/boundary-cases.md","sectionId":"why-it-matters","kind":"concept","productArea":"coverage_engineering","score":322.4522520815147,"reasons":["search_match","page_title_match","term_match"],"markdown":"## Why it matters\n\nOrdinary Cases can make a weak rule appear reliable because they never force the team to decide where it stops applying. Boundary Cases expose vague Policy scope, overlapping Rubrics, missing exceptions, and unsupported assumptions before those problems are hidden inside aggregate results."},{"blockId":"coverage.boundary-cases#operational-check","pageId":"coverage.boundary-cases","title":"Operational check","pageTitle":"Boundary Cases","url":"https://teammately.ai/docs/coverage-engineering/boundary-cases.md","humanUrl":"https://teammately.ai/docs/coverage-engineering/boundary-cases#operational-check","markdownUrl":"https://teammately.ai/docs/coverage-engineering/boundary-cases.md","sectionId":"operational-check","kind":"concept","productArea":"coverage_engineering","score":321.983955691453,"reasons":["search_match","page_title_match","term_match"],"markdown":"## Operational check\n\nCompare the Boundary Case with a nearby ordinary Case. The pair should differ in the intended condition, not in several unrelated dimensions. Confirm that specialists can explain why the expected behavior changes, that the Rubric tests one observable criterion, and that the Case materials make the boundary visible to the evaluated system.\n\n{% example-demo title=\"Current versus superseded source\" %}\nTwo Cases ask the same eligibility question. One contains only the current policy document; the other also contains a plausible superseded document with conflicting terms. Specialists confirm that the response must follow the controlling current source or state uncertainty. The pair becomes a Boundary Case set for source authority, and its Rubric fails unsupported blending rather than generic factual error.\n{% /example-demo %}"},{"blockId":"coverage.boundary-cases#where-it-appears-in-the-product","pageId":"coverage.boundary-cases","title":"Where it appears in the product","pageTitle":"Boundary Cases","url":"https://teammately.ai/docs/coverage-engineering/boundary-cases.md","humanUrl":"https://teammately.ai/docs/coverage-engineering/boundary-cases#where-it-appears-in-the-product","markdownUrl":"https://teammately.ai/docs/coverage-engineering/boundary-cases.md","sectionId":"where-it-appears-in-the-product","kind":"concept","productArea":"coverage_engineering","score":321.78107624981436,"reasons":["search_match","page_title_match","term_match"],"markdown":"## Where it appears in the product\n\nCoverage Stories can name a boundary as a missing or thin behavior slice. Case Foundry or another sourcing workflow can prepare candidate Cases against that need. Case Review checks whether the input, materials, and contrast are realistic. If the expected judgment is unclear, route the selected Cases into an Expert Contribution instead of inventing the answer during case construction."},{"blockId":"coverage.boundary-cases#artifacts-it-affects","pageId":"coverage.boundary-cases","title":"Artifacts it affects","pageTitle":"Boundary Cases","url":"https://teammately.ai/docs/coverage-engineering/boundary-cases.md","humanUrl":"https://teammately.ai/docs/coverage-engineering/boundary-cases#artifacts-it-affects","markdownUrl":"https://teammately.ai/docs/coverage-engineering/boundary-cases.md","sectionId":"artifacts-it-affects","kind":"concept","productArea":"coverage_engineering","score":317.3804133179059,"reasons":["search_match","page_title_match","term_match"],"markdown":"## Artifacts it affects\n\nA useful Boundary Case records the exact contextual feature that changes the expectation, the controlling source material, the relevant Coverage Facets, and the Policy or Rubric question it exercises. Admission to the current Benchmark Dataset is a separate selection decision; admission to a Snapshot is a later immutable evidence decision."}]}