How it works
The workflow should feel like legal operations, not prompt roulette.
This page describes the intended user journey through the frontend: select context, ask focused questions, inspect sources, and move into drafting only when needed.
1. Choose context
- •Set country context from the header.
- •Keep jurisdiction visible before a question is asked.
- •Allow browser-based defaulting and manual override at any time.
2. Ask a focused question
- •Users enter the issue in plain language.
- •The chat surface should provide suggested prompts and clear empty-state guidance.
- •The interface should make it obvious that the result is research support, not legal advice.
3. Review supporting material
- •Source visibility matters as much as the answer itself.
- •The user should be able to inspect cited materials without losing the thread of the conversation.
- •No answer should visually imply certainty without a path to source review.
4. Continue into drafting only when needed
- •Document tools should feel like a separate, deliberate workspace.
- •The transition from research to drafting must be clear.
- •Generated output must be framed as a draft aid, not a liability transfer.