Actual PDFs · Reviewed Basis outputs
These pages are public-safe viewers built from reviewed Basis outputs. Each example centers on the document itself: the run brief, the manuscript, and the artifact trail that carried through to a handoff-ready result.
Every page below is derived from a real Basis run. The shortest is a 3-page formal note; the longest is a 38-page technical brief. Read them to judge whether Basis matches your workflow before you start a run of your own.
How these are curated
Public-safe editions
Each example is a public-safe edition of a real run output. We redact internal references, draft-state banners, and placeholder front matter. The document's structure, argument, and artifact trail are preserved.
Source runs unchanged
The stored run artifacts are never modified. Every source run keeps its full audit trail and can still be continued or resumed independently.
Read critically
Treat these the way you would any research draft. Every output is a hypothesis that still requires your review. Some Basis runs end "completed with blockers", and the audit trail records that state.
Reviewed outputs
7 documents
Research paper
A cleaned standalone paper derived from a real Basis Draft Paper run. It preserves the full manuscript structure while removing draft-state leakage, broken references, and other presentation issues that made the original export harder to read.
Research proposal
A cleaned standalone proposal derived from a real Basis Proposal run. It keeps the proposal posture intact while removing prompt-shaped title text, run-local leakage, and other presentation artifacts.
Research paper
A cleaned standalone literature-style paper derived from a real Basis Draft Paper run. It keeps the full manuscript spine, bibliography, and chapter structure while removing placeholder figures, provenance-heavy captions, and draft-state leakage.
Research paper
A cleaned standalone engineering paper derived from a real Basis Draft Paper run. It preserves the nonlinear benchmark framing, controller synthesis arc, and selection guidance while removing placeholder summary figures and public-facing provenance noise.
Technical brief
A real 38-page Basis brief on repository-scale coding-agent evaluation, presented as a curated public proof page with the actual manuscript output front and center.
Formal note
A compact Basis manuscript showing that the system can produce a tight proof note with clear assumptions, a clean theorem statement, and an explicit failure case.
Structured manuscript
A paper-style Basis manuscript that expands a simple theorem into a more structured note with setup, main result, counterexample, and a practical bounded-transform remedy.
Next step
Start with a concrete objective, your constraints, and the artifact you expect to review at the end. We usually recommend 6–22 cycles to see meaningful progress, and every run stops hard at the budget cap you set. When a run stalls, use "Continue run" with specific guidance, or change the constraints and branch.
Public beta · email verification required. Microsoft sign-in is available; some organizations require admin approval.
