October 11, 2026
In this edition
Turn onboarding examples into real product evidence
Guided onboarding can move from the accepted Company Context into Nova feedback, GitHub and the workspace tour without treating those sources as an either-or choice.
Read moreRead less
- Nova prepares eight Demo customer messages grounded in the accepted product brief. They use email, chat and interview formats, and the ordinary analysis pipeline turns them into summaries, evidence and reviewable Problem proposals.
- Preparation shows its current stage and actual classified-message count. Saved examples and their original messages remain available after reload, alongside feedback added by the user.
- Repeated starts reuse the same preparation attempt. If the Company Context changed before any examples were saved, retry uses the current context.
- GitHub can be deferred and added later from Delivery. Valid imports are reused, while onboarding receipts, open feedback drafts and the current step survive reload.
- Demo data can be removed together after preparation completes, fails or reaches its recovery boundary. Individual Demo Feedback can also be deleted. Both paths preserve real feedback, Company Context and unrelated relationships, and Reset can prepare a fresh set.
The full flow was exercised in DEV. Production rollout is not verified.
Coordinate campaign work across the team
- Assign a campaign member to a teammate, then filter the pipeline by everyone, unassigned members or one operator.
- Pipeline cards and tables show the assignee. Touchpoint history records who performed each interaction.
- Connected MCP clients can read and set campaign assignees and attribute interactions to the acting team member.
Close Initiatives with the remaining work visible
- The Initiative closure dialog shows the aggregate number of Initiatives, Problems, Feedback items and Evidence chunks affected by the close.
- Problem verification checks linked Changes and pull requests, gives each Problem a verdict and calls out concrete remaining scope when the evidence supports only a partial resolution.
- Connected MCP clients can link or unlink Changes and Initiatives. They can also inspect prepared Initiative goal suggestions, confirm a suggested or custom goal with an idempotent receipt and open canonical Initiative URLs.
- MCP clients can link and unlink Changes from Capabilities, keeping delivery work grounded in the product model.
Keep contact networks distinct
- The Contacts page opens Company, Contact and JSON import dialogs again, and a newly created Contact opens directly in its detail panel.
- Filter Contacts by the LinkedIn network labels present in the current workspace. Source labels appear in the table and technical detail, switching filters waits for the selected network, and failed loads show an error instead of an empty result.
- Connected MCP clients can attach network provenance and tags during company or contact upserts, match Contacts by normalized LinkedIn profile URL and search by exact network, tag or profile URL. Ambiguous identities return an explicit error for review.
- Overlapping company and Contact records keep their reviewed ICP rating unless the caller supplies that reviewed record. Country LinkedIn subdomains and encoded profile slugs are accepted, and the write response returns the saved provenance.
The contact-network changes require coordinated app and MCP delivery; production rollout is not verified.