Basis is deep research on steroids: start with a hard technical question and get a structured investigation with evidence, branches, artifacts, and an exportable draft.
Use Basis when you need more than a search summary or a polished answer. It creates a research run you can inspect, continue, export, or hand off to your normal workflow.
Basis is useful when the question is still taking shape and you need the research process to produce something inspectable, not just conversational momentum.
Give Basis the problem, constraints, and success criteria so it can map the first useful investigation instead of producing a generic overview.
Use a run to separate promising paths, weak assumptions, and open questions before you spend time writing, coding, or modeling.
Export the draft, supporting files, and run package so the next step starts from a concrete research record.
State the problem, domain, constraints, and what would make the result useful.
Let Basis gather context, explore branches, and draft around the evidence trail.
Review the draft, artifacts, figures, calculations when used, and unresolved issues.
Run another cycle, export the project, or take the output into your writing or coding stack.
Basis is a deep-research tool, not a guarantee that generated text is publication-ready without review. Treat the output as a serious draft and evidence trail.
The value is in the run: branch exploration, sources, generated artifacts, drafts, and a package you can inspect. That makes the next human or LLM pass much stronger.
For quick factual questions, normal chat is faster. For hard technical questions where evidence and artifacts matter, start with Basis.
Start with a technical problem you actually care about, then review the evidence trail and decide whether to continue in Basis or export the result.