FAQ

Questions the interface should answer before users ask support.

A legal-product frontend should remove ambiguity early: what the tool does, what it does not do, and how users are expected to work with it.

Frequently asked questions

Is this legal advice?

No. The interface must consistently present the product as an AI research and drafting tool. Users remain solely responsible for any legal reliance, filing, implementation, or publication decision.

Why keep the public root on Coming Soon for now?

Because staged rollout is better than exposing half-finished journeys. The rest of the GUI can still be completed, tested, and SEO-prepared behind separate routes.

Will the UI support country aware behavior?

Yes. Country context should be selectable manually and detectable on demand from a country only lookup, with local first browser preference as the default.

Does the product also generate documents?

Yes, the GUI already includes a dedicated document route and now adds a document hub so users can discover drafting tools more naturally.