{"query":"Product boundaries","corpusVersion":"local","generatedAt":"2026-09-13T04:37:59.301Z","results":[{"blockId":"intro.product-boundaries#product-boundaries","pageId":"intro.product-boundaries","title":"Product boundaries","pageTitle":"Product boundaries","url":"https://teammately.ai/docs/introduction/product-boundaries.md","humanUrl":"https://teammately.ai/docs/introduction/product-boundaries#product-boundaries","markdownUrl":"https://teammately.ai/docs/introduction/product-boundaries.md","sectionId":"product-boundaries","kind":"concept","productArea":"introduction","score":960.7768848214497,"reasons":["search_match","title_match","display_title_match","term_match"],"markdown":"# Product boundaries\n\nTeammately owns the correctness system that connects specialist judgment to deliberate benchmark coverage, executable standards, constructed cases, evaluation evidence, and improvement history. This page distinguishes that system from adjacent inputs and downstream responsibilities.\n\n> Adjacent systems are inputs\n>\n> Logs, traces, source repositories, model endpoints, coding environments, and external evaluation results can supply material or receive work. Their presence does not change the Teammately ownership boundary: Teammately governs the connected correctness artifacts and the evidence produced from them."},{"blockId":"integrations.overview#product-ui-and-api-boundaries","pageId":"integrations.overview","title":"Product UI and API boundaries","pageTitle":"Integrations","url":"https://teammately.ai/docs/integrations.md","humanUrl":"https://teammately.ai/docs/integrations#product-ui-and-api-boundaries","markdownUrl":"https://teammately.ai/docs/integrations.md","sectionId":"product-ui-and-api-boundaries","kind":"concept","productArea":"data_integrations","score":585.3615056528844,"reasons":["search_match","summary_match","term_match"],"markdown":"## Product UI and API boundaries\n\nThe product UI owns interactive setup, mapping, preview, conflict resolution, and human decisions. Automated integrations should use only a supported external contract that preserves the same object and version boundaries.\n\nInternal browser endpoints, event payloads, database shapes, and service-to-service handlers are not customer integration contracts. Their presence in source code does not make them stable or safe to automate against.\n\n{% example-demo title=\"External candidate evaluation\" %}\nA team produces assistant outputs in its own evaluation pipeline. It selects an immutable Benchmark Version, downloads the exact Case IDs, and maps one output to each Case. The imported output set becomes an output-only reference Run.\n\nThe team retains its own generation ID as correlation metadata while using the Teammately Run, Benchmark Version, and Case IDs as correctness-evidence identity. Missing cost remains absent. The Run becomes interpretable after Rubric evaluation completes; successful upload alone is not a result.\n{% /example-demo %}"},{"blockId":"project-settings.overview#change-boundaries","pageId":"project-settings.overview","title":"Change boundaries","pageTitle":"Project Settings","url":"https://teammately.ai/docs/project-settings.md","humanUrl":"https://teammately.ai/docs/project-settings#change-boundaries","markdownUrl":"https://teammately.ai/docs/project-settings.md","sectionId":"change-boundaries","kind":"concept","productArea":"project_settings","score":359.0900086166446,"reasons":["search_match","term_match"],"markdown":"## Change boundaries\n\nProject Settings is intentionally separate from Agent Setup and benchmark workspaces. A settings change can influence what future work accepts or displays, but it does not silently rewrite a saved Harness Version, Dataset Snapshot, Contribution, or Run. When a project-wide contract changes, inspect downstream readiness and create new versioned evidence where the product workflow requires it.\n\nInput Schema deserves the most caution because future Case validation follows it. Before tightening a required material or changing architecture, identify existing Cases that may no longer conform. Regime changes create a new immutable Regime Version for future Benchmark Versions; existing Benchmark Versions, Runs, and results retain their published Regime Version. Project Members affects access, not authorship or task history."},{"blockId":"intro.product-boundaries#source-confidence","pageId":"intro.product-boundaries","title":"Source confidence","pageTitle":"Product boundaries","url":"https://teammately.ai/docs/introduction/product-boundaries.md","humanUrl":"https://teammately.ai/docs/introduction/product-boundaries#source-confidence","markdownUrl":"https://teammately.ai/docs/introduction/product-boundaries.md","sectionId":"source-confidence","kind":"concept","productArea":"introduction","score":330.7004516207621,"reasons":["search_match","page_title_match","term_match"],"markdown":"## Source confidence\n\nDoctrine-backed: this page states product ownership and authority boundaries. Exact UI and execution behavior is delegated to linked code-backed pages."},{"blockId":"agent-instructions#safe-operating-boundaries","pageId":"agent-instructions","title":"Safe operating boundaries","pageTitle":"Agent instructions","url":"https://teammately.ai/docs/agent-instructions.md","humanUrl":"https://teammately.ai/docs/agent-instructions#safe-operating-boundaries","markdownUrl":"https://teammately.ai/docs/agent-instructions.md","sectionId":"safe-operating-boundaries","kind":"reference","productArea":"reference","score":329.0973754184644,"reasons":["search_match","term_match"],"markdown":"## Safe operating boundaries\n\nAgents may help readers find pages, summarize stable docs, compare source-confidence labels, and draft operational next steps. Agents should not approve policies, approve rubrics, assign reviewers, declare a candidate ready for rollout, or convert draft/inferred material into public product commitments.\n\nSearch mode is diagnostic metadata, not a confidence label. Lexical fallback remains usable when semantic embeddings are unavailable; source confidence still comes from the fetched page metadata and prose."},{"blockId":"intro.product-boundaries#data-and-execution-boundary","pageId":"intro.product-boundaries","title":"Data and execution boundary","pageTitle":"Product boundaries","url":"https://teammately.ai/docs/introduction/product-boundaries.md","humanUrl":"https://teammately.ai/docs/introduction/product-boundaries#data-and-execution-boundary","markdownUrl":"https://teammately.ai/docs/introduction/product-boundaries.md","sectionId":"data-and-execution-boundary","kind":"concept","productArea":"introduction","score":326.4021065090446,"reasons":["search_match","page_title_match","term_match","prefix_or_fuzzy_match"],"markdown":"## Data and execution boundary\n\nProject Input Schema controls the accepted shape of case input and materials. Static context remains part of case content or case-material references. An executable or queryable environment uses a world reference and follows a separate runtime boundary. Public docs describe the behavior visible through stable product surfaces; they do not promote internal storage or service structures into customer-facing contracts.\n\nSimilarly, the presence of Harness Assets and managed Runs does not imply that Teammately owns a customer's model registry, production telemetry, or deployment system. A harness is the executable candidate boundary used by a benchmark evaluation.\n\n{% example-demo title=\"External coding worker\" %}\nAn Improvement Session starts from failed grounding Cases and a confirmed Goal Contract. Teammately prepares a scoped package for a coding worker with the pinned target and evidence. The worker's private activity is outside the product boundary. A returned Harness Version and canonical evaluation request become observable candidates; their Rubric results enter the session record, while Improve may add a safe narrated trajectory of observable session activity.\n{% /example-demo %}"},{"blockId":"intro.product-boundaries#related-reference-pages","pageId":"intro.product-boundaries","title":"Related reference pages","pageTitle":"Product boundaries","url":"https://teammately.ai/docs/introduction/product-boundaries.md","humanUrl":"https://teammately.ai/docs/introduction/product-boundaries#related-reference-pages","markdownUrl":"https://teammately.ai/docs/introduction/product-boundaries.md","sectionId":"related-reference-pages","kind":"concept","productArea":"introduction","score":324.15045282108343,"reasons":["search_match","page_title_match","term_match"],"markdown":"## Related reference pages\n\n{% related-card-grid title=\"Related reference pages\" %}\n- [Human Approval Boundaries](/docs/governance/human-approval-boundaries)\n- [What AI Features Can and Cannot Do](/docs/governance/what-ai-features-can-and-cannot-do)\n- [Project Input Schema](/docs/project-settings/input-schema)\n{% /related-card-grid %}"},{"blockId":"intro.product-boundaries#definition","pageId":"intro.product-boundaries","title":"Definition","pageTitle":"Product boundaries","url":"https://teammately.ai/docs/introduction/product-boundaries.md","humanUrl":"https://teammately.ai/docs/introduction/product-boundaries#definition","markdownUrl":"https://teammately.ai/docs/introduction/product-boundaries.md","sectionId":"definition","kind":"concept","productArea":"introduction","score":318.5035535592262,"reasons":["search_match","page_title_match","term_match"],"markdown":"## Definition\n\nThe product boundary follows artifacts and authority. Teammately can index project knowledge, prepare an expert contribution, materialize an accepted policy or rubric, construct a case, execute an evaluation through a managed harness, and coordinate an Improvement Session. It preserves which inputs, versions, settings, and human decisions produced the resulting evidence.\n\nCustomer teams own the AI system outside that evidence graph and the action taken afterward. Teammately can prepare a scoped package for an external coding worker, but it does not claim private work performed outside the product. It can show benchmark evidence, but it does not turn that evidence into an automatic downstream decision."}]}