Workflow · How it works
Basis is built for the hard middle of research.
Much of research is getting unstuck, exploring branches, and assembling evidence. Basis supports that work and produces an artifact you can keep refining or hand off to your preferred LLM, code agent, editor, or team workflow.
Where it fits
- Before
- A question is too broad, too technical, or stuck in one branch.
- During
- Basis runs in cycles, tracks evidence, and updates a reviewable artifact as it goes.
- After
- You continue in Basis, or polish the output in the tools you already use.
Use Basis when
The problem needs more than a single answer.
Basis gives you a structured research loop and a concrete artifact you can inspect, continue, export, or take somewhere else. For a quick factual question, ordinary chat is faster. Start a run when:
- A hard question deserves a serious first pass. A run turns a difficult topic into findings, assumptions, open questions, citations, and a draft structure.
- The answer needs evidence you can check. A Draft Paper run leaves a manuscript, references, logs, and the full timeline of the work, including the approaches that failed.
- You want to compare branches. Explore competing hypotheses or implementation paths before you commit days of work to one direction.
The examples are PDFs produced by audited Basis runs. Review one to see the shape of the output before you start.
How a run works
A run repeats four steps until the work is ready to hand off.
-
Ask the hard version
State the real research question, the constraints, and what would make an answer useful. Add context and grounding material: Draft Paper runs ingest PDF, TeX, and CSV uploads, and scanned PDFs are read with OCR. Then set two caps: total cycles and a dollar budget. The budget cap is a hard stop.
-
Let the run explore
The run iterates in cycles through evidence, assumptions, branches, and draft structure, and artifacts update as it progresses. Runs persist, so you can pause, resume, or cancel at any point. Plan on roughly
6–22cycles to see meaningful progress on a hard question. -
Inspect the artifact
Open the PDF in the browser or download the pieces: manuscript TeX, references, logs, and the exportable run package. Read it the way you would read a colleague's draft. The conclusions, the citations, and the steps that produced them are all on the record.
-
Continue or hand off
When the direction is right, use
Continue runwith specific guidance, or add cycles and resume. If the constraints were wrong, change them and branch. You can also export the package and carry the work into ChatGPT, Claude, Codex, Claude Code, LaTeX, or your own review process.
draft.pdf Manuscript PDF (clean)
draft.tex Manuscript TeX
references.bib References (BibTeX)
draft_42_integrity.json Integrity summary
run package (zip) Full project · logs · timeline
What to expect
It is still research software.
Basis is strongest when you give it a concrete research goal and let it do the slow middle: branch exploration, evidence gathering, technical drafting, and artifact assembly. It is STEM-centric and tuned for technical writing and LaTeX workflows.
Treat every output as a hypothesis that still needs your review. Check the conclusions and the citations, and apply your own judgment before you publish, ship, or make a high-stakes decision on top of a run. Direction, judgment, and proof stay in your hands.
Basis is designed to hand work off cleanly. A good run produces material strong enough to make the next step easier. That next step can be another Basis cycle or a handoff to the rest of your workflow.
Next step
Try Basis on a question you are already stuck on.
Start with a targeted problem and review the artifact. Then continue in Basis, or carry the output into the tools you already use.
Public beta · email verification required. Microsoft sign-in is available; some organizations may require admin approval.