Campaign controls, Capability discovery, and Problem review
In this edition
Work with campaign fit and follow-ups
- Contact, Company, and Campaign tables and Kanban cards show three-segment ICP fit meters with person and company icons instead of text badges. Negative fit is labeled No fit. Hover over a meter to see its fit state, rationale, and any mismatch warning when a fit contact belongs to a No fit company.
- Users with write access can click the fit indicator in Campaign table rows, on Kanban cards, or in the editorial subtitle of Contact, Company, and Campaign Member details to edit the fit state and rationale. When marking a contact or company No fit, they can also mark the linked company No fit and move the campaign member to Excluded, clearing the next action and due date.
- If a campaign member only has a company name from their title or import without a linked company record, saving Company fit creates and links the company.
- Campaign Kanban cards omit the header Engaged badge. Replied notes appear in the card footer only during pre-connection outreach stages. Completed and closed stages suppress overdue badges and open due-count totals; moving a member into one of these stages clears the next action and due date unless a new follow-up is entered.
- Campaign member lists and stage summaries load members in 1,000-row slices, so campaigns with more than 1,000 members can show all members.
- In the Campaign Member detail panel, Log Touchpoint is the primary action. The touchpoint composer offers an option to exclude the member as Wrong ICP and mark the contact or company No fit. Capture Product Signal has a one-click action to move typed notes into the composer, and Contact Detail opens the full Contact or Company view within the same panel stack.
Review Initiative Capability suggestions
- Suggestions use a bounded shortlist with ancestor context, rationale, and confidence, while retaining manual review.
- Suggestions can return partial results while eligible search data is being prepared, and warn when overlong descriptions prevent complete semantic coverage. Search or provider failures still report failure. An empty partial result does not mean all Capabilities were checked, so review other Capabilities manually.
Search existing Capabilities in Nova and connected MCP clients
- Search with natural questions in German or English, Capability names, UUIDs, or technical identifiers. Nova preserves Capability match scores. Ranked results report coverage, fallback, and continuation, while retaining workspace, lifecycle, and Demo boundaries. An absent result does not establish that a Capability does not exist.
Open linked Problems and review resolution verification
- Canonical Problem links in Nova open the authenticated Problem detail even when the Problem is outside the first loaded list page. This applies to links in saved answers, tables, and lists.
- When linked Initiatives have more than 50 Changes, Problem Resolution Verification keeps the 50 most recently completed or created linked Changes. It considers each Change’s recorded delivery status and completion timestamp. A completed pull request is not downgraded to partial solely because its pre-merge description mentions local, CI, or DEV/staging validation rather than production deployment.