# Keep the conversation tied to the right Problem

**Date:** 2026-11-02 | **Period:** Week of November 2, 2026 | **Edition:** weekly | **Canonical URL:** https://outcomet.app/changelog/2026-11-02-keep-the-conversation-tied-to-the-right-problem

Conversation Analysis now checks whether an existing Problem still fits before reusing it. Structural market conditions and peer observations stay visible without inflating direct customer reach. Workspace language now travels further across the product, and hosted Claude clients can sign in to Outcomet MCP.

## Review the market Problem, not just a title match

- Conversation Analysis v3 verifies that an existing Problem still describes the same customer situation before reusing it.
- The Problems workspace separates conditions that the product can relieve from structural market conditions. Peer observations remain visible without counting as direct customer reach.
- Problem analysis keeps actionable input from onboarding, pricing, positioning, sales, support and retention in view. Concrete feature requests and practitioner observations can become Problems, while newsletters, invoices, account reminders and vendor pitches remain outside the product decision queue.

## Use your own taxonomy across the workspace

Workspace administrators can define singular and plural labels for Evidence alongside Signals, Problems, Initiatives, Capabilities and the other core records. Those labels now carry through Signals, Strategy, Discovery, Delivery, Stories and Product Capabilities instead of stopping at a few headings.

Settings preview the default label as soon as a custom value is cleared. Conflicting singular or plural labels are caught before saving, so two different record types cannot quietly end up with the same name.

## Connect hosted Claude to Outcomet MCP

Claude on the web, desktop, mobile and Cowork can now start the Outcomet MCP sign-in flow. Compatible clients show readable tool names, and registries can inspect the server identity, available actions and static resources before authentication.

The catalog is public enough for a client to understand the connection. Every action still requires OAuth workspace access.

## Keep linked work and visual defaults in sync

The Delivery Timeline now follows batches of Capability and Initiative link changes without finishing on an older intermediate state. If another edit arrives during a refresh, the final relationships are read again.

Graph and table views also use their own calmer Light and Dark canvas defaults. Existing custom palettes and disabled backgrounds keep their choices.
