Conversational φ application
LiveChat-first interaction with persistent conversations, streamed reasoning and output, workflow progress, account-aware access, and downloadable results.
Product updates · φ
Where the product is going.
This page records the product direction and meaningful capability changes. It is kept deliberately practical: what exists, what is being hardened, and what is planned next.
Current product
Research product family
LiveMarket reports, company profiles, research desk outputs, decks, dashboards, and source-led deck generation are available as separate capabilities with different depth and access requirements.
Evidence and delivery foundations
LiveShared knowledge reuse, provenance-aware records, structured stage outputs, artifact packaging, visual review, and durable workflow supervision underpin the production paths.
Reliability and operational clarity
HardeningReducing false blocks, improving recovery, preserving progress across reconnects, making access boundaries clear, and ensuring users can always find the current status and deliverables.
Next improvements
Richer customer guidance
Make it easier to understand which path fits a question, what evidence depth means, how long work usually takes, and what can be done while a workflow is running.
Reusable cross-workflow knowledge
Improve semantic linking and read-only retrieval across markets, companies, facts, evidence, and prior deliverables so new work benefits from the complete Pheonix knowledge base.
Usage and account transparency
Expose clearer credit, usage, workflow queue, and delivery status information while preserving account ownership and operational privacy.
More research and visual products
Add new workflow modules and tools without changing the core conversation model: each capability will declare its inputs, output contract, evidence expectations, and access policy.
Product principles
Evidence before fluency
A polished answer is not useful if the underlying claim cannot be checked.
Smallest reliable path
Use a direct tool for a bounded need and reserve long workflows for work that benefits from their full method.
Visible progress
Long work should expose meaningful stages, status, recovery state, and deliverables rather than appearing frozen.
Capability by declaration
New workflows and tools should be discoverable through their contracts and documentation, not hidden in special cases.