All updates

Clean up the journal, refine workspace tables and make client errors actionable

In this edition

Product journal

  • Public changelog pages keep internal provenance markers, release-verification notes and internal-only placeholders out of the reader-facing Markdown.
  • Weekly editions combine a readable editorial narrative with a scannable list of the concrete product changes covered by the period.

Workspace data tables

  • Page Style card color, card opacity, block alignment, and inline detail surface opacity and gradients now apply to all workspace data tables and inline detail panels without opaque card wrappers blocking the page canvas.
  • Data tables across Capabilities, Companies, Contacts, Campaigns, Playbooks, Campaign Pipeline, Stories, Metrics, Work Items, Discovery Experiments, and Signals Reporting now support clickable column sorting, sticky headers that preserve rounded top corners while scrolling, container-responsive column folding when the detail panel opens, and locally persisted column visibility and sort order per user. Product Capabilities, Contacts, Campaigns and Stories use one page scrollbar without nested table scrolling or header corner gaps.
  • Companies, Contacts and Campaigns sort the full workspace dataset on every visible column before pagination, including linked records, profile and source details, funnel metrics and custom fields.

Contacts and campaigns

  • Companies and Contacts tables now display loaded-to-total item counts in the search bar, allow optional workspace custom fields to be toggled on in the Columns menu, sort server-side across the full dataset before pagination for database-backed columns, and order and color ICP fit badges from Unknown (gray) through No Fit (red), Weak Fit (orange), Partial Fit (yellow), and Strong Fit (green).
  • Connected MCP clients calling contact_create, contact_update, contact_upsert, company_create, company_update, and company_upsert receive specific, actionable error codes (invalid_argument, conflict, forbidden, scope_missing, rate_limited, contract_mismatch, temporarily_unavailable) and sanitized failure reasons in both content[0].text and _meta.error across validation errors, duplicate/conflicting identity matches, permission or billing write blocks, rate limits, missing RPC / schema mismatches, and temporary upstream failures. Previously, non-P0001 Supabase/PostgREST failures, permission blocks, rate limits, contract mismatches, and transient upstream errors collapsed into generic "Contact creation is temporarily unavailable.", "Company creation is temporarily unavailable.", or "Contact upsert is temporarily unavailable." messages without explaining why the call failed.

Capability landscape

  • The Product capability tree now renders as an interactive hierarchical table with aligned columns for Capability, Children, Initiatives, Evolution, Health, and Owner, plus 3-zone drag-and-drop rows to reorder siblings or reparent capabilities as children.

See how Outcomet works.

Follow a customer problem from feedback to a product decision.

See how it works
Clean up the journal, refine workspace tables and make client errors actionable | Outcomet