Product Context
In this edition
Product Context
- Enter the workspace's product website in Product Context to build a report of its value proposition, target audience, capabilities and pricing. Open it from the Product navigation on desktop or mobile.
- Nova, Polaris and Vega receive the synthesized workspace product overview when a conversation starts. They can request deeper details from the report on demand. Competitor website content is kept separate from this product grounding.
- Analysis shows elapsed time, processing phases and discovered pages as it runs. Progress survives a refresh, in-flight analysis can resume, and a Cancel Analysis action lets the user stop and restart.
- Reports keep capability titles and descriptions readable and handle both plain text and structured AI output without the render crash caused by structured proof points or differentiators.
- Product Context's database setup was applied to staging.
Reading Competitor Websites
- Each website scan creates a dated snapshot and preserves earlier snapshots.
- Competitor details separate the vendor's website description in Their pitch from the workspace's evaluation in Our read and Against us. A full-page reader opens the brief, while scoring dimensions and trajectory sit in the Technical tab.
- Website briefs describe how the competitor organizes its product and link back to source pages. Active waitlist sites are identified separately from unreachable domains.
- Value proposition quotes are checked against extracted website text. Verified literal quotes receive a mark, and unverified claims remain visible.
- Site scans distinguish dead domains from temporary server errors and bot protection. Duplicate simultaneous scans are prevented, and scans stuck in progress become eligible for recovery after 15 minutes.
Evidence Before Closure
- From a Problem's detail drawer or view, check whether linked Changes resolve its active evidence. Read a verdict and explanation for each chunk, then open the closure dialog with the proof note already filled in.
- In an Initiative's closure checklist, verify all open Problems against linked Changes. Fully verified Problems are selected for closure and proof notes are added to the conclusion. The user still confirms the closure.