September 2026

Evidence review and Initiative planning in one product workflow

September connects customer evidence, product decisions and delivery more closely. Initiative planning brings goals and related Problems together, while Campaigns and Stories gain controls for the work around those decisions.

In this edition

Review the evidence behind a Problem

Feedback analysis proposes reusing an existing Problem or creating a new one with cited evidence. Reviewers retain the decision: proposals can be approved or rejected, and supporting source material stays available for inspection.

Review evidence in context, adjust its severity or classification, and separate background material from actionable evidence.
Inspect original customer wording alongside English titles and summaries.
Retry stalled extraction. Historical source dates order evidence without changing ingestion history.
Attach or paste screenshots into feedback dialogs. Drafts survive dismissal, and submission waits for uploads to finish.

The customer Feedback workspace is named Signals at the end of the month. Quantitative indicators move to Metrics, with redirects for existing links.

Plan and revisit an Initiative

Initiatives bring a goal, related Problems, Decisions and Learning into a Decision brief. Start with a title-only draft, prepare goal directions or write a goal directly, then confirm a measurable outcome and success criterion.

Guided phase transitions support work, review and reopening. Historical closure receipts remain available. Closing an Initiative includes an explicit choice about which connected Problems to resolve.

The former Bet concept is absorbed into Initiatives, retaining existing records and redirects. Discovery gathers Decisions, Initiative Kanban, relative Planning, the Validation Tree and Experiments in one module. Planning supports Now, Next, Later and Closed groups.

The Validation Tree follows customer and experiment feedback through Evidence and Problems into an Initiative. Entity details open in place, and completed Changes connect to their impacted Capabilities.

Review what delivery affects

Delivery shows proposed capabilities in their hierarchy, distinct from confirmed links. Link, create or dismiss a suggestion while retaining the other proposals for review. Parent links and child proposals can be handled separately.

Exploration considers the workspace taxonomy and repository context. Supported documentation matches remain available, while empty results are not filled with arbitrary guesses.

Recent GitHub Changes loaded in Delivery receive missing analysis without a card click, with a ten-minute webhook allowance and a 48-hour automatic pickup window. Failed analysis exposes a manual retry.

Run campaigns with the right stages

Campaigns support archive, restore and deletion, and linked playbooks can be changed while reviewing how existing members move between stages. Bluesky outbound joins LinkedIn, X and Email.

Configure board visibility, success, funnel participation, rechecks and cooldowns by stage.
Return parked members to the active pipeline.
Read funnel progression from recorded stage history.
Check outreach exclusions and cooldowns across campaigns when adding contacts.

Work with sources and connected clients

Stories accepts sources from custom domains and offers platform, shelf-life and topic filters. Enrichment produces card previews and detail summaries, can use visual material, and preserves partial results when another attempt is needed. Ordinary enrichment retains customized titles.

Bluesky post links can show captured like, repost and reply counts. Platforms without metric capture, including X, remain reference links.

Connected AI clients can upsert contacts and companies by ID, domain or email, with name fallback when those identifiers are absent. Writes require contacts:write access. Problem and Initiative MCP context remains deployment-enabled and off by default, and clients using retired Theme tool names must update.

Availability boundaries

The Feedback email and deletion safeguards were verified in DEV: customer close, duplicate and delete events do not send resolved emails, and deleting the last active evidence closes a Problem as obsolete while preserving its history. Production release was not verified for these safeguards.

Nova's Low, Medium and High chat thinking configuration was verified on staging. Agent changes remain subject to confirmation.