All updates

October 14, 2026

Changes on October 14, 2026

Complete change list

  • Contacts JSON imports map values from custom_fields or matching top-level custom field keys and labels, and Nova (query_contacts, get_contact_details, upsert_contacts) plus the Outcomet MCP contacts RPCs can read custom field definitions and shallow-merge custom field values on Companies and Contacts with automatic synonym/alias resolution.
  • Company and Contact detail views display active custom fields in the Technical tab under Custom Fields with workspace value autocomplete suggestions, canonical Country and State/Region normalization, and case-insensitive deduplication on save.
  • Workspace administrators and editors can manage custom fields for Companies and Contacts in Settings under Workspace (Contact Fields), starting from a prefilled list of 20 Company fields and 8 Contact fields across text, URL, number, boolean, date, single-select, and multi-select types (including curated B2B select taxonomies for Department, Funding Status, Last Funding Type, and Financial Backing Status). Fields can be added, edited, archived, restored, or deleted.
  • Feedback Inbox cards display consolidated Evidence and Problem progress ratios (x/y evidence resolved and x/y problems solved, counting canonically closed Problems as solved) instead of repeating separate total and solved counters.
  • Feedback Inbox cards display derived lifecycle status badges (Open, Triaged, Ready to Close, Closed, Obsolete, Rejected) and filter by those lifecycle states directly from the Status filter bar (All Open, Open, Triaged, Ready to Close, Closed, All), with MCP and Other added to the Source filter.
  • Feedback and Problem status badges use grey for Open, blue for Triaged / In Progress, cyan for Ready to Close, emerald green for Closed, muted grey for Obsolete, and red for Rejected.
  • In Feedback Detail, the Problems section displays closed Problems by default (showClosed: true) and sorts open and proposed Problems above closed Problems.
  • Closing a Feedback item via command_feedback('set_status') or the Resolve Feedback dialog can resolve open non-context Evidence items in one step, attach an optional Change Proof (changeId and changeReason), and optionally close linked open Problems.
  • Returning from an Initiative workspace whose record is not present in a loaded Initiatives portfolio navigates back to the Initiatives board instead of opening an empty side-panel error state.
  • Problem details no longer display soft-deleted Initiatives, Decisions on soft-deleted Initiatives, or Evidence from soft-deleted Feedback items.
  • Opening a proposed Problem generated from Feedback analysis resolves edit permissions against the parent Feedback item instead of failing with an access-denied error, keeping the Approve problem and Reject proposal actions available to users with write access without exposing an editable Feedback owner picker inside the proposal view.
  • Users can open the Reporting tab in the Signals workspace (/signals?feedbackTab=reporting) to inspect signal volume, open backlog age buckets (<30d, 30–90d, 90–180d, >180d), closed signals, and untriaged open signals across 7 universal Issue Types (Feature Gap, Missing Action, Schema Drift, State Bug, Overload, Missing Logs, Praise / Context) or 5 Architectural Layers (Interface, Workflow, Integration, Data Model, Security). Clicking any KPI card, header age-bucket legend item, cluster bar, source row, Cluster × Source or Cluster × Reporter Origin matrix cell, or monthly cohort column and stacked age segment filters the bottom signal table with removable filter chips and opens the selected signal in the inline detail panel.
  • The Jev System One classification card in Signal Detail displays simplified 1–2 word labels (Customer, AI Agent, Internal Team; Interface, Workflow, Integration, Data Model, Security; Feature Gap, Missing Action, Schema Drift, State Bug, Overload, Missing Logs) and omits the retired Outcomet-specific domain cluster field while retaining backward compatibility for previously classified records.
  • Signals in the Signals Inbox, Signal Detail metadata section, and Signals Reporting table no longer display standalone severity codes (S0–S3), which remain exclusively on canonical Problems; instead, raw Signals display a source-medium icon and color indicating their channel and reporter origin (Interview, Support Ticket, Sales Call, Community, In-App, or Agent Audit).
  • Users can enable 4 additional diagnostic KPI cards with 30-day sparklines and trend indicators (Median Open Age, Open >90 Days, Customer Voice, and Empty Summaries) in the Signals Configure Metrics dialog alongside Open High Severity (S0–S1).
  • When Capability write tools are enabled, authorized Admin/Member MCP clients can reparent, retire, and merge Capabilities through canonical resource-first tools under capabilities:write. Reparenting uses hierarchy and row-version checks, retirement preserves historical relationships, and merge transfers governed relationships and children before retiring the source; external Capability proposals remain disabled.
  • Connected Admin and Member MCP clients with capabilities:write can link and unlink Capabilities and Opportunities through capability_link_opportunity and capability_unlink_opportunity when Capability context and Capability write tools are enabled.
  • Connected MCP clients with product_context:read can search and inspect Opportunities through opportunity_search and opportunity_get when Initiative context is enabled.
  • problem_unlink_evidence now passes the expected dismiss_evidence operation to the Problem command boundary instead of failing to apply the change when detaching an Evidence chunk from a Problem.

See how Outcomet works.

Follow a customer problem from feedback to a product decision.

See how it works
October 14, 2026 | Outcomet